Microsoft Dynamics GP is ending
Leave Dynamics GP on your terms. Land somewhere no vendor can end.
Microsoft has set the clock on Great Plains. This is the plan for getting off it cleanly: what the dates really mean, what each destination honestly costs, and where we think most GP shops should land. Our default recommendation is Odoo, the open source ERP you can own and host yourself, and we make the case for every other path too, including when they beat it. Written by the engineers who do the migrations, not a reseller.
Free 2-minute assessment. No account, no sales call required.
What the Dynamics GP end of life actually means
Four dates, one that matters most. If you run payroll or file taxes from GP, December 31, 2029 is your real deadline.
You can no longer buy GP outright.
No net-new GP instances. Existing shops can still add users.
The practical deadline: no more regulatory or payroll tax updates.
GP is frozen. No new users, even on perpetual licenses.
Where we stand
We tell you the truth about every path
Most GP-migration advice comes from a reseller who only wins if you buy their product. We are engineers, and every destination on this site gets the honest case for and against. For most GP shops that truth points to Odoo: open source, so nobody can sunset it out from under you again. And because we implement and extend Odoo rather than resell it, we build the system with you instead of billing you a license.
Where should you migrate?
For most GP shops our recommendation is Odoo, and its page explains exactly why. But no default fits everyone, so here is the honest case for every path, including when Business Central, QuickBooks, or a custom system beats it.
Migrating from Dynamics GP to Odoo
Our default pick for most GP shops
Odoo is the open source ERP that cannot be sunset out from under you. Why it is our default recommendation for most GP shops, who it fits, what changes, and the honest tradeoffs.
Compare this path →Migrating from Dynamics GP to Business Central
Dynamics 365 Business Central is Microsoft's recommended successor to GP. An honest look at when it fits, what changes, and the migration gotchas.
Compare this path →Migrating from Dynamics GP to NetSuite
NetSuite is a common landing spot for GP shops that want to leave the Microsoft stack. When it fits, what it costs you, and what to watch.
Compare this path →Migrating from Dynamics GP to QuickBooks Online
For smaller GP shops, QuickBooks Online can be the right downsize. When it fits, when you will outgrow it, and how to move cleanly.
Compare this path →When a custom system beats an off-the-shelf ERP
GP survived because it did something specific for you. Sometimes the right move off GP is a custom system, not another ERP. How to tell.
Compare this path →The hard parts nobody warns you about
A GP migration is not a data export. The risk lives in your history, your custom reports, and your payroll. These are the guides for each.
Migrating GP custom reports, integrations, and add-ons
The customizations around GP are the hardest part of leaving it. How to inventory reports, integrations, and ISV add-ons, then decide what to rebuild.
Read the guide →How to migrate Dynamics GP data without losing history
The practical approach to migrating Dynamics GP data: what to bring, what to archive, how to reconcile, and how to avoid losing your history.
Read the guide →What to do with years of Dynamics GP historical data
You do not have to migrate 15 years of GP history into a new ERP. The options for keeping history reportable without paying to run GP forever.
Read the guide →The Dynamics GP migration checklist
A practical, ordered checklist for migrating off Dynamics GP: inventory, decisions, data, cutover, and go-live, without losing your history.
Read the guide →What a Dynamics GP migration actually costs
An honest breakdown of what a Dynamics GP migration costs: the real cost drivers, rough ranges, and where budgets blow up.
Read the guide →Migrating off GP payroll before the updates stop
GP payroll is tied to the December 2029 deadline: tax and regulatory updates stop. How to plan a payroll migration and run parallel safely.
Read the guide →Who is behind this
Built by Webisoft, a software engineering firm
We are a custom software and data-engineering team. We implement and extend Odoo rather than resell it, and we have moved finance systems off legacy platforms, rebuilt the reports and integrations that grew around them, and migrated years of history into new systems without losing the numbers. This site is the guidance we give clients before an engagement begins, whichever destination it points to.
Get a scoped plan
Tell us your GP setup. We will map your realistic timeline, destination options, and what the data migration involves.
Talk to a migration engineer