Microsoft is not shutting off Dynamics GP tomorrow, and that is precisely the problem. A distant deadline feels like permission to wait, and waiting is how a nine-month migration project becomes an eighteen-month scramble for the same shrinking pool of GP-to-Business Central consultants that everyone else waited for too.
The actual dates give some breathing room: new GP license sales end on April 1, 2026; support continues through December 31, 2029; and security updates run through April 30, 2031. But breathing room is not the same as a plan. The organizations that come out ahead are those that understand early on that data migration and functional equivalence are distinct problems; when treated as one, migrations fail.
What carries over
Microsoft provides a cloud migration tool for GP-to-Business Central migrations that moves records without manual reconstruction. Chart of accounts structures, customer and vendor master records, item master data, and open transactions are transferred through the tool. General ledger opening balances post as summary entries for the years you select, so comparative reporting works from day one.
Following a detailed Dynamics GP to Business Central migration checklist helps operational teams verify which default workflows transfer seamlessly and which need manual reconfiguration. This is significant progress. However, a customer record that moves forward does not carry its GP credit hold workflow. The concept survives, but the mechanism usually needs a rebuild.
What can move, but not exactly as it exists today
Several categories require mapping rather than a direct copy. Historical transaction detail is one. GP databases often hold ten to twenty years of history, and the migration tool lets you choose how far back detailed records go, typically the current and prior fiscal years, with older years summarized rather than itemized. Deeper history can move into extension tables or remain queryable in an archive, without adding clutter to the live ledger.
Dimensions present a similar challenge. Dynamics GP customers who relied on segmented account strings or Analytical Accounting for departmental tracking will find that Business Central uses a dimension model instead. The underlying need remains, but the structure does not transfer directly, and mapping takes real time for companies with several analytical layers in GP.
Security roles behave the same way. GP’s security task structure does not translate one-to-one into Business Central permission sets. Someone must decide what each role allows, rather than replicating old access levels by name. Partnering with experts for a dedicated GP to Business Central migration service ensures user roles, permission sets, and dimension mappings align directly with modern cloud governance.
What gets left behind or rebuilt
This is where GP customers most often underestimate the project. Report Writer reports and SmartList queries do not migrate. Business Central reporting uses account schedules, Power BI, and SSRS layouts, so custom reports must be recreated with different tools.
Dexterity customizations and GP-specific ISV products fall into the same category. GP relies on Dexterity, an older on-premises development model. Business Central relies on AL, a modern cloud extension framework. A customization that automates an approval step has no equivalent that can simply be installed in Business Central. Someone must evaluate whether the functionality still applies, then rebuild it as an extension or find an app that covers the need.
Third-party integrations deserve equal scrutiny. An integration built on GP’s data structure, whether it feeds a warehouse system, a payroll provider, or a customer portal, must be redeveloped to use Business Central’s APIs. Manufacturing data, fixed assets, and payroll data require separate planning, and firms that use GP Manufacturing should expect substantial configuration work in Premium.
What this means for migration planning
The practical task before migration is not a generic checklist. It is an honest inventory of four items. First, which reports and SmartLists your team actually uses each week, not just those that exist in the system. Second, which integrations are load-bearing, meaning the business cannot operate without them. Third, which customizations are still earning their keep, and which have outlived their purpose. Fourth, how much history finance genuinely needs on hand.
A company that runs mostly standard GP financials with clean master data faces a different project than one with a Dexterity customization, three ISV products, and a decade of heavily used custom reports. Understanding the long-term cost of stagnation when remaining on Dynamics GP clarifies how proactive migration prevents unexpected support expenses and security overhead. Both share the same tool and support dates. The actual work differs enormously, and assuming otherwise is how budgets and timelines fail.
The Bottom Line
Moving from Dynamics GP to Business Central is a deliberate transfer of business value and operational continuity, paired with a decision about which technical baggage to carry with you. Treat the two separately, complete an inventory first, and the move becomes a modernization project rather than a scramble against a deadline.
That inventory is where most GP customers get stuck. Knowing a customization needs evaluation is different from knowing what it should become in Business Central. That is the gap LevelShift closes for GP customers every day; we map dimension structures and rebuild integrations so the move happens with confidence. Engaging tailored Dynamics 365 Business Central consulting services provides structured scope evaluation, architecture reviews, and cutover planning to keep your migration on schedule. If you are ready to turn a support deadline into a real plan, that conversation is worth having now.
Frequently Asked Questions
Does all Dynamics GP data move to Business Central automatically? No. Master data, open transactions, and configurable ranges of historical data move through Microsoft’s tool, but deep history is typically summarized or archived rather than fully itemized.
Do Dynamics GP customizations transfer to Business Central? Generally not directly. Customizations built on Dexterity require evaluation and rebuilding as extensions because the platforms use different frameworks.
Do we have to move every year of historical transactions? No. Most organizations migrate detail for the current and prior fiscal years, summarize older years, and keep deep history in an archive.
Does Business Central exactly replace every Dynamics GP feature? Not exactly. Report Writer, SmartList, security roles, and Analytical Accounting all require reconfiguration using a different model rather than a direct replacement.
What should we assess before a GP-to-Business Central migration? Inventory actively used reports, load-bearing integrations, customizations that still solve a real problem, and the historical detail finance truly needs live.
Is there still time to plan a Dynamics GP end-of-life migration? Yes, though the practical window is shorter than the 2029 deadline suggests, because projects that involve customization review and mapping commonly take nine to eighteen months.
