Dynamics GP End of Support: Dates, Migration and a Timeline
Microsoft ends Dynamics GP support on 2029-12-31 and security updates on 2031-04-30. Here is what each date changes, what the cloud migration tool moves, and how to plan a migration around the US payroll year.

On this page
- Dynamics GP end of support dates
- Is Dynamics GP being discontinued?
- What the end of support changes in practice
- Your options
- What the GP cloud migration tool moves, and what it does not
- A migration planning timeline that counts back from 2029-12-31
- What to clean up in GP before migrating
- How Bitta Apps helps
Dynamics GP end of support comes in stages. Microsoft ends Dynamics GP product enhancements, tax and regulatory updates, and technical support on 2029-12-31. Security updates, if needed, continue until 2031-04-30. New customers could license GP subscriptions only until 2026-04-01. Microsoft encourages GP customers to move to Dynamics 365 Business Central.
This article is for US finance leaders and IT managers on Dynamics GP who are planning a migration. It covers the Dynamics GP end of support date for each release, what each date changes in practice, the options, what Microsoft's cloud migration tool moves to Business Central online, and a migration timeline that counts back from 2029-12-31. The Bitta Apps page on Dynamics GP end of life takes requests for a written GP migration plan.
Running Dynamics GP? Book a free discovery call to agree practical next steps, or use the short form on the Dynamics GP migration page. Prefer to talk now: (626) 766-9732.
Dynamics GP end of support dates
Microsoft first announced the end of support for Dynamics GP on 2024-09-25. In an update dated 2025-01-15, Microsoft moved the end of product support and updates from 2029-09-30 to 2029-12-31, stating that the change "will allow GP customers to meet their payroll and taxes obligations for the full year." The security patch date did not change.
Date | What happens | Microsoft source |
|---|---|---|
2026-04-01 | Final day for new customers to license Dynamics GP subscriptions | |
2026-07-14 | Extended support ended for GP 2016 and GP 2016 R2 on the Fixed Lifecycle Policy | |
2028-01-11 | Extended support ends for GP 2018 and GP 2018 R2 on the Fixed Lifecycle Policy | |
2029-12-31 | Product enhancements, tax and regulatory updates, and technical support end | |
2031-04-30 | Security updates end. Service Plan coverage ends, GP subscription licenses under SPA/DPL are no longer renewable, and no additional perpetual users can be added | GP lifecycle policies, June 2025 post |
Older releases are already unsupported: extended support for GP 2015 and GP 2015 R2, for example, ended on 2025-04-08.
GP 2018 and GP 2018 R2 sit on the Fixed Lifecycle Policy, with extended support ending 2028-01-11. Microsoft states that installing any compatible tax release or hotfix brings them to version 18.5 or later, which moves the system to the Modern Lifecycle Policy and the 2029-12-31 date. No tax release keeps GP 2018 on the fixed lifecycle.
Is Dynamics GP being discontinued?
Yes, on a schedule. Microsoft's lifecycle listing for Dynamics GP shows retirement at the end of 2029. Until then, the GP lifecycle policy page says customers stay current by taking at least one of the three yearly updates, typically released in June, October and December. Microsoft's dates describe when its enhancements, tax and regulatory updates, technical support and, later, security updates end. They do not describe a shutdown of on-premises installations.
What the end of support changes in practice
The risk is specific and dated. Three areas deserve attention.
Payroll and tax updates. After 2029-12-31, Microsoft no longer ships tax and regulatory updates for GP. For a US company running payroll in GP, that is the date that matters most: later tax table and form changes would have to come from somewhere other than Microsoft. Microsoft's stated reason for moving the date to the calendar year end is that GP customers can meet their payroll and tax obligations for the full year.
Security. Security updates, if needed, continue until 2031-04-30. After that, no new patches arrive. The infrastructure underneath GP has its own clock. Microsoft's 2029 lifecycle page lists Windows Server 2019 reaching end of support on 2029-01-09, so a GP server on that operating system loses support before GP itself does.
ISV add-ons. If your GP system runs ISV add-ons, their dates matter as much as Microsoft's. Microsoft states that the GP partner ecosystem will continue to release add-ons. Each vendor sets its own support policy, though, and those dates are not Microsoft's. Ask every add-on vendor for its GP support date in writing, and ask whether it offers a Business Central product.
Your options
Move to Business Central online. Microsoft encourages GP customers to transition to Business Central, and it documents a cloud migration tool that moves GP data to Business Central online. Microsoft states that Business Central online receives continuous updates that remove the need for expensive upgrades every few years, with major releases every April and October. Compare Essentials, Premium and Team Members licenses before you count seats.
Stay on GP until a chosen date. This is a legitimate plan when it has an end date. A company can stay on supported GP through the 2029 year end, then rely on security updates until 2031-04-30 while it finishes a move. The trade-off is time: a later start leaves fewer test migrations and less contingency before tax and regulatory updates stop.
Evaluate another ERP. Some companies will use the deadline to run a broader selection. The same work applies to any target: inventory the customizations, map the integrations, decide what history must stay reachable and plan the payroll cutover.
What the GP cloud migration tool moves, and what it does not
Microsoft's GP to Business Central online migration runs from Business Central online through Azure Data Factory, replicating data table by table from the on-premises SQL Server database. GP stays the operative system until you complete the migration.
Prerequisites on the source side are GP 2015 or later, SQL Server 2016 SP1 or later, database compatibility level 130 or higher, TCP/IP enabled, and SQL Server authentication. The assisted setup is supported for the United States, Canada, the United Kingdom and Australia.
According to Microsoft's page on migrated GP data, the tool moves:
Company setup, the chart of accounts, customers, vendors, items, checkbooks and classes (as posting groups, if you choose).
GL summary transactions by fiscal period for open years and the historical years you select. The main account segment becomes the account number and the other segments become dimensions.
Open receivables and payables at the amount still owed, open purchase orders for the item quantities still remaining, and unreconciled bank transactions.
Inventory quantities, locations, and serial and lot information, at the cost valuation method set in GP.
Vendor 1099 information for a calendar year you choose (2024 is the first supported year), and vendor EFT bank details.
An optional GP Historical Snapshot of GL detail, receivables, payables, sales order processing, purchase receipts and inventory transactions, stored in extension tables you can read in Business Central and Power BI.
What it does not do, or does differently:
Microsoft's pages on migrated GP data do not mention payroll, customizations or add-on data. Microsoft does not state outright that they are excluded, but Bitta Apps reads that silence as a reason to plan each as its own workstream and confirm the approach with your partner and add-on vendors.
Undeposited cash receipts are not migrated.
GP historical years arrive as open years and must be closed in Business Central.
Business Central has no direct equivalent to GP unit of measure schedules.
You can copy the full GP database to Azure Data Lake to keep reference access to history the tool does not migrate.
The patterns in migrating NAV customizations to Business Central online apply to GP as well: decide what standard Business Central now covers, what becomes an extension, and what to retire. The cost of carrying customization debt forward is easier to avoid at migration than after it.
A migration planning timeline that counts back from 2029-12-31
Microsoft moved the date to the year end for payroll reasons, and Bitta Apps uses the same anchor when payroll moves with the migration. Employee year-to-date earnings and year-end tax reporting are simpler when one system owns the whole calendar year. So for a company coordinating a payroll transition, the useful question is which January 1 it goes live on Business Central.
Milestone | What to have done |
|---|---|
Now to 2027 | Readiness inventory and assessment: companies, customizations, add-ons, integrations, history requirements, payroll approach |
Before 2028-01-11 | GP 2018 or GP 2018 R2 systems on the fixed lifecycle either updated to 18.5 or later or on a decided migration date |
Year end 2028 | Candidate go-live on 2029-01-01, which leaves a full supported GP year as contingency |
During 2029 | Last supported GP year. Final test migrations, reconciliation sign-off, payroll cutover rehearsal |
2030-01-01 | Latest payroll-year start on which to begin in a new system with GP fully supported through the prior year |
2031-04-30 | GP security updates end. A GP system kept for reference needs a plan |
Microsoft names the factors that drive migration run time: data volume, SQL Server configuration, connection speed and the number of companies replicated at once. Process redesign, add-on replacement and training come on top. An environment set up for cloud migration cannot be updated, so schedule test and final migrations between Business Central updates.
What to clean up in GP before migrating
Deposit every posted cash receipt.
Mark inactive customers, vendors and items, then decide whether to migrate only active records.
Choose which account segments become Global Dimension 1 and 2, and review the rest as shortcut dimensions.
Pick the oldest historical year for GL summaries and the oldest snapshot year for detail.
Reconcile receivables, payables, inventory and bank balances to the GL, so validation differences are migration issues and not old ones.
Confirm the SQL Server version and compatibility level. If you migrate from a backup, use a full backup, because Microsoft states differential or partial backups are not supported.
Decide which companies to migrate and check data size against the tenant's storage capacity, which Microsoft sets at 80 GB plus per-user allowances and any extra capacity licenses.
Microsoft's migration validation compares GP with Business Central for G/L and statistical accounts, bank accounts, customers, vendors, items, purchase orders and 1099 data. Finance should still define what it reconciles by company and period.
How Bitta Apps helps
Bitta Apps runs a fixed-fee Migration Readiness Assessment for companies on GP, NAV, QuickBooks or another ERP. It covers customization disposition, process-fit gaps, an integration map, a data and archive plan, a risk register, an executive roadmap and a fixed-price implementation estimate. As published on the Bitta Apps pricing page, the assessment is $7,500, seven business days after access; multi-entity or integration-heavy environments are quoted up to $12,500.
Business Central implementation at Bitta Apps starts with a written fixed-price proposal before any build work, with a named engagement lead, project manager and QA, and 30 days of hypercare after go-live. If you are comparing firms, the guide to choosing a Business Central implementation partner lists the questions to ask.
GP customers have dates, tooling and time. The companies that use the time well pick their January 1 early, rehearse the migration in a sandbox, and run their last GP payroll year on supported software.
Next step. Pick your January 1, then book a free discovery call to talk through your GP modules, add-ons and payroll and agree practical next steps. Or use the short form on the Dynamics GP migration page, or call (626) 766-9732.
FAQ
Frequently asked questions
Is Dynamics GP being discontinued?
Yes, on a published schedule. Microsoft ends Dynamics GP product enhancements, tax and regulatory updates, and technical support on 2029-12-31, and security updates, if needed, continue until 2031-04-30. New customers could license GP subscriptions only until 2026-04-01. Microsoft encourages GP customers to move to Dynamics 365 Business Central.
What is the Dynamics GP end of support date?
Dynamics GP support for enhancements, tax and regulatory updates, and technical support ends on 2029-12-31. Microsoft moved the date from 2029-09-30 in an update dated 2025-01-15 so customers can meet payroll and tax obligations for the full year. Security updates continue until 2031-04-30. GP 2018 and GP 2018 R2 systems still on the Fixed Lifecycle Policy reach the end of extended support on 2028-01-11.
Can I keep using GP after 2029?
Microsoft's dates mark the end of updates and support, not a shutdown of on-premises GP. After 2029-12-31 Microsoft no longer provides tax and regulatory updates, enhancements or technical support, and security updates, if needed, continue until 2031-04-30. On 2031-04-30 Microsoft also ends Service Plan coverage, stops renewals of GP subscription licenses obtained under SPA and DPL, and stops the addition of perpetual users to existing GP systems. A US company that keeps running payroll in GP after 2029 would need another source for tax updates.
How long does a GP to Business Central migration take?
Microsoft does not publish a standard duration. It states that migration time depends on the amount of data, SQL Server configuration and connection speeds, and that replicating more companies in one run takes longer. Customizations, add-on replacement, integrations and the payroll cutover usually set the overall project length. Bitta Apps states that typical implementations take 8 to 16 weeks, that complex projects need a tailored schedule, and that it commits to a go-live date in its written proposal.
Does GP history migrate to Business Central?
Partly, by choice. The cloud migration tool posts GL summary transactions by fiscal period for open years and the historical years you select, and an optional GP Historical Snapshot brings GL, receivables, payables, sales order, purchase receipt and inventory transaction detail into extension tables. Microsoft also documents copying the full GP database to Azure Data Lake for reference access to history the tool does not migrate.
Which Dynamics GP versions can migrate to Business Central online?
Microsoft's cloud migration supports Dynamics GP 2015 or later. The SQL Server database must run SQL Server 2016 SP1 or later with compatibility level 130 or higher, TCP/IP enabled and SQL Server authentication configured. The assisted setup is supported for the United States, Canada, the United Kingdom and Australia. Older GP versions must be upgraded before migrating.
Sources
Claims in this article were checked against the following on Nov 11, 2026.
- learn.microsoft.com/en-us/dynamics-gp/terms/lifecycle
- learn.microsoft.com/en-us/lifecycle/end-of-support/end-of-support-2029
- learn.microsoft.com/en-us/lifecycle/products/dynamics-gp
- learn.microsoft.com/en-us/lifecycle/products/dynamics-gp-2018-r2
- www.microsoft.com/en-us/dynamics-365/blog/it-professional/2024/09/25/announcing-end-of-support-for-dynamics-gp/
- www.microsoft.com/en-us/dynamics-365/blog/business-leader/2025/06/05/explore-migration-options-for-microsoft-dynamics-gp-and-microsoft-dynamics-sl-customers/
- www.microsoft.com/en-us/dynamics-365/blog/business-leader/2026/07/28/explore-migration-options-for-microsoft-dynamics-nav-microsoft-dynamics-gp-and-microsoft-dynamics-sl-customers/
- learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-gp-overview
- learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/cloud-migration-prerequisites-gp
- learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-dynamics-gp
- learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/cloud-migration-plan-prepare-gp
- learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/cloud-migration-azure-data-lake-gp
- learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-gp-validation
- learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/update-rollout-timeline
- bittaapps.com/services/business-central-implementation
- bittaapps.com/connect/business-central-migration-readiness
- bittaapps.com/pricing
- bittaapps.com/dynamics-gp-end-of-life
Work with Bitta Apps on this
- Dynamics GP end of lifeMicrosoft's GP support dates, what migrates to Business Central and how to plan the move.Read more
- Business Central partner servicesImplementation, customization, integrations, licensing and support, with published pricing and a written fixed-scope proposal.Read more
- QuickBooks to Business Central migrationWhat moves, what is archived, the published pricing and who signs off the cutover.Read more