Dynamics GP end of life
Dynamics GP end of life. Plan the move to Business Central before December 31, 2029.
Microsoft ends support for current Dynamics GP on December 31, 2029, with security updates until April 30, 2031, and earlier dates for older GP versions. Microsoft points GP customers to Dynamics 365 Business Central. Bitta Apps scopes the migration in writing, moves and reconciles your GP data, and replaces add-ons and customizations with Business Central apps or extensions.
A Business Central consultant replies within one business day.
GP migration plan
Plan your Dynamics GP to Business Central move
Tell us what you run today. A Business Central consultant replies within one business day with the next steps for your GP data, add-ons and cutover date.
The short answer
When does Dynamics GP reach end of life?
For current Dynamics GP (version 18.x, on Microsoft's Modern Lifecycle Policy), support ends on December 31, 2029. After that date there are no product enhancements, no tax or regulatory updates and no Microsoft technical support. Security updates, if needed, continue until April 30, 2031. Older versions on the Fixed Lifecycle Policy end sooner: GP 2016 and GP 2016 R2 extended support ended on July 14, 2026, and GP 2018 and GP 2018 R2 extended support ends on January 11, 2028.
Microsoft points GP customers to Dynamics 365 Business Central and provides cloud migration tools for the move. A GP system keeps running after 2029, but payroll and tax updates stop, so most companies plan to be live on Business Central before their last supported year end.
- End of support
- December 31, 2029 for GP 18.x: enhancements, tax and regulatory updates and technical support end
- Security updates
- Until April 30, 2031, if needed
- Typical project
- 8 to 16 weeks for implementation, after a readiness assessment
The dates
Microsoft's Dynamics GP support timeline
Dates from Microsoft's Dynamics GP lifecycle policy.
Today
Check your GP version
GP version 18.x is under Microsoft's Modern Lifecycle Policy, with updates typically released in June, October and December. GP 2018 and GP 2018 R2 on the Fixed Lifecycle reach the end of extended support on January 11, 2028; installing a current 18.x update moves them to the Modern Lifecycle. GP 2016 and GP 2016 R2 extended support ended on July 14, 2026.
December 31, 2029
Support ends
For GP 18.x, Microsoft stops product enhancements, regulatory and tax updates, and technical support. Microsoft moved the date from September 30, 2029 so GP customers can complete payroll and tax obligations for the full year.
April 30, 2031
Security updates end
Security patches, if needed, are the last thing Microsoft provides for GP. After this date the product receives nothing further.
What migrates
What moves from GP to Business Central
Chart of accounts and history
The main account segment becomes the Business Central account number and the other segments become dimensions. Summary transactions are posted for open years and the historical years you select, by fiscal period.
Customers, vendors and open items
Active or all customers and vendors move with their addresses, plus outstanding receivables and payables at the remaining amount. Vendor 1099 data and open purchase orders can be included.
Inventory and bank
Items move with the costing method set in GP, quantities by location and lot or serial numbers. Checkbooks move with unreconciled bank transactions. Undeposited receipts do not migrate, so deposit them in GP first.
What the tool does not decide
Customizations, third-party GP add-ons, reports, integrations and payroll need their own plan. Detailed history can be kept in the GP Historical Snapshot tables or an archive. A readiness assessment turns these into a written scope.
Scope as documented in Microsoft's Dynamics GP cloud migration guide. A trial migration and reconciliation confirm what works for your companies and data.
The plan
How to move from GP to Business Central
- 01
Inventory the GP system
List companies, version and update level, add-ons, customizations, integrations, reports and the history finance needs to keep. Note which add-ons have a Business Central equivalent.
- 02
Run a Migration Readiness Assessment
A paid, written assessment ($7,500, larger scopes up to $12,500) maps GP data, processes and add-ons to Business Central configuration, apps or extensions, and produces the implementation scope.
- 03
Implement and trial-migrate
A fixed-scope implementation, typically 8 to 16 weeks, with trial migrations reconciled by your finance team: trial balance, receivables and payables aging, bank and inventory.
- 04
Cut over before your deadline
Choose a period start that leaves room before December 31, 2029, rehearse the cutover, then 30 days of hypercare. Plan around your year end and payroll calendar rather than the last possible month.
How we work
How a Bitta Apps migration runs
Guides
Plan the GP migration
- GP and NAV migration readiness planningThe data inventory, customization review and reconciliation criteria behind a scoped migration roadmap.
- Migrating NAV customizations to Business Central onlineHow legacy customizations are reviewed, replaced or rebuilt as extensions when the platform changes.
- How to choose a Business Central implementation partnerThe questions to ask before you sign a migration proposal, and the answers to expect in writing.
- Business Central partner servicesImplementation, customization, integrations, licensing and support from one accountable partner.
FAQ
Dynamics GP end of life questions
Will Dynamics GP stop working after December 31, 2029?
No. The software keeps running, but for GP 18.x Microsoft stops enhancements, tax and regulatory updates and technical support on that date, and security updates end on April 30, 2031. Running payroll and year-end tax processes on an unsupported system is the main risk.
Do the 2029 dates apply to every GP version?
No. They apply to GP version 18.x under the Modern Lifecycle Policy. Older versions follow the Fixed Lifecycle Policy: GP 2016 and GP 2016 R2 extended support ended on July 14, 2026, and GP 2018 and GP 2018 R2 extended support ends on January 11, 2028. Installing a current GP 18.x update moves a 2018 system to the Modern Lifecycle.
What is Microsoft's recommended replacement for Dynamics GP?
Microsoft encourages GP customers to move to Dynamics 365 Business Central and provides cloud migration tools from GP to Business Central online.
What data does the GP to Business Central migration tool move?
Fiscal periods, the chart of accounts with segments as dimensions, summary history for selected years, customers, vendors, open receivables and payables, open purchase orders, items with quantities and tracking, and checkbooks with unreconciled transactions. Detailed history can be kept in the GP Historical Snapshot tables.
What happens to our GP customizations and add-ons?
They do not migrate as code. Each one is mapped to standard Business Central configuration, a Microsoft Marketplace app or an extension built for Business Central, and retired where the business no longer needs it. That mapping is part of the readiness assessment.
How long does a GP to Business Central migration take?
A typical implementation takes 8 to 16 weeks after the readiness assessment. Multiple companies, heavy customization, many integrations and the history you keep extend it. Start early enough to cut over at a period start well before the end of 2029.
What does a GP migration cost?
The Migration Readiness Assessment is $7,500, with larger scopes quoted up to $12,500. Published implementation bands are Standard from $28,500, Extended $45,000 to $90,000 and Complex from $90,000. Business Central licenses are billed separately at Microsoft list rates.
Should we wait until closer to 2029?
Waiting shortens the window for testing, add-on replacement and a calm cutover, and leaves less room if a trial migration surfaces data problems. Starting with an assessment now gives you the scope and budget to choose a cutover period on your terms.