Skip to content
Get a quote

Dynamics GP support ends December 31, 2029

Deadline: December 31, 2029

Short answer

Microsoft ends Dynamics GP support on December 31, 2029, with security updates until April 30, 2031. Microsoft recommends Dynamics 365 Business Central, and its cloud migration tool moves setup, master data, open transactions and configurable history from GP 2015 or later. FlitStack AI migrates GP data with trial balance reconciliation and handles what the tool doesn't.

By

What we handle5
  • Move GP setup and master data
  • Move transactions and history
  • Source versions
  • Check the result
  • Keep working during migration

What the native tool does, and where it stops

TaskNative toolWith FlitStack AI
Move GP setup and master dataBusiness Central cloud migration: payment terms, shipping methods, sites, accounts, customers, vendors, items and classes.Maps the chart of accounts, dimensions and masters with your accounting team, including parent and child structure.
Move transactions and historyTransactional and historical data, with the scope configured per company during setup.Line-level transactions with a configurable history cut-off; the site cites 3 to 7 years as typical.
Source versionsGP 2015 or later, on SQL Server, via Azure Data Factory and a self-hosted integration runtime.Scoped per environment on the scoping call.
Check the resultMigration validation compares GP source data with Business Central and lists discrepancies.Pre and post trial balance reconciliation, with every differing account flagged and explained.
Keep working during migrationGP stays the live system; the Business Central tenant is read-only for non-SUPER users until migration completes.Plans cutover at a period end, with a final delta for late postings.
Reports, forms and integrationsRebuilt in Business Central after migration.Data and schema only; reports and custom forms are rebuilt in Business Central.

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?

DateWhat happens
September 25, 2024Microsoft announces end of support for Dynamics GP
January 15, 2025Support end moved from September 30, 2029 to December 31, 2029
April 1, 2026Final day for new customers to license GP subscriptions
July 14, 2026GP 2016 and GP 2016 R2 reach end of support
December 31, 2029GP support ends: no enhancements, tax updates or technical support
April 30, 2031Security 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?

  1. Run Microsoft’s migration assessment to check readiness and flag structural issues.
  2. Pick the cutover period. Cut over at a month or year end so opening balances are clean.
  3. 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.
  4. Clean GP data: inactive customers, vendors and items; unposted batches; old open documents.
  5. Map the chart of accounts and dimensions, including GP account segments to Business Central dimensions.
  6. Set up posting groups. Decide how GP customer, vendor and item classes map to Business Central posting groups.
  7. Run a sandbox migration and reconcile trial balance, AR and AP ageing, and inventory value.
  8. Rebuild reports, forms and integrations, including third-party GP add-ons that have no direct equivalent.
  9. Run production migration, validate, then close GP to new postings.
  10. 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.

Questions, answered

A few useful answers.

When does Dynamics GP support end?

Microsoft will end Dynamics GP support on December 31, 2029 for product enhancements, regulatory (tax) updates and technical support. The earlier date was September 30, 2029. Security updates and patches, if needed, will be available until April 30, 2031.

Can I still buy Dynamics GP?

Microsoft said the final day for new customers to license Dynamics GP subscriptions was April 1, 2026. From April 30, 2031, subscription licences can't be renewed, SPLA use is expected to end, and additional perpetual users can't be added to existing systems.

Is my version of GP already out of support?

Possibly. Dynamics GP 2016 and GP 2016 R2 reached end of support on July 14, 2026. The current version, 18.x, follows the Modern Lifecycle Policy and is covered by the December 31, 2029 date.

Does Microsoft's GP migration tool overwrite Business Central data?

Yes. Microsoft warns that existing data in Business Central online is overwritten with data from the on-premises source when replication runs, and says not to set up cloud migration for a production environment already in use.

Get a quote

Rather have it done for you?

FlitStack AI maps, validates and migrates your data, sets up the process in the new system, and keeps a one-click rollback.

Get a quote