Dynamics GP reaches end of life in three steps. Microsoft stopped selling GP subscriptions to new customers on April 1, 2026, ends product updates, tax updates and technical support on December 31, 2029, and ends security patches on April 30, 2031 (source: Microsoft). GP keeps running after that, but without fixes, tax updates or Microsoft help.
Who this is for: "Our GP partner says we have time, but I need a plan before support ends." This guide is for the finance lead or controller who owns Dynamics GP and has to take a dated, sourced plan to the CFO or board. You need the real deadlines, a fair look at the options, an answer on how much history to keep, and a short list of things to start this quarter, without a sales pitch for one ERP.
Dynamics GP is not switching off tomorrow. It is, however, on a fixed clock.
Microsoft is discontinuing Dynamics GP in stages, and the end of support is already dated. If you run finance on Dynamics GP, you have probably heard three different versions of the deadline: 2026, 2029 and 2031. All three are real. They just mean different things. One has already passed, one stops your tax updates, and one stops your security patches.
This guide puts each date next to its Microsoft source, explains what it changes for your team, and compares the realistic ways forward. We cover Business Central, Dynamics 365 Finance, other ERPs, and staying on GP for a while. We also cover the question most articles skip: how much GP history to bring with you. If you want to see how a move like this runs end to end, our Dynamics 365 migration services page shows the stages.
You will finish with a dated timeline for your board and a checklist you can start this quarter.
When Is Dynamics GP End of Life?
Dynamics GP end of life runs in three stages. New customers could license GP subscriptions until April 1, 2026.1 Product enhancements, tax updates and technical support for GP 18.x end on December 31, 2029, and security patches end on April 30, 2031.2
For example, a company on GP 18.x can still take the June, October and December updates through 2029. Its 2030 payroll tax tables, though, will not come from Microsoft.
| Date | What ends | What it means for you | Source |
|---|---|---|---|
| 1 Apr 2026 (passed) | New GP subscription sales to new customers | Existing customers keep running GP. No new GP instances for new buyers. | Microsoft Dynamics 365 blog, 5 Jun 2025 |
| 31 Dec 2029 | Product enhancements, regulatory and tax updates, technical support | The 2029 year-end update is the last one Microsoft ships. You would close 2029 in early 2030 without Microsoft support. | Microsoft Learn lifecycle page |
| 30 Apr 2031 | Security updates and patches; Service Plan coverage; subscription renewals; adding users to perpetual licenses | Official end of life. GP still opens, but runs unpatched. | Microsoft Learn lifecycle page; Microsoft Dynamics 365 blog |
Microsoft has moved one of these dates before. It first set support to end on September 30, 2029, then pushed it to December 31, 2029, which is why some older articles still show September.
If you plan to add users or renew a subscription before 2031, confirm your license position early. Our Dynamics 365 licensing advisory team can check what your current agreement still allows.
The date that matters most: For most finance teams, December 31, 2029 is the real deadline. It is the last date Microsoft ships tax and regulatory updates for GP.
Which GP Version Are You On, and Does It End Sooner?
Your GP version decides your real deadline. Only GP 18.x follows the 2029 and 2031 dates. Older versions follow Microsoft's fixed lifecycle, and most of those have already ended.2
To check yours, open GP and go to Help, then About Microsoft Dynamics GP. The version number tells you which row below applies.
| Version | Lifecycle policy | Support status (as of Nov 2026) |
|---|---|---|
| GP 2013 and 2013 R2 | Fixed | Extended support ended 11 Apr 2023 |
| GP 2015 and 2015 R2 | Fixed | Extended support ended 8 Apr 2025 |
| GP 2016 and 2016 R2 | Fixed | Extended support ended 14 Jul 2026 |
| GP 2018 and 2018 R2 | Fixed | Extended support ends 11 Jan 2028 |
| GP 18.x (18.5 and later) | Modern | Supported to 31 Dec 2029; security patches to 30 Apr 2031, if you take at least one of the three yearly updates |
One detail matters for GP 2018 users. Installing any compatible tax release or hotfix moves the system to version 18.5 or later, which puts it on the modern lifecycle. So a GP 2018 site that keeps taking tax updates is effectively on the 2029 timeline.
While you are checking the version, count your users by role and list every third-party (ISV) add-on and custom report. Those three facts shape every option below, and they are the first questions any partner will ask.
If nobody has a full list of what is bolted onto GP, a technology stack assessment builds that inventory in a few days.
What Happens to Dynamics GP After Support Ends?
After December 31, 2029, Dynamics GP keeps working, but Microsoft stops shipping tax updates, regulatory changes, fixes and technical support. After April 30, 2031, security patches stop too, so the system runs unpatched.2 Nothing deletes your data or locks you out.
Here is a concrete example. A US company running payroll in GP after 2029 has to update tax tables and year-end forms itself, or buy that work from a third party, every year. Any problem with a GP service pack has no Microsoft fix behind it.
What changes after December 31, 2029
- No new tax tables, year-end forms or regulatory changes from Microsoft
- No technical support cases with Microsoft
- Security patches continue, but only when Microsoft judges them necessary
What changes after April 30, 2031
- No security patches, and no Service Plan coverage
- Subscriptions can no longer renew, and perpetual licenses can no longer add users
Microsoft has said these changes apply on April 30, 2031.1
Can you stay on GP for a while?
Yes, as a bridge. Some teams keep GP stable while they plan, especially if a recent year-end went badly or backups have never been tested. That is a sensible short-term step, not a destination. If that is you, our Dynamics GP rescue program makes GP safe first, then plans the move on your timeline.
Your Options: Business Central, Dynamics 365 Finance or Another ERP
Choose Business Central if you want the most direct path off GP with a Microsoft migration tool. Choose Dynamics 365 Finance if you run many legal entities, complex supply chains or global operations. Choose another ERP only if a clear business reason points you outside Microsoft. Stay on GP only as a short bridge.
| Option | License cost (list) | Effort | Risk | Best fit |
|---|---|---|---|---|
| Dynamics 365 Business Central (online) | Essentials $80, Premium $110, Team Members $8 per user/month, paid yearly | Moderate. Microsoft cloud migration tool for GP 2015 or later moves masters, open items and history | Low to moderate. Add-ons need replacements; processes change | Most GP customers: one or a few companies, finance plus distribution |
| Dynamics 365 Finance (with Supply Chain Management if needed) | Finance $210 per user/month, paid yearly | High. A reimplementation, not a tool-based move | Moderate to high. Longer project, bigger team | Multi-entity, multi-country, complex manufacturing or supply chain |
| Another ERP (for example NetSuite, Sage Intacct, Acumatica) | Vendor quote | High. Full reimplementation and data mapping | Moderate to high. New vendor, new partner, new skills | A strategic reason outside the Microsoft stack |
| Stay on GP for now (on GP 18.x) | Your current plan | Low now, higher later | Rises after 31 Dec 2029 (no tax updates) | A bridge while you plan, not an end state |
Prices from Microsoft's pricing pages, checked November 4, 2026.3,4 Microsoft points GP customers to Business Central first and builds the migration tooling for that path.1
Business Central
Business Central feels familiar to GP users and shares the Microsoft stack you already know, including Excel, Outlook and Power BI. The migration tool handles chart of accounts, customers, vendors, items, open transactions and history. See what a Business Central implementation covers beyond the data move.
Dynamics 365 Finance
Finance suits larger groups that GP was already stretching. It costs more per user and takes longer, so pick it for scale, not for prestige.
Another ERP
If you are seriously weighing NetSuite or Sage Intacct, compare them on your own processes and data, not feature lists, and ask each vendor to demo with your real chart of accounts.
How Much Dynamics GP History Should You Migrate?
Most companies should move open balances, master data and summary general ledger history, then keep detailed transactions in a read-only snapshot or archive. Moving every historical line into a new ERP is rarely worth the cost.
Microsoft's tool supports this split. You choose the oldest historical year to bring across as summary GL by fiscal period. An optional GP Historical Snapshot then moves detailed GL, receivables, payables, sales order, purchase receipt and inventory history into separate tables for reporting.5
| History option | What moves | Effort | Risk | Best fit |
|---|---|---|---|---|
| A. Open items only | Masters, open AR and AP, open POs, on-hand stock, balances | Lowest | Old detail lives only in GP | Clean break, GP kept read-only |
| B. Plus summary GL history | Option A plus GL summary by fiscal period from the oldest year you pick | Low | No line detail in Business Central | Most mid-market finance teams |
| C. Plus Historical Snapshot | Option B plus detailed GL, AR, AP, SOP, POP receipt and inventory history in extension tables | Moderate | Reporting needs setup | Teams that run multi-year trend or audit reports |
| D. Archive outside the ERP | History held in a GP read-only copy, a cloud-hosted GP, or a data lake archive | Low to moderate | Two places to look; storage costs | Long retention rules, very large databases |
| E. Full re-posted history | Every historical transaction rebuilt in the new ERP | Highest | Costly reconciliation | Only when a regulator requires it |
Limits to know before you decide
- Open receivables and payables migrate at their remaining balance, not the original document amount
- Undeposited receipts do not migrate, so deposit them in GP first
- GP account segments become dimensions, with a limit of eight in Business Central
- 1099 data migrates from tax year 2024 onward5
Agree the retention rule with your auditors before you pick an option. Snapshot data can feed Power BI reports, and an archive can sit in Azure, so old detail stays readable without living in the new ERP.
Once the scope is agreed, a Business Central data migration fast track moves it in tested steps.
How Long Does a GP Migration Take, and What Does It Cost?
A single-company GP to Business Central move can run in about 12 weeks. A published fixed-scope offer on Microsoft AppSource quotes that, including data transfer.6 Multi-entity or heavily customized moves, and reimplementations on another ERP, take considerably longer.
Cost has two parts: yearly licenses and the one-time project. Licenses are easy to estimate. For example, 25 Business Central Essentials users cost 25 x $80 x 12 = $24,000 a year at list price, and the same 25 users on Premium cost $33,000 a year.
The project cost depends on five things:
- How much history you move (options A to E above)
- How many companies and charts of accounts you consolidate
- How many ISV add-ons and custom reports you replace or retire
- How many integrations you rebuild (banks, payroll, ecommerce, EDI)
- Whether you migrate directly or redesign processes along the way
| Planning step | Typical time | Why it matters |
|---|---|---|
| Assessment and option choice | 4 to 6 weeks (Redefine estimate) | Sets scope, history option and budget |
| Single-company Business Central move | About 12 weeks | What a published fixed-scope AppSource offer quotes |
| Multi-entity or another ERP | Longer; scoped per project | Reimplementation, not a tool-based move |
| Buffer before 31 Dec 2029 (Redefine guidance) | At least one full year-end on the new ERP | Aim to close at least one year on the new ERP before GP support ends |
To put a number on your own scope, try the Dynamics 365 implementation cost calculator.
Checklist: What to Start This Quarter
Start with eight steps. They give you a plan your board can approve. In our experience they take about six to eight weeks of part-time effort; the effort on each step is a Redefine planning estimate, not a Microsoft figure.
- Confirm your GP version. Check Help, then About Microsoft Dynamics GP, and match it to the version table. Effort: 1 hour.
- Count your users by role. Split full finance users from occasional and approval-only users, because license types differ. Effort: 1 day.
- List every ISV add-on and custom report. Mark each one keep, replace or retire. Effort: 1 to 2 weeks.
- Run Microsoft's migration assessment. Microsoft's GP to Business Central process starts with a readiness assessment, and the migration tool needs GP 2015 or later. Effort: 1 to 2 days.
- Agree how much history moves. Pick options A to E with your auditors and record the retention rule. Effort: 1 week.
- Map your integrations. List bank feeds, payroll, ecommerce, EDI and reporting connections, and decide how each one reconnects. Effort: 1 to 2 weeks.
- Choose the target ERP and partner. Get a written scope, timeline and price for your top option. Effort: 4 to 6 weeks.
- Set a go-live window and budget. Pick a date away from year-end close, then take the plan to the board. Effort: 1 day.
For step 6, our ERP integration services team maps every connection line by line. Train key users early, so they test the new system with your own data.
- We know our exact GP version and its lifecycle date
- We counted users by role
- We listed every add-on and custom report, marked keep, replace or retire
- We ran the Microsoft migration assessment
- Our auditors agreed how much history moves and where the rest lives
- We mapped every integration
- We have a written scope, timeline and price for our chosen ERP
- Our go-live leaves at least one year-end on the new ERP before December 31, 2029
"The GP deadline rarely causes the problem. Starting the plan too late does."A common lesson from ERP migrations
Frequently Asked Questions
Is Dynamics GP being discontinued?
Yes, in stages. Microsoft stopped selling GP subscriptions to new customers on April 1, 2026, ends support and tax updates on December 31, 2029, and ends security patches on April 30, 2031. Existing GP keeps running after those dates, and Microsoft points GP customers to Dynamics 365 Business Central as the replacement.
Can I still buy Dynamics GP or add users?
New customers could license GP subscriptions only until April 1, 2026. For existing customers, Microsoft says two things end on April 30, 2031: subscriptions can no longer renew, and perpetual licenses can no longer add users.1 Terms differ by license type, so check your own agreement before you plan to grow on GP.
Will my GP add-ons work in Business Central?
No. GP add-ons do not carry over. Business Central uses its own extensions, so each add-on needs a Business Central equivalent from the same vendor, a different app, standard Business Central features, or retirement. List them early, because replacements drive both cost and timeline.
Does Microsoft charge for the GP migration tool?
The cloud migration tool is built into Business Central online, so there is no separate tool to buy, and it supports GP 2015 or later.7 You still pay for Business Central licenses and, usually, a partner to plan the move, map data, replace add-ons, test and train your team.
Should we migrate now or wait until closer to 2029?
Start planning now, even if you go live later. You want at least one year-end close on the new ERP while GP is still supported, and a plan made in 2026 or 2027 leaves room to fix surprises in testing, add-on replacement or data mapping before that deadline.
Can we host GP in Azure instead of migrating?
You can, and it can make sense as a bridge or as a read-only archive for history. Hosting changes where GP runs, not its support dates, so tax updates still stop after December 31, 2029. Confirm your SQL Server and GP versions support the target environment first.
Your Next Step
Dynamics GP gives you a clear runway, and December 31, 2029 marks the end of it. Pick an option this quarter and you can go live on your terms, with history handled and at least one year-end on the new system before GP support stops.
When you are ready to turn this into a plan, our Dynamics GP to Business Central migration service starts with a review of your GP setup, modules and add-ons, then gives you a written data map and step-by-step plan. Redefine has delivered 550+ projects over 25+ years.
For a look at how we run Dynamics 365 data work, see the Parsons Kellogg case study, where stock accuracy reached 99.0%. That was a Dynamics 365 data project, not a GP migration.
"Plan to the 2029 tax cutoff, not the 2031 security cutoff."The short version of this guide
Need a dated GP plan for your board?
Bring your GP version, user count and add-on list. We will map your options side by side, recommend how much history to move, and give you a dated plan for your board. If staying on GP for now is the right answer, we will say so.
Book a Business Central discovery sprint
Sources & Citations
Official Microsoft pages and a Microsoft marketplace listing used for the dates, prices and timelines in this guide:
- Microsoft Dynamics 365 blog, Mike Morton, "Explore migration options for Microsoft Dynamics GP and Microsoft Dynamics SL customers" (5 Jun 2025): 1 Apr 2026 as the final day for new customers to license GP subscriptions; 30 Apr 2031 end of Service Plan coverage, subscription renewals and user adds on perpetual licenses.
- Microsoft Learn, Dynamics GP lifecycle and support dates (page last updated 25 Sep 2024, checked 4 Nov 2026): GP 18.x support, product and tax updates end 31 Dec 2029; security updates end 30 Apr 2031; fixed lifecycle dates for GP 2013 to GP 2018; hotfix rule for GP 2018.
- Microsoft, Dynamics 365 Business Central pricing (checked 4 Nov 2026): Essentials $80, Premium $110 and Team Members $8 per user per month, paid yearly.
- Microsoft, Dynamics 365 Finance pricing (checked 4 Nov 2026): Dynamics 365 Finance $210 per user per month, paid yearly.
- Microsoft Learn, Migrate Dynamics GP to Business Central online (page last updated 15 Jan 2026): what the cloud migration tool moves, the oldest historical year setting, the GP Historical Snapshot, and known limits.
- Microsoft AppSource, Enavate Xcelerate GP to Business Central migration offer (checked 4 Nov 2026): example of a fixed-scope partner offer that typically runs about 12 weeks, including data transfer.
- Microsoft Learn, Dynamics GP to Business Central online end-to-end migration overview (page dated 13 Dec 2024): GP 2015 or later prerequisite and the eight-stage migration process, including the migration assessment.
Umang Patel
Co-owner | Ecommerce Architecture, Systems & Integrations
Umang Patel has worked in ecommerce and technology since 2001. He specializes in backend systems,
ecommerce architecture, ERP and platform integrations, automation, and reverse engineering complex
business processes. At Redefine Innovations, he leads technology and project teams building scalable
systems across both B2B and DTC ecommerce environments.
Areas of expertise: Ecommerce
Architecture • Backend Systems • ERP Integration • Automation • Headless Commerce • Reverse Engineering
