How to Migrate from Microsoft Dynamics GP to Dynamics 365 Business Central in 2026

Dynamics GP is still running critical finance operations for many organizations, but Microsoft’s published support timeline makes modernization planning urgent. A GP-to-Business-Central migration can reduce infrastructure dependency, improve reporting, and connect ERP data with Microsoft 365, Power BI, Power Platform, and Copilot-enabled workflows — if it is planned as a business transformation, not just a data import.

Why GP migration planning matters now

Microsoft has announced a defined lifecycle path for Dynamics GP: product support, hotfixes, tax updates, and regulatory updates are scheduled to end on September 30, 2029, with security updates continuing until April 30, 2031. That does not mean every GP customer must move immediately, but it does mean finance and IT teams should build a realistic migration roadmap now. Dynamics 365 Business Central is Microsoft’s cloud ERP for small and midsize organizations, with regular release waves, browser-based access, integration with Microsoft 365, Power BI and Power Platform, and identity management through Microsoft Entra ID.

Business Central editions and licensing context

Business Central is available mainly as Essentials or Premium. Essentials covers core financial management, sales, purchasing, inventory, project management, warehouse basics, and many operational processes. Premium adds manufacturing and service management capabilities. Team Members licenses can be used for limited access scenarios, such as approvals, read access, and light updates. Most customers buy Business Central through Microsoft Cloud Solution Provider licensing under the New Commerce Experience, with monthly or annual term options depending on business needs. Licensing should be reviewed before migration because GP users, security roles, device access, reporting users, and external integrations may not map one-to-one to Business Central licenses.

Use the current GP version and build before you migrate

The old guidance that focused on GP 2015, GP 2016, and GP 2018 is no longer sufficient for 2026 planning. For a supported migration project, organizations should plan from a current Dynamics GP 18.x release on a supported SQL Server and Windows Server platform, with the latest applicable service pack or hotfixes installed. Older GP deployments may require a technical upgrade, database cleanup, or remediation before migration tools can be used reliably. Before starting, confirm the current Microsoft documentation for the GP migration tool and verify prerequisites for the Business Central online environment, SQL connectivity, company databases, and any required migration extensions.

What the standard migration tools can and cannot do

Microsoft provides migration capabilities for moving core Dynamics GP data into Business Central online, typically through the Business Central assisted setup and cloud migration experience. The exact supported data set can change, so it should be validated against current Microsoft documentation during discovery. In general, standard migration focuses on core financial and operational data such as chart of accounts, fiscal periods, customers, vendors, items, inventory balances or quantities, open receivables and payables, and general ledger balances or supported transaction data. It does not automatically recreate every GP module, custom table, modified report, workflow, ISV solution, payroll setup, or historical operational process. GP payroll, complex fixed assets, advanced manufacturing, service workflows, multi-entity structures, custom integrations, and third-party add-ons need separate analysis.

Expect redesign, not a perfect copy of GP

Business Central is not Dynamics GP in a browser. Its account structure, dimensions, posting setup, number series, approval workflows, security model, reporting tools, and extension architecture are different. During migration, GP account segments are commonly redesigned into Business Central accounts and dimensions. This is an opportunity to simplify the chart of accounts, improve reporting dimensions, clean inactive records, standardize naming, and remove years of workarounds. Trying to duplicate GP exactly often increases cost and reduces the value of moving to Business Central.

Migration readiness checklist

Before running a migration, review the GP version and build, SQL Server health, database size, company list, fiscal calendar, chart of accounts, account segments, multicurrency requirements, inventory costing, open AR and AP, bank accounts, fixed assets, payroll, tax configuration, security roles, integrations, custom reports, modified forms, ISV products, audit and retention requirements, and month-end close processes. Also identify which historical data must be migrated, which can remain in GP read-only, and which should be moved to a data warehouse or reporting archive. For identity and access, plan Business Central users and permissions with Microsoft Entra ID groups where appropriate.

Recommended migration approach

A successful GP-to-Business-Central migration usually follows phases: assessment, solution design, sandbox configuration, trial migration, data validation, reporting redesign, integration build, user acceptance testing, training, cutover planning, go-live, and post-go-live support. The first migration should happen in a Business Central sandbox, not in production. Finance users should reconcile trial balances, customer and vendor aging, inventory values, open documents, bank balances, and key management reports. Only after the team signs off on configuration, migrated data, security, reports, and integrations should the production cutover be scheduled.

Choosing the right migration method

Use Microsoft’s standard GP migration tooling when your goal is to move supported core data into Business Central with minimal custom transformation. Use Business Central configuration packages, Excel import, APIs, RapidStart-style templates, or partner migration tools when data must be transformed, enriched, split, consolidated, or loaded into areas not covered by the standard tool. Use a custom migration approach when you have complex historical data, multiple GP companies, nonstandard account structures, heavy customizations, or industry-specific ISV tables. Many organizations use a hybrid approach: standard migration for core records, configuration packages for setup data, APIs for integrations, and a reporting archive for older GP history.

Reporting, Excel, Power BI, and historical GP data

Business Central includes list pages, account schedules/financial reports, analysis views, Excel integration, and Power BI options. The current Excel experience includes Open in Excel for analysis and Edit in Excel for authorized updates, subject to user permissions and governance. This is useful for controlled bulk updates, but it should not replace migration testing or master-data ownership. For historical GP reporting, some organizations keep GP available as read-only for a defined retention period, while others export GP data to SQL, Azure, Power BI, or another reporting repository. Decide this before go-live so auditors and finance users know where to find prior-year detail.

Integrations, automation, and Copilot-era capabilities

After migration, Business Central can connect with Outlook, Teams, Excel, Power BI, Power Automate, Power Apps, Dataverse, and third-party extensions from Microsoft AppSource. Copilot capabilities in Business Central and Microsoft 365 can assist with tasks such as analysis, content generation, and productivity workflows where enabled and licensed, but they do not replace ERP design, controls, reconciliation, or user training. Integration planning should include payment systems, banks, ecommerce, CRM, warehouse systems, payroll providers, document management, EDI, and any GP-era integrations that must be rebuilt using modern APIs or connectors.

Cutover and post-go-live support

The cutover plan should define the final GP transaction date, data freeze window, final migration run, reconciliation owners, approval process, user access changes, production environment setup, backups, and rollback criteria. After go-live, expect a stabilization period for user questions, report tuning, posting setup adjustments, permissions refinement, and integration monitoring. The best projects include finance leadership, IT, operations, and an experienced Business Central partner from the start.

Key takeaways

• Dynamics GP is still usable, but Microsoft’s support timeline makes a planned migration roadmap important before 2029.
• Business Central migration is not just a wizard-driven export/import; it requires data cleanup, account and dimension design, testing, training, and reconciliation.
• Use a current supported GP 18.x build and validate Microsoft’s latest migration-tool prerequisites before starting.
• Standard tools cover common core data, but payroll, fixed assets, advanced modules, ISV products, custom reports, integrations, and deep history often require separate migration or reporting strategies.
• A sandbox trial migration and finance-led validation are essential before production cutover.

If you are planning a Dynamics GP modernization project, IT Partner can help assess your GP environment, design the Business Central solution, run sandbox migrations, rebuild reports and integrations, and support your go-live. Start with our Dynamics 365 Business Central services or contact us for a migration readiness review.