Dynamics GP Support Ends December 31, 2029. What Happens Between Now and Then Is Up to You.
Microsoft Dynamics GP has a defined end-of-support timeline. But moving to a new ERP is not something most organizations should leave until the final year.
A successful Dynamics GP to Business Central migration takes planning: understanding your existing GP environment, identifying integrations and customizations, determining what data needs to move, preparing your users, testing the new system, and building a realistic path to go-live.
2029 is the deadline. Find out what your migration will require before then.
EXPLORE ASSESSMENT OPTIONSKnow the Dates
2029 ends normal GP support, and 2031 closes the final security-update window- the time to plan is now.
Know what you have, decide what moves and build the path forward.
Product updates, tax and regulatory updates, and technical support end.
The final security-update window closes.
What Should You Figure Out Before You Migrate?
A successful GP-to-Business Central migration starts long before go-live. These five questions help define the scope, risks, and path forward.
Understand Your GP Environment
Know your GP version, databases, users, reporting requirements, infrastructure, and current business processes.
Identify Integrations & Customizations
Determine what connects to GP today, what has been customized, and what functionality needs to exist in Business Central.
Decide What Data Moves
Define what historical data you need, what should migrate, and what can remain archived or accessible outside the new environment.
Build a Realistic Timeline
Account for configuration, testing, user preparation, training, and a go-live window that works for your organization.
Validate the Migration Path
Test assumptions before implementation, uncover risks early, and understand what the move will actually require.
You don't need every answer before you start. You need a clear picture of the questions.
EXPLORE ASSESSMENT OPTIONSWhat Does a Successful Migration Look Like?
SalusCare needed a sustainable path beyond Dynamics GP without creating unnecessary disruption for its accounting team. The result was a practical move to Business Central backed by responsive support.
After years on Dynamics GP, SalusCare wanted a more sustainable financial system without creating a painful or disruptive transition for its team.
Easy breezy.
“Their responsiveness and their ability to make it happen.”
A successful migration isn't just about reaching Business Central. It's about getting there without creating unnecessary pain for the people who rely on the system every day.
Choose the Level of Assessment That Matches Your Migration Readiness
Each package builds on the one before it. Start with a GP environment assessment, move into test migration, or go further with a Business Central trial environment and hands-on guidance.
- Comprehensive GP environment evaluation
- Recommendations for migration issues
- Detailed migration process scope
- Test migration using Cloud Migration Tools
- Migration results report
- Presentation of findings and next steps
- Business Central trial environment setup
- Hands-on guidance for Business Central features
Compare What's Included
Each higher-tier package includes everything in the tier before it. The table below shows exactly what you gain as you move up.
| Feature | Basic | Standard | Enhanced |
|---|---|---|---|
| Comprehensive GP Environment Evaluation | ✓ | ✓ | ✓ |
| Recommendations for Migration Issues | ✓ | ✓ | ✓ |
| Detailed Migration Process Scope | ✓ | ✓ | ✓ |
| Test Migration Using Cloud Migration Tools | — | ✓ | ✓ |
| Migration Results Report | — | ✓ | ✓ |
| Presentation of Findings and Next Steps | — | ✓ | ✓ |
| Business Central Trial Environment Setup | — | — | ✓ |
| Hands-On Guidance for Business Central Features | — | — | ✓ |
Questions Organizations Ask Before They Move
You don't need to have every migration decision made today. These are some of the questions worth answering early.
Will Dynamics GP stop working on December 31, 2029?
No. The end of Microsoft's normal support does not mean your GP environment simply stops running the next day. It does mean organizations should evaluate the technical, operational, security, and support implications of continuing to rely on GP after that date.
How long does a GP-to-Business Central migration take?
There is no single timeline that fits every organization. Data requirements, integrations, customizations, number of companies, testing, training, and available internal resources can all affect the project.
Do we need to migrate everything from Dynamics GP?
Not necessarily. Migration planning should determine what data, processes, integrations, reports, and customizations still provide value and what can remain archived or be handled differently in the future environment.
Can historical Dynamics GP data move to Business Central?
Historical-data requirements should be evaluated during assessment and migration planning. The appropriate approach depends on what information your organization needs to retain and how users need to access it after go-live.
Why start planning now if support continues through 2029?
Planning earlier gives your organization more control over testing, data preparation, user readiness, project timing, and the eventual go-live window. Waiting until the deadline is close removes that flexibility.
What does a GP migration assessment help determine?
An assessment helps establish the current-state picture: your GP environment, migration risks, integrations, customizations, data considerations, and the likely scope of a move to Business Central.
2029 Is the Deadline. Your Plan Starts Before Then.
Understand your current environment, evaluate the path forward, and give your organization the time to make the move deliberately.