Dynamics GP Planning for 2027: How to Build a Roadmap to Business Central
For many organizations, Dynamics GP has been a reliable foundation for years, and in some cases, decades. Because the system continues to work well, it can be tempting to view Microsoft’s December 31, 2029 end-of-support date as a future problem.
Over the past several years, we’ve worked with organizations at every stage of their Dynamics GP journey. Some have already moved to Dynamics 365 Business Central. Others are just beginning to ask what comes next. One thing we consistently see is that the most successful transitions begin long before an implementation project is approved. They begin when leadership teams take the time to understand what they have today, what they want their future state to look like, and what steps will help them get there.
Rather than viewing the end of support as a deadline to fear, organizations can use it as an opportunity to evaluate their systems, modernize their business processes, and build a roadmap for future growth.
Watch the full recording below for additional insights and guidance on building your Dynamics GP roadmap:
What Makes 2027 an Important Planning Year
When people hear that Dynamics GP support continues until December 31, 2029, it’s understandable to think there is plenty of time. Technically, there is. Strategically, that timeline arrives much faster than many organizations expect.
One of the most common planning mistakes we see is organizations treating 2029 as the date they need to start making decisions. In reality, by the time a company evaluates its current environment, assesses reporting requirements, reviews integrations and customizations, develops a budget, and completes an implementation, those years can disappear quickly.
For organizations using GP Payroll, the timeline becomes even more important. Payroll updates will no longer be available after support ends, making payroll planning a critical part of any transition strategy.
Customers often assume that starting the conversation means committing to a project right away. In our experience, the opposite is true. Early planning creates flexibility. It allows organizations to align ERP decisions with budgeting cycles, staffing resources, infrastructure investments, and broader business goals, rather than making decisions under pressure later.
Before You Build a Roadmap, Understand What You Have Today
Once you start thinking about the future, the first question is often, “What would a move to Business Central look like?”
Before answering that, there is usually a more important question: How are you using Dynamics GP today?
Every GP environment is different. Some organizations use primarily core financial functionality. Others have accumulated years of integrations, customizations, reporting processes, and third-party products that have become deeply embedded in day-to-day operations.
One of the biggest surprises we encounter during migration assessments is how much complexity exists beneath the surface of systems that are often described as “fairly standard.”
That’s why assessment is such an important first step.
A strong assessment goes beyond documenting software modules. It examines how the business operates.
- Which processes work well?
- Which processes frustrate users?
- Which reports require significant manual effort?
- Which workarounds have become accepted simply because they’ve existed for years?
- Which customizations continue to create value?
In many cases, organizations uncover opportunities for improvement before they ever begin discussing implementation timelines.
The goal is not simply to understand what exists today but to determine what should move forward, what should be improved, and what may no longer be necessary at all.
Business Central Is Not GP in the Cloud
Many organizations begin planning with the assumption that Dynamics 365 Business Central is simply Dynamics GP hosted in the cloud. In reality, Business Central is a different ERP platform altogether. A move from GP to Business Central is not a traditional software upgrade. It is a reimplementation that requires planning, process review, user training, and thoughtful change management.
Understanding this distinction early helps organizations build realistic timelines and take advantage of the opportunity to modernize rather than simply recreate their existing environment.
Use the Transition as an Opportunity to Improve, Not Just Replace
Once organizations have a clear picture of their current environment, a broader conversation begins. Do you want to recreate your existing system or improve it? An ERP migration creates a rare opportunity to review foundational business data.
Most companies don’t undertake an ERP transition just to arrive at the same destination. They want a system that better supports how they operate today and where they want to go tomorrow.
Revisit Long-Standing Business Decisions
This doesn’t mean redesigning every process at once. It means taking a thoughtful look at the areas where change could create meaningful value.
We’ve seen customers use this planning period to:
- Review the chart of accounts structures
- Consolidate vendors
- Standardize customer records
- Simplify item numbering conventions
- Revisit reporting structures
- Clean up legacy processes that no longer reflect the business
These conversations often lead to an important question: If we were designing this system today, would we still do it the same way?
Sometimes the answer is yes. Sometimes the answer reveals years of accumulated processes that no longer serve the organization particularly well.
Prepare for Changes in Financial Structure
A good example is the chart of accounts, as mentioned above.
Dynamics GP uses a segmented chart structure, while D365 Business Central uses dimensions. For many customers, this represents one of the biggest conceptual shifts during the transition. The dimensional approach can provide more flexibility and simplify reporting, but it also requires teams to think differently about how they organize financial information. Read our blog comparing the chart of accounts in GP with Business Central.
The earlier those discussions happen, the easier it becomes to design a future state that supports the business for years to come.
Take a Phased Approach to Transformation
Organizations are often excited about the possibilities within Business Central, including automation, AI capabilities, approval workflows, Power BI, Copilot, and broader integration with Microsoft technologies. While these capabilities can deliver significant value, trying to implement everything at once can create unnecessary complexity.
Instead, many organizations benefit from a two-phase approach:
Phase One: Establish a Strong Foundation
The initial objective is to move from GP to Business Central while minimizing disruption.
The focus remains on:
- Core financial processes
- Essential operational workflows
- Required integrations
- User adoption
- Platform stabilization
Employees can learn the new system without simultaneously managing extensive process redesigns.
Phase Two: Optimize and Innovate
Once Business Central becomes part of daily operations, organizations can begin exploring additional improvements.
This may include:
- Automated workflows
- Approval processes
- AI-assisted business processes
- Advanced analytics
- Power BI dashboards
- Power Automate integrations
- Expanded reporting capabilities
This phased approach allows organizations to build confidence while continuing to unlock new business value over time. In many cases, these optimizations become easier to implement successfully after the organization has settled into its new environment.
Key Planning Considerations
Reporting and Historical Data
Historical data remains important long after a new ERP goes live. Audits, compliance requirements, customer inquiries, and financial analysis often require access to years of historical information. Because of this, organizations should develop a clear strategy for retaining and accessing Dynamics GP data after migration.
Questions to address include:
- How long must historical data be retained?
- Who requires access?
- How frequently is it accessed?
- Does all data need to reside in the ERP system?
- What reporting requirements span historical and current information?
A thoughtful retention strategy helps organizations balance accessibility, compliance requirements, and long-term costs.
Reporting often receives less attention than data migration, but it can have a significant impact on user adoption.
Executives, managers, finance teams, and operational leaders depend on reports every day. Understanding how those reports are produced today and how they will be delivered in the future is an important part of roadmap planning.
The move to Dynamics 365 Business Central also creates an opportunity to modernize reporting through tools such as Power BI and other cloud-based reporting platforms that deliver broader visibility across the organization.
Reevaluate Customizations and Third-Party Applications
Many Dynamics GP environments contain customizations that were developed for valid business reasons years ago. However, the existence of a customization does not necessarily mean it should be recreated.
A better question is: What business problem was this customization designed to solve?
In many cases, capabilities that once required custom development are now available directly within Business Central or through specialized applications available in Microsoft’s cloud ecosystem.
Rather than assuming every customization must be rebuilt, a Microsoft Partner can help you evaluate whether it can be:
- Replaced by standard functionality
- Addressed with a Business Central extension
- Simplified through process changes
- Eliminated entirely
- Modernized through automation
This exercise frequently reduces long-term maintenance requirements while improving supportability and scalability.
Infrastructure Planning
Organizations that are evaluating SQL upgrades, hardware refreshes, server replacements, or broader IT modernization initiatives should consider how those investments align with their Business Central roadmap.
In many cases, moving to a cloud-based ERP can eliminate future infrastructure investments while reducing administrative overhead associated with maintaining on-premises environments.
The Organizations That Benefit Most Start Planning Early
The organizations getting the most value from their planning efforts aren’t starting with software demonstrations or implementation schedules. They’re starting with a roadmap. They’re evaluating business processes, understanding dependencies, reviewing reporting requirements, aligning business and technology priorities, and identifying opportunities to improve how the organization operates.
In our experience, the organizations that start these conversations early almost always have more options, more flexibility, and better outcomes. They have the time to make strategic decisions instead of reactive ones. They can focus on the business value of modernization rather than the pressure of a deadline.
Start with a Migration Assessment
A Business Central Migration Assessment helps you understand where you are today, what needs to be addressed before a migration, and how to develop a transition plan that aligns with your business goals.
Through the assessment, we review:
- Current GP functionality and usage
- Customizations, integrations, and third-party solutions
- Reporting, payroll, and historical data requirements
- Opportunities to simplify or modernize processes
- Migration considerations, timelines, and next steps
Whether you’re actively evaluating Business Central or simply beginning to plan for the years ahead, an assessment can provide the clarity needed to move forward with confidence.
Ready to start planning? Contact Encore to begin building your roadmap.