What happens now that Microsoft Dynamics GP has ended?

As of now, Microsoft Dynamics GP (Great Plains) has not fully ended, but Microsoft has begun phasing it out.

Here is what’s happening and what you should expect:

Current Status (as of 2025):

• Mainstream support has ended for most versions.
• Extended support continues for the latest versions:
  • GP 18.5 (2023 release) is still under Microsoft’s Modern Lifecycle Policy, meaning it will receive updates as long as you have an active enhancement plan and stay current with updates.
  • Microsoft plans to support Dynamics GP at least through 2028, with tax and regulatory updates.
• Microsoft is not adding major new features—focus is now on bug fixes, compliance updates, and minor enhancements.

What This Means for You:

1. You can keep using GP, but you’ll be on a system in “maintenance mode.”
2. No new features means it may fall behind on integrations, automation, and reporting tools.
3. Support and talent for GP are slowly dwindling, making it harder and more expensive to maintain over time.
4. Microsoft is encouraging users to migrate to Dynamics 365 Business Central, a modern cloud-based ERP.

Your Options Moving Forward:

1. Stay on GP (short term):
   • Make sure you’re on the latest supported version (GP 18.5).
   • Keep your support plan active for updates.
2. Start planning a migration:
   • Business Central is the logical Microsoft replacement.
   • Other ERPs like NetSuite, Acumatica, or Sage Intacct may also be worth evaluating.
3. Talk to your VAR (Value-Added Reseller) or Microsoft partner:
   • They can help you understand your licensing, costs, and migration roadmap.

Key Dates:

How do I migrate from Microsoft Dynamics GP to Microsoft Dynamics Business Central?

Migrating from Microsoft Dynamics GP to Dynamics 365 Business Central (BC) is a structured but complex process.

Microsoft has provided some tools and services to assist, but success depends on your setup, customizations, and business needs.

Here’s a clear breakdown of how to do it:

Step-by-Step: Migrating GP to Business Central

1. Assess Your Current GP Environment

• Document your:
  • GP version and modules used (e.g., GL, AP, AR, Payroll).
  • Customizations, third-party ISVs (e.g., Mekorma, Greenshades), and integrations.
  • On-premises vs. hosted GP deployment.
• Clean up data if possible (inactive accounts, customers, vendors).

2. Decide on Migration Scope

You can migrate:

• Master records only (customers, vendors, items, chart of accounts).
• Open transactions (open AP, AR, unposted transactions).
• Historical data (via Data Archive or custom ETL processes).

Please note: Most migrations do not move full GP history into BC. If you need full history, consider maintaining read-only GP access post-migration.

3. Choose Migration Tools

Microsoft provides two main options:

Intelligent Cloud Insights (Built-in)

• Works for GP versions 2015+ (especially 2018 or newer).
• Migrates:
  • Chart of Accounts
  • Customers, Vendors, Items
  • Open AP/AR
• Runs via the Data Migration Wizard in Business Central.

Microsoft Data Migration Extension (for GP)

• Available in BC AppSource.
• Connects to your on-prem GP SQL database.
• Use with Azure Data Factory if you’re on cloud BC.

4. Prepare Business Central

• Choose between:
  • SaaS (cloud) version (Microsoft-hosted, preferred by Microsoft).
  • On-premises version (if you have strict data control or regulatory requirements).
• Set up users, security, and environments.
• Install any required ISVs or custom apps to replace GP add-ons.

5. Perform the Migration

• Set up a sandbox environment in Business Central.
• Run the migration tools:
  • Validate the source connection to GP SQL.
  • Select the data scope.
  • Migrate in phases (test migration > UAT > final cutover).
• Reconcile balances and test key workflows (e.g., invoicing, posting, reporting).

6. Train Users and Go Live

• Provide training on Business Central UI and differences from GP.
• Migrate or recreate custom reports (SSRS → Power BI or BC reports).
• Schedule a go-live weekend or downtime window.
• Archive your GP system if needed for audit/history access.

Key Differences to Prepare For

Common Pitfalls

• Assuming all GP functionality maps 1:1 to BC.
• Neglecting to train users—Business Central is not just a new skin on GP.
• Underestimating the need for new reporting tools (e.g., if you rely heavily on Management Reporter).
• Ignoring data cleanup before migration.

Need Help?

Most businesses use a Microsoft Partner or VAR for this process.

They can help with:

• Custom migration tools.
• Integration rebuilding.
• Historical data access solutions.
• Licensing changes.