Dynamics GP end of life: dates, migration options and cost

Dynamics GP support ends on 31 December 2029. Security patches continue only if Microsoft decides they are needed, until 30 April 2031. The end of life date that still circulates in third-party articles, 30 September 2029, is the old announcement; Microsoft set the current dates on 25 September 2024.

If your company runs 25 to 100 people, plan backwards from 31 December 2029. The last tax and regulatory updates ship for periods through that date, so any close or filing that needs a 2030 rate, form, or payroll change has to run somewhere else. Choosing a destination in 2027 and signing a phase-one scope in 2028 leaves a full quarter of live running before the deadline. If you run GP 2016, your extended support already ended on 14 July 2026, and your clock is shorter than everyone else's.

This page gives the dates version by version, what stops on each, the four realistic paths, what Microsoft's migration tool moves and leaves behind, how much history to bring, a timeline, and what drives cost.

What Microsoft has announced for Dynamics GP, version by version

Microsoft's lifecycle policy page states the dates for the current release: support ends 31 December 2029 for product enhancements, regulatory and tax updates, and technical support. Security patches, if needed, continue until 30 April 2031. The product lifecycle record stamps the final moment precisely: 22:59:59.999 Pacific time on 31 December 2029.

The dates moved once. The original plan ended support on 30 September 2029. Microsoft's announcement of 25 September 2024 set 31 December 2029 as the end of support and updates, with security patches to 30 April 2031. Third-party FAQ documents that still carry the September date are superseded, and several pages ranking for this query repeat the old date.

Modern lifecycle has applied to version 18.x since 7 October 2019. Customers stay current by taking at least one of three yearly updates, typically released on 1 June, 1 October, and 1 December. Those updates carry hotfixes, tax and regulatory changes, and usability or reliability fixes.

Older versions sit on fixed dates:

• GP 2013 and R2 (Mainstream support ended: 4 April 2018 · Extended support ends: 11 April 2023 · Status in October 2026: Unsupported)
• GP 2015 and R2 (Mainstream support ended: 14 April 2020 · Extended support ends: 8 April 2025 · Status in October 2026: Unsupported)
• GP 2016 and R2 (Mainstream support ended: 13 July 2021 · Extended support ends: 14 July 2026 · Status in October 2026: Extended support ended in July 2026)
• GP 2018 and R2 (Mainstream support ended: 10 January 2023 · Extended support ends: 11 January 2028 · Status in October 2026: Fixed dates apply only if no compatible tax release or hotfix has moved the install to 18.5 or later)
• Current release (18.x) (Mainstream support ended: n/a · Extended support ends: 31 December 2029 for support, enhancements and tax updates; 30 April 2031 for security patches if needed · Status in October 2026: The dates that matter for planning)

The GP 2018 row needs a closer look. Installing any compatible tax release or hotfix on GP 2018 or 2018 R2 moves the installation to version 18.5 or later and puts it on the modern lifecycle. Microsoft documents no update that keeps 2018 on the fixed dates. A maintained GP 2018 site is therefore already on the 2029 and 2031 timeline, while a site that has taken nothing since early 2023 hits its own cliff on 11 January 2028.

What end of support does to a company that stays on GP

Three support streams stop together on 31 December 2029: product enhancements, regulatory and tax updates, and technical support. Security patches sit outside that date on a conditional basis. Each lands differently on a running business.

Tax and regulatory updates are the sharpest edge. The last of them ship for periods through 31 December 2029. Any close or filing that needs a 2030 rate, form, or payroll change has to run somewhere else. Payroll is not given its own later stream on the pages Microsoft publishes. Confirm the payroll roadmap in writing before anyone plans to run payroll on GP past that date.

Technical support ends with them. A failure in January 2030 has no vendor case to open. Your options become community forums, your own team, and whoever still contracts for GP work at that point.

Enhancements stop too, which freezes the product. A gap you tolerate today to control cost becomes permanent, because the fix will never ship.

Security patches may be issued until 30 April 2031 only if Microsoft judges one is needed, and nothing is promised past that date. Plan the exit around 31 December 2029.

The surroundings age as well. An ERP that receives no fixes eventually meets a Windows release, a SQL Server version, or an Office update it was never tested against, and no published commitment covers that meeting. Add-ons and companion tools such as Mekorma, SmartList and Integration Manager carry their own support answers: list every one your site runs and ask each vendor for its written plan past 2029.

Canadian payroll deserves its own homework item. The pages Microsoft publishes make no separate statement about payroll after regulatory and tax updates stop, so ask for the Canadian payroll roadmap in writing before you count on anything past 2029.

Your auditor will ask how your numbers are produced and controlled. An unsupported system makes that conversation longer every year.

Your four paths off Dynamics GP

Four destinations are realistic for a company your size. Microsoft encourages GP customers toward Business Central and publishes an automated cloud migration tool for that move. The other three are legitimate choices; each becomes a broader project because Microsoft's documented tooling does not apply to them.

• Business Central (The documented route from GP: Microsoft's automated cloud migration tool; source GP 2015 or later on SQL Server 2016 or later · What to test before you commit: License count and mix, reporting parity, Canadian payroll plan)
• Dynamics 365 Finance (The documented route from GP: Microsoft's GP migration tooling targets Business Central, so a Finance move scopes its own data load · What to test before you commit: Score it on the workflows, chart of accounts, transactions and payroll calendar you already use)
• Odoo (The documented route from GP: Microsoft documents no GP migration tool for Odoo; the data load is scoped inside the project · What to test before you commit: Whether the apps cover your highest-volume workflows without heavy customization)
• Acumatica, NetSuite, or Sage Intacct (The documented route from GP: Microsoft documents no GP migration tool for these · What to test before you commit: The same workflows, chart of accounts, transactions and payroll scoring you apply to the other options)

Business Central lists at USD 80 per user per month for Essentials and USD 110 for Premium, paid yearly, as of October 2026. Canadian list prices are CAD 108.50 and CAD 149.20 plus tax. That covers the license alone; the project around it is scoped work, which the cost section takes up.

Odoo is on this list because buyers ask about it, and Flectic implements Odoo for companies in your size range; the Odoo implementation page shows how we phase it.

Whatever the destination, score candidates the same way. Take your ten highest-volume workflows, your chart of accounts, a representative year of transactions, and your payroll calendar, then make each vendor show the path for each item. In Canada, treat the written payroll answer as the heaviest criterion.

Business Central as the GP successor: what maps and what does not

Because Microsoft names Business Central as the destination, its tooling is worth understanding in detail before you scope anything.

The cloud migration overview documents what moves: the tool takes an on-premises SQL company database to Business Central online, carrying system and company setup, master data, transactional data, classes, vendor 1099 information, and historical data. The set of companies is configurable, and data moves table by table.

The documented sequence has four steps:

1. Run the assessment.
2. Complete preparation.
3. Choose Run Migration Now.
4. Verify the result and rerun replication as needed.

The prerequisites are specific. The migration FAQ, updated 24 August 2026, requires SQL Server 2016 or later with compatibility level 130 or higher, and Dynamics GP 2015 or later as the source. The setup itself has to run under a tenant admin and a Business Central admin, so whoever holds those roles needs to be available.

Mapping details shape your cutover plan. Per the GP data page:

• Fiscal periods become accounting periods.
• Years marked historical in GP arrive open and must be closed in Business Central.
• General-ledger account summary transactions are generated for open and history years.
• You choose the oldest historical year the migration picks up.
• Historical snapshots are optional per module and can use a different oldest year than the GL summary. Snapshot data lands in extension tables and shows on GP Detail Snapshot list pages.
• Record links and notes migrate through a manual action.
• After the data upgrade succeeds, you cannot replicate again from an earlier version.

One more option shapes the history decision: an optional Azure Data Lake copy of the GP database holds whatever the tool does not migrate.

The documentation is detailed on data movement and quiet on design. How your chart of accounts rebuilds, which reports must match GP output, how Canadian payroll will run, and what replaces each add-on are project decisions, and they drive scope more than the table list does. Settle them before data work starts.

Flectic runs Business Central implementations in phases, and scoping starts with exactly these questions: your companies, your add-ons, your history, and your payroll calendar.

How much history to migrate: a decision rule

The tool separates today's business from the archive, which makes history a lever you control directly. Summary transactions are generated for the open and history years you choose. Snapshots are optional per module and can use their own oldest year. A Data Lake copy holds the history the tool does not take.

The rule: set the oldest historical year where your retention policy starts, bring GL summaries for the years from there forward, bring snapshots for the modules and line detail you still look up, and point the Data Lake copy at everything else. Depth is a scope decision you set before the first rehearsal load, and the tool's oldest-year setting is where you set it.

Worked example, with the assumptions stated: a GP database that started in 2012 and a seven-year retention policy. Set the oldest historical year to 2019, so summaries cover 2019 forward. Take payables and receivables snapshots if your AP and AR staff still look up old vouchers and invoices. Point the Data Lake copy at 2012 through 2018. The validation effort falls with the volume you choose to move.

For cleanup and load mechanics, our ERP data migration guide covers the steps in order.

Your timeline, back-solved from 31 December 2029

Build the schedule backwards from dates you control. The duration comes out of your scope, and any duration quoted before a scope exists is a placeholder. Two anchors set the shape: the last tax and regulatory updates cover periods through 31 December 2029, and you want at least one full quarter of live running before that date.

Worked backwards from October 2026, a phased plan looks like this:

• By mid-2027 (Phase: Decide the path · Done means: Destination chosen, add-on inventory written down, budget approved)
• Late 2027 to early 2028 (Phase: Select and contract · Done means: Phase-one scope signed, data cleanup underway)
• 2028 (Phase: Build and rehearse · Done means: Chart of accounts and reports designed, trial loads run, core team trained)
• First half of 2029 (Phase: Phase one live · Done means: One possible scope: finance and inventory run in the new system day to day)
• Second half of 2029 (Phase: Stabilize and re-home · Done means: Payroll and tax processing off GP before the last supported year-end)
• January 2030 (Phase: GP holds history only · Done means: Tax-sensitive processing has left GP)

Your version changes the clock. GP 2016 sites are already past extended support, so every row moves earlier and the decision belongs in this budget year; the migration tool does accept GP 2016 as a source, since it takes GP 2015 or later. A GP 2018 site that has taken no compatible tax release or hotfix since early 2023 has a hard date of 11 January 2028. Everyone on the modern lifecycle plans against the table above.

The parallel quarter is there for one close: run both systems through a single month-end while GP is still supported, and mapping errors surface while they are still correctable. If you run payroll in GP, move it early in that window, because payroll has the least tolerance for a frozen tax table.

For the phase-by-phase decisions in more detail, see our ERP migration guide.

What drives the cost of a GP migration

Start with the anchor you can compute today: the license. The destination license has list prices, and they recur for as long as you run the system:

• Business Central Essentials (US list: USD 80 per user per month · Canada list: CAD 108.50 per user per month · Basis: Paid yearly, plus tax in Canada, as of October 2026)
• Business Central Premium (US list: USD 110 per user per month · Canada list: CAD 149.20 per user per month · Basis: Paid yearly, plus tax in Canada, as of October 2026)

Worked example, with the assumptions stated: 25 employees, of whom 12 need full Business Central Essentials licenses at USD 80 per user per month. That is USD 960 per month, USD 11,520 per year. In Canada, the same 12 users at CAD 108.50 come to CAD 1,302 per month, CAD 15,624 per year, plus tax. At 25 full users, the yearly Essentials figures are USD 24,000 and CAD 32,550. If those users need Premium, the same 12 users pay USD 1,320 per month at USD 110 (USD 15,840 a year) or CAD 1,790.40 per month at CAD 149.20 (CAD 21,484.80 a year), plus tax. Count your own full users before any vendor call: that recurring license total is the floor of your budget, and it is the one line you can check against the US pricing page or the Canadian pricing page for the currency you pay.

The implementation has no list price. Microsoft publishes the license prices and the migration tooling; the services figure exists only after scoping, built on your company list, add-on inventory, history depth, reporting requirements and payroll plan. Any number quoted before that scope exists is a placeholder.

The drivers, in rough order of weight: how many company databases are in the migration set, because each company adds validation work; how many add-ons need a replacement plan; how much history you bring; whether payroll moves, rebuilds or re-homes to a service; how many reports must match GP output; and how clean the data is before the first load.

Ask each bidder for three things: a fixed-scope phase-one price, data migration priced as its own line, and a phase plan with calendar dates. Scoping is the first purchase worth making; Flectic's ERP implementation services page describes how discovery and phasing work.

Three mistakes that turn this deadline into a crisis

Waiting for the last quarter

A project signed in mid-2029 leaves no supported quarter to rehearse a close and correct mapping errors before tax and regulatory updates stop. The parallel quarter needs a supported GP on the far side of it. GP 2016 sites have already used up their runway, and their planning date is now.

Migrating dirty data

Duplicate customers, dead items and unapplied credits cost little while they sit in GP. In a migration they cost validation hours, and they arrive in the new system looking official. Clean before the first rehearsal load. The tooling can rerun replication while you verify the result, but once the data upgrade succeeds you cannot replicate again from an earlier version.

Keeping add-ons you no longer need

Every add-on on your inventory needs a written migration answer or a retirement. An add-on you retire carries no replacement plan and no validation work of its own, and its line drops out of the scope you take to bidders, so check usage before you scope.

How Flectic can help

Flectic implements Microsoft Dynamics 365 Business Central for companies of 20 to 100 people in the US and Canada that are planning a move off Dynamics GP. Our finance foundation covers the general ledger, accounts payable and receivable, dimensions and bank reconciliation, and the migration reconciles opening balances before go-live. We work alongside your team through the first month-end close on the new system. Book a free discovery call with Flectic through our Dynamics 365 implementation service to map your history against your Dynamics GP support deadline.

Sources

• Dynamics GP lifecycle policy, Microsoft Learn, October 2026
• Dynamics GP product lifecycle, Microsoft Learn, October 2026
• Announcing end of support for Dynamics GP, Microsoft, September 2024
• Migrate from Dynamics GP, overview, Microsoft Learn, October 2026
• Cloud migration FAQ, Microsoft Learn, October 2026
• Dynamics GP data that migrates, Microsoft Learn, October 2026
• Business Central pricing, Microsoft, October 2026
• Business Central pricing (Canada), Microsoft, October 2026