Deadline: December 31, 2029 for support; April 30, 2031 for security updates. Microsoft announced the end of Dynamics GP in September 2024 and, in January 2025, moved the support end date from September 30, 2029 to December 31, 2029. After that, GP gets no product enhancements, no regulatory or tax updates and no technical support. Security patches continue, if needed, until April 30, 2031.
For a finance system, the end of regulatory and tax updates matters most: it becomes a compliance question well before the security date. This guide covers the dates, Microsoft’s recommended route to Business Central, and how to plan the move around your financial calendar.
What are the Dynamics GP end-of-support dates?
| Date | What happens |
|---|---|
| September 25, 2024 | Microsoft announces end of support for Dynamics GP |
| January 15, 2025 | Support end moved from September 30, 2029 to December 31, 2029 |
| April 1, 2026 | Final day for new customers to license GP subscriptions |
| July 14, 2026 | GP 2016 and GP 2016 R2 reach end of support |
| December 31, 2029 | GP support ends: no enhancements, tax updates or technical support |
| April 30, 2031 | Security updates end; subscription licences no longer renewable; SPLA use expected to end; no additional perpetual users |
The current release, 18.x, follows the Modern Lifecycle Policy. Older fixed-lifecycle versions may already be out of support, so check your version first.
Where does Microsoft want GP customers to go?
Microsoft’s GP documentation encourages customers to move to Dynamics 365 Business Central and points them to partners. Its blog lists the tools: data replication with Azure Data Factory from on-premises SQL Server to Business Central’s Azure SQL database, a data upgrade, migration documentation, comparison videos showing how GP workflows map to Business Central, and partner consultation.
What does Business Central’s GP cloud migration move?
From Microsoft’s migration overview, the cloud migration tool generally migrates:
- system and company setup, such as payment terms, shipping methods and sites;
- master data for accounts, customers, vendors and items;
- transactional data;
- classes for customers, vendors and items;
- Vendor 1099 data;
- historical data.
What is migrated is configurable per company during setup. The process runs table by table, logging success or failure for each; a table fails if it can’t be found or its schema doesn’t match.
Rules to plan around:
- Source: GP 2015 or later is a prerequisite.
- Test first: Microsoft recommends a sandbox run, then production.
- Overwrites: existing data in Business Central online is overwritten when replication runs. Don’t set it up against a production environment that is already in use.
- Read-only target: during migration, users without SUPER permissions get the Intelligent Cloud permission set and can’t change migrated data.
- One way: once data upgrade runs, you can’t replicate again from an earlier version.
- Validation: a validation step compares GP source data with Business Central and lists discrepancies.
How do I plan a GP to Business Central migration?
- Run Microsoft’s migration assessment to check readiness and flag structural issues.
- Pick the cutover period. Cut over at a month or year end so opening balances are clean.
- Decide how much history moves. Open transactions are essential; detailed history can stay in an archive if reports and audits don’t need it in Business Central.
- Clean GP data: inactive customers, vendors and items; unposted batches; old open documents.
- Map the chart of accounts and dimensions, including GP account segments to Business Central dimensions.
- Set up posting groups. Decide how GP customer, vendor and item classes map to Business Central posting groups.
- Run a sandbox migration and reconcile trial balance, AR and AP ageing, and inventory value.
- Rebuild reports, forms and integrations, including third-party GP add-ons that have no direct equivalent.
- Run production migration, validate, then close GP to new postings.
- Keep GP read-only or archived for audit queries.
What should the finance team prepare?
- A closed period to cut over at, with all batches posted and reconciled.
- Trial balance, AR ageing, AP ageing and inventory valuation reports from GP at that date, to reconcile against Business Central.
- A list of add-ons and integrations (payroll, banking, EDI, reporting) and who supports each.
- A decision on history: how many years of detail Business Central needs, and where older records will be kept for audit.
- Sign-off owners for each reconciliation, named before the migration starts.
What makes GP migrations hard?
- Third-party add-ons. Many GP systems rely on ISV products whose data lives in their own tables.
- Customised tables that won’t match Business Central’s schema.
- Multi-company setups, where each company migrates separately and intercompany logic has to be rebuilt.
- History expectations. Finance teams want years of detail; moving all of it is slow and rarely needed day to day.
- Timing. Year-end, audits and tax filing leave only a few good cutover windows each year.
Do I have to move to Business Central?
No. Business Central is Microsoft’s recommended path and the closest fit for most GP users, but end of support is also a natural point to review the whole finance stack. Teams that have outgrown GP, or run inventory-heavy or manufacturing operations, sometimes evaluate other ERPs at the same time.
Whatever the destination, the preparation is the same: clean masters, a mapped chart of accounts, a decision on history, and a reconciled trial balance at cutover. FlitStack AI’s ERP destinations include Business Central, Acumatica and Odoo, so the comparison can be made on fit rather than on which migration is easier.
Should I wait until 2029?
No. Support ends on December 31, 2029, but a finance system migration needs a quiet period, a parallel run and a year-end close on the new system. Planning back from the date leaves fewer good cutover windows than it seems, and every customer on GP is planning against the same deadline.
When to bring in FlitStack AI
FlitStack AI is a data-migration platform sold as software plus a done-for-you service. For ERP moves it migrates the chart of accounts, customers, vendors, items, transactions, inventory and purchase orders, with a configurable history cut-off and a pre and post trial balance reconciliation that flags every account where balances differ. Multi-entity setups run as separate workstreams. Reports and custom forms are rebuilt in Business Central. The site lists 1 to 3 weeks as typical for an ERP migration.
See the Business Central migration hub and the data migration service, or book a free scoping call.