Dynamics GP end of life: the dates, and what to do in 2027
Microsoft has set the dates for the end of Dynamics GP. Here is what changes at each one, how long you can reasonably stay, and what to get done in 2027 so the move happens on your schedule.
Microsoft has set firm dates for the end of Dynamics GP. None of them means GP stops working. They do mean the window for a calm, planned move is now a few years, not open-ended. This is how we walk GP clients through it.
The dates
- April 1, 2025: new perpetual licenses stopped being sold to new customers.
- April 1, 2026: new subscription licenses stopped being sold to new customers. Existing customers can still add users and modules.
- December 31, 2029: end of product support. No more feature updates, tax and regulatory updates, or technical support from Microsoft.
- April 30, 2031: end of security updates.
What each date means for you
The 2025 and 2026 dates matter mostly for new customers. If you already run GP, little changed. You can keep using it, keep your partner, and keep adding users.
December 31, 2029 is the one to plan around. After it, payroll tax tables, 1099 changes and year-end updates stop coming from Microsoft. Some ISVs and partners will keep patching for a while, but you will be depending on them rather than on the vendor. For a company that runs payroll in GP, that date is close to a hard deadline.
April 30, 2031 is when staying on GP becomes a security question. Expect your auditors, insurers and IT provider to ask about it well before then.
How long can you reasonably stay?
Most companies can run GP comfortably through 2028, and many through 2029, as long as the system still meets the business's needs. Staying put a little longer is often the right call if you are in the middle of an acquisition, a new warehouse or a leadership change. The mistake is treating 2029 as the start date for the project instead of the finish line.
There is also a practical reason not to wait: every GP partner is going to be busy in 2028 and 2029. The best consultants will be booked, and rushed projects are the ones that go badly.
What to get done in 2027
- List what GP actually does for you. Modules, add-ons, integrations, reports, and the spreadsheets people keep beside GP. The add-ons and integrations are usually where the surprises are.
- Decide how much history you need. Most companies need detailed history for two or three years and summary balances before that. Older detail can stay in a read-only copy of GP for reference.
- Clean up the data. Inactive customers, vendors and items, unused accounts, and old open transactions. Every record you clean now is one you don't have to convert.
- Choose where to go. For most GP companies that means Acumatica or Dynamics 365 Business Central. We compare them in a separate post.
- Pick a cutover date. A fiscal year-end or quarter-end makes reporting and reconciliation much simpler. Work backward from it.
What moves, and how
Moving to Business Central, Microsoft provides a migration tool that brings over the chart of accounts, customers, vendors, items, open transactions and summarized general ledger history, with an optional snapshot of detailed history for reference. Moving to Acumatica, data is converted through import scenarios. We use conversion templates built from our own GP projects, so mapping and reconciliation start from what has already worked.
Either way, the parts that take judgment are the same: redesigning the account structure where GP's segments no longer fit, deciding what replaces each add-on, and rebuilding the reports people rely on.
If you are staying on GP for now
That is fine. Keep GP current, keep your integrations and reports working, and use the time to clean data and make decisions. We support GP clients every day, and we can help you keep the system useful until the move makes sense.
If you want to talk through your timeline, write to us at info@pivotalridge.com.