Microsoft has confirmed that Dynamics GP (formerly Great Plains) will reach end of mainstream support on 31 December 2029, with extended support ending in 2031. For the tens of thousands of organisations still running Dynamics GP, this creates a clear and urgent mandate: plan your migration to Business Central now, while you have time to do it properly.
This guide covers everything GP users need to know – why Business Central is the right destination, how the migration works, what data migrates easily and what requires manual effort, and how to structure your project for a smooth go-live.
Why Business Central Is the Right Destination for GP Users
Microsoft has invested significantly in making Business Central the natural upgrade path for Dynamics GP:
- Purpose-built migration tooling: Microsoft provides a Dynamics GP migration wizard built directly into Business Central
- Familiar financial logic: Business Central and GP share similar financial architecture
- Cloud-native: Business Central runs on Azure and updates automatically, eliminating costly upgrade projects
- Microsoft 365 integration: Unlike GP, Business Central integrates natively with Teams, Outlook, Power BI, and Power Automate
- No re-implementation required: Business Central is Microsoft’s modern ERP, and GP experience maps directly to equivalent BC concepts
Alphavima’s Microsoft Business Central ERP consulting practice has delivered GP migrations across professional services, distribution, and manufacturing customers.
What Changes - and What Stays the Same
What Stays Familiar
- Chart of accounts and GL posting structure
- Receivables and payables management
- Bank reconciliation
- Fixed assets
- Purchase order and sales order processing
- Multi-company support
What Changes Significantly
- Customisations: GP customisations built in Dexterity or Modifier do not migrate. They must be rebuilt as Business Central extensions using AL code or replaced with AppSource apps
- Report Writer reports: GP’s Report Writer reports do not transfer. Business Central uses SSRS-based reports or Power BI
- SmartList: Business Central uses native list views and Power BI
- Analytical Accounting: Business Central uses dimensions to replicate the multi-dimensional analysis
- User interface: Business Central uses a browser-based interface – fundamentally different from GP’s desktop client
The GP to Business Central Migration Tool
Microsoft’s built-in migration tool handles a significant portion of the technical migration automatically.
Migrated automatically: chart of accounts; customer and vendor master data; item master data; open transactions (invoices, purchase orders, sales orders); historical transactions (configurable years); bank account master data.
Not migrated automatically: GP customisations and third-party add-ons; Report Writer reports; SmartList queries; Manufacturing module data; Fixed assets; Payroll data.
To use the tool, access Cloud Migration Management in Business Central Admin Centre and follow the wizard to connect to your GP SQL database.
Migration Approach
Phase 1: Discovery and Gap Analysis (Weeks 1-4)
- Audit all GP modules in use
- List all customisations, Report Writer reports, and SmartList queries
- Map GP modules to Business Central equivalents
- Document all GP integrations
Phase 2: Business Central Configuration (Weeks 4-10)
- Set up chart of accounts, posting groups, and number series
- Configure dimensions to replicate GP Analytical Accounting segments
- Set up bank accounts, tax codes, and currencies
- Build or source Business Central equivalents for critical GP customisations
Phase 3: Run the Migration Tool (Weeks 10-12)
- Execute the GP migration wizard for master data and open transactions
- Import historical transaction data for the agreed number of years
- Validate migrated data against GP reports
Phase 4: Rebuild Integrations (Weeks 10-14, overlapping)
- Rebuild GP integrations using Business Central APIs and Power Automate
- Test each integration end-to-end with real data volumes
Phase 5: Testing and Training (Weeks 14-18)
- User acceptance testing with core process owners
- Parallel processing – run GP and BC simultaneously for 2-4 weeks
- Role-based training for all user groups
Phase 6: Go-Live and Hypercare (Weeks 18-20)
- Cutover on agreed date; freeze GP
- Provide hypercare support for 2-4 weeks
- GP remains available in read-only mode for 12-24 months
Mapping Key GP Modules to Business Central
| Dynamics GP Module | Business Central Equivalent |
|---|---|
| General Ledger | Finance → General Ledger |
| Receivables Management | Finance → Accounts Receivable |
| Payables Management | Finance → Accounts Payable |
| Inventory Control | Inventory Management |
| Purchase Order Processing | Purchase Management |
| Sales Order Processing | Sales Management |
| Fixed Assets | Fixed Assets |
| Analytical Accounting | Dimensions (G/L and Shortcut Dimensions) |
| SmartList | List Views + Power BI |
| Report Writer | SSRS Reports + Power BI |
| Manufacturing (MFG) | Manufacturing (BC Premium) |
| Field Service | Dynamics 365 Field Service (separate) |
| Payroll | Third-party via AppSource |
Common GP Migration Challenges
Challenge 1: Dexterity Customisations. GP customisations built in Dexterity are not portable. Each must be assessed individually and either rebuilt as a Business Central AL extension, replaced by a standard BC feature, or sourced as an AppSource app. Budget 2–8 weeks of development for complex customisations.
Challenge 2: Historical Data Volume. GP databases can contain 10–20 years of transaction history. The migration tool can transfer several years, but migrating all historical data is rarely necessary. Agree on a practical historical data window (typically 3–5 years).
Challenge 3: Manufacturing Complexity. GP Manufacturing is a complex module. Business Central Premium includes manufacturing, but detailed configuration is required.
Challenge 4: Report Re-creation. GP users often rely on custom Report Writer reports. These do not migrate – they must be rebuilt in Business Central’s reporting layer or Power BI.
Business Central vs Dynamics GP: What You Gain
| Feature | Dynamics GP | Business Central |
|---|---|---|
| Deployment | On-premises or hosted | Cloud (SaaS) |
| Update model | Manual upgrades every 2–3 years | Automatic twice-yearly updates |
| Teams integration | No | Native |
| Power BI embedded | No | Yes |
| Power Automate | No | Yes |
| Mobile access | Limited (web client) | Full browser + mobile app |
| AI/Copilot features | None | Growing Copilot capabilities |
| Multi-currency | Yes | Yes (enhanced) |
Need Help Migrating from Dynamics GP to Business Central?
Move from Microsoft Dynamics GP to Business Central Online with a structured migration strategy covering data, integrations, reporting, and cloud readiness.
Conclusion
The end-of-support deadline for Dynamics GP is not a distant concern – it is a project planning trigger. Companies that start their migration now have time to do it properly: rigorous discovery, careful configuration, thorough testing, and a parallel running period.
Business Central is not just a like-for-like replacement for GP. It is a platform upgrade – cloud-native, AI-enabled, and deeply integrated with the Microsoft 365 stack.
Don’t wait for 2029. Alphavima’s certified Dynamics GP specialists can assess your environment, plan your migration, and deliver a smooth transition to Business Central. Contact our Business Central consulting team near you.
FAQs
When does Microsoft Dynamics GP reach end of support?
Microsoft Dynamics GP mainstream support ends on 31 December 2029, with extended support available until 31 December 2031. While this gives GP users several years, starting a migration project in 2025 or 2026 is strongly recommended to allow adequate time for project delivery without the pressure of an imminent deadline.
Can I use the GP migration tool for all versions of Dynamics GP?
Microsoft's built-in migration tool supports Dynamics GP versions 2015 and later. Companies running GP 2013 or earlier should plan for a more manual migration approach. Alphavima can assess your specific GP version and recommend the most efficient migration path.
How much does a GP to Business Central migration cost?
Migration project costs vary based on company size, number of modules, customization complexity, integrations, and data volumes. A typical mid-market migration project (50–150 users, standard finance and inventory modules, limited customizations) generally ranges from $60,000 to $180,000 USD in implementation services. Organizations with complex manufacturing processes, multiple integrations, or extensive custom development should budget $180,000 to $350,000+ USD. Licensing, ISV apps, data cleanup, testing, and post-go-live support can also affect total project cost.
Will my GP add-ons work in Business Central?
GP third-party add-ons do not transfer to Business Central. However, most GP ISV solutions have Business Central equivalents available on Microsoft AppSource. For every critical GP add-on, identify the Business Central equivalent during your gap analysis phase.
How does Business Central handle the multi-company functionality of Dynamics GP?
Business Central fully supports multi-company scenarios. Each company is a separate environment within the same tenant. Intercompany transactions - intercompany journals, intercompany purchase and sales orders - are supported natively. Consolidation reporting across companies is available through the financial consolidation module.
Can I run Dynamics GP and Business Central in parallel during migration?
Yes, and this is strongly recommended. A parallel running period of 2-4 weeks - where you process the same transactions in both GP and BC - validates data accuracy and process correctness before full cutover. Microsoft licences allow Business Central trial environments specifically to support this testing phase.
What happens to Dynamics GP data after we go live on Business Central?
After go-live, Dynamics GP should remain available in read-only mode for at least 12–24 months to support audit queries, tax investigations, and prior-year reporting. Your GP SQL database can be backed up and stored at minimal cost. For long-term archiving, consider exporting historical data to a Power BI dataset for ongoing query access.
Is Business Central better than Dynamics GP for Power BI reporting?
Significantly better. Business Central has native Power BI integration with embedded dashboards accessible directly within the Business Central interface. Pre-built content packs for Finance, Sales, and Inventory are available immediately. GP requires separate Power BI connectors and custom data modelling. For organisations that invest heavily in data analytics, this alone often justifies the migration.