A Dynamics GP to Business Central migration is no longer a “someday” project for finance leaders in the USA; it’s a countdown. Microsoft has formally retired Dynamics GP: new license sales have already stopped, product support ends on December 31, 2029, and security patches stop on April 30, 2031. For US businesses still running GP, the question isn’t whether to move, but how much value you can unlock by moving early instead of late. This guide from Shreeji Softinfo Consultancy LLP breaks down the five most important benefits, the licensing deadlines driving them, and the compliance details that matter specifically to American finance teams.
Microsoft Is Discontinuing Dynamics GP: What It Means for USA Licensing and Support
The biggest driver behind every GP to Business Central migration happening right now is simple: Microsoft has retired Dynamics GP. This isn’t a rumor or a soft nudge toward the cloud it’s a published lifecycle policy with fixed dates that affect your licenses, your updates, and your legal right to run the software
The official Dynamics GP end-of-life timeline
| Date | What changes for USA customers | |
| April 1, 2025 | No new customer sales of Dynamics GP perpetual licenses. | |
| April 2026 | No new customer sales of Dynamics GP subscription licenses. | |
| December 31, 2029 | Microsoft ends product enhancements, regulatory/tax updates and technical support for Dynamics GP. | |
| April 30, 2031 | Security updates/patches, if needed, end. Additional licensing/service-plan restrictions also take effect for applicable customers. |
What this means for licensing
If you hold perpetual licenses, you can legally keep running GP after 2031 but as a frozen, unpatched codebase with no path to add users and no support channel. If you’re on a subscription or SPLA agreement, the position is stricter: your right to use the software ends on April 30, 2031. Continuing to operate GP past that date is not a licensing option that exists.
What this means for ongoing support in the USA
From January 1, 2030, Microsoft stopped issuing payroll and tax table updates, SQL Server compatibility hotfixes, and regulatory compliance changes. For US organizations, that is the sharpest edge of the deadline: no more federal or state payroll tax tables, no updated 1099 forms, and no adjustments when IRS reporting requirements change. You also cannot escalate a defect, a data corruption issue, or a performance failure to Microsoft engineering. The 2030–2031 window is a narrow security-only runway, not a supported operating model.
Which version you’re on matters. Only the current release (v18.8) receives updates through the full window under Microsoft’s Modern Lifecycle Policy. Customers still on v18.1–18.5 must upgrade to stay eligible, and anyone on GP 2018 R2 or earlier falls under the older Fixed Lifecycle Policy, meaning support has already lapsed.
The commercial reality. Beyond Microsoft’s own timeline, the wider GP ecosystem is contracting. ISVs are winding down add-on development, experienced GP consultants across the USA are moving into Business Central practices, and annual enhancement-plan costs keep rising for a product receiving no new features. Every year you wait, the pool of people who can support your system gets smaller and more expensive.
Most mid-market ERP migrations take 2 to 3 months from project kick-off to go-live once you account for data cleanup, integration rebuilds, testing and training though a tightly scoped migration with clean data can complete in 4 to 6 weeks. Work backwards from 2029, and the sensible planning window is now, not 2028. Microsoft is actively encouraging Dynamics GP customers to evaluate Dynamics 365 Business Central as a modern cloud ERP path.
Benefit 1: Lower Total Cost of Ownership
GP carries costs that never appear on a single invoice: SQL Server licensing, on-premises hardware, the annual enhancement plan, VPN and remote-access infrastructure, backup systems, disaster recovery, and the IT hours spent keeping all of it alive.
Business Central replaces that stack with a predictable per-user subscription. There are no servers to refresh every four to five years, no upgrade projects that consume a quarter of your IT budget, and no downtime windows for patching.
Most organizations that complete a GP to Business Central migration see a meaningful drop in infrastructure spend within the first year and, just as importantly, they stop paying the hidden tax of deferred maintenance on aging hardware. For US finance teams, the shift from capital expenditure to a predictable operating expense also makes budgeting and forecasting considerably cleaner.
Benefit 2: Real-Time Reporting and a Faster Month-End Close
In GP, meaningful reporting usually means exporting to Excel, rebuilding the same pivot tables every month, and reconciling spreadsheets three people have already edited. Finance teams routinely lose several days close to this cycle.
Business Central delivers live financial data through built-in dimensions, account schedules, and native Power BI dashboards. Dimensions replace GP’s rigid segmented chart of accounts, letting you slice revenue by department, project, region, or customer without adding a single new GL account.
The result can be a significantly more efficient month-end close, with finance teams gaining faster access to real-time financial information and reducing manual reporting and reconciliation work. For US businesses reporting under GAAP or preparing for an audit, a lender review, or investor reporting that traceability from summary figure back to source transaction is worth as much as the time saved.
Benefit 3: Native Microsoft 365, Power BI and Copilot AI
This is where the gap between GP and Business Central widens with every release. Business Central was built inside the Microsoft cloud ecosystem, not bolted onto it.
- Outlook integration: brings Business Central customer and sales information into the Microsoft 365 workflow, reducing the need to switch between applications.
- Excel refresh: pulls live ERP data rather than a stale export.
- Power Automate and Power Apps: automate approvals, alerts and mobile workflows with no custom code.
- Copilot AI: drafts descriptions, suggests bank reconciliation matches, explains variances in plain language and flags ledger anomalies.
Business Central continues to receive significant cloud-first innovation across Microsoft 365, Power Platform, analytics and AI a release cadence Dynamics GP no longer participates in.
Benefit 4: Stronger Security and Automatic Updates
An unpatched, internet-connected ERP holding your entire financial history is a genuine risk, and after April 2031, that is exactly what Dynamics GP becomes.
Business Central Online benefits from Microsoft’s cloud security architecture: identity and access controls, encryption at rest and in transit, role-based permissions, managed infrastructure, and Microsoft’s broad compliance framework. For USA organizations, that framework covers the attestations buyers and auditors typically ask about including SOC 1 and SOC 2 with US-region data residency available through Microsoft’s American datacenters. Updates arrive automatically twice a year, so you are never the customer running a version nobody supports.
Benefit 5: Scalability Without Re-Platforming Again
Growth is where GP’s architecture starts to strain. New legal entities mean new company databases, intercompany consolidation becomes manual, and multi-currency handling gets fragile.
Business Central handles multi-entity, multi-currency and multi-location operations natively, with consolidation built in. Adding a subsidiary becomes a configuration task, not an infrastructure project. Users log in from a browser, tablet or phone, anywhere which matters for US companies operating across multiple states and time zones.
And because the platform extends through AppSource apps and modern extensions rather than intrusive code modifications, your customizations survive upgrades instead of blocking them. You migrate once, not every five years.
What Makes a GP to Business Central Migration Different in the USA
The Microsoft lifecycle dates are global, but the migration work is not. A few areas consistently take more attention on American projects than they do elsewhere:
- Sales and use tax: US sales tax is calculated at state, county, city and district level, and rates change constantly. Most US migrations pair Business Central with a tax engine such as Avalara AvaTax or Vertex through AppSource, replacing GP’s tax detail and tax schedule setup rather than porting it across.
- 1099 reporting: vendor 1099 boxes, minimum thresholds and historical amounts need to be mapped into Business Central’s IRS 1099 forms functionality and validated against a prior filing before go-live, not after.
- Payroll: Business Central has no native US payroll module. Most American organizations move payroll to a dedicated provider such as ADP, Paychex or Gusto and integrate at the GL level. This is a decision to make during assessment, because it can shape the whole chart of accounts.
- Banking and ACH: GP’s Electronic Funds Transfer setup, positive pay files and bank reconciliation formats need to be rebuilt against your US bank’s current specifications.
- US GAAP and audit readiness: fixed asset depreciation books, revenue recognition schedules and the audit trail your external auditors expect all need to be configured deliberately rather than inherited.
- Data residency: if your contracts or clients require US-hosted data, confirm the Business Central environment is provisioned in a United States Azure region at the outset moving it later is disruptive.
How Shreeji Softinfo Consultancy LLP Handles GP to Business Central Migration for USA Businesses
A migration succeeds or fails on preparation, not software. At Shreeji Softinfo Consultancy LLP, our approach is deliberately phased:
- Assessment: we audit your GP version, customizations, ISV add-ons, integrations and data quality to produce a realistic scope, cost and timeline.
- Data strategy: we decide together what moves (open transactions, master data, balances) and what stays archived, then cleanse before migrating rather than importing years of duplicate vendor records.
- Configuration and re-engineering: legacy GP customizations are re-evaluated; in many cases, native Business Central functionality replaces them outright, cutting long-term maintenance costs.
- US compliance setup: sales tax engine, 1099 mapping, payroll integration and bank file formats configured and tested against your existing US filings.
- Parallel testing and UAT: your finance team validates against known GP results before anyone commits to a cut-over date.
- Go-live and adoption: role-based training, hypercare support and post–go-live optimization, so the system is actually used, not just installed.
With deep Microsoft Dynamics experience across manufacturing, distribution, trading and services, our team has guided organizations through this exact transition, and we plan around your financial year, not ours.
Conclusion
The five benefits of a Dynamics GP to Business Central migration lower total cost of ownership, real-time reporting, native Microsoft AI and analytics, stronger security, and true scalability are compelling on their own. Combined with a fixed end-of-support date and a licensing cut-off you cannot negotiate, they turn a strategic option into a plan you should already be building.
The USA organizations that come out ahead won’t be the ones who waited the longest. They’ll be the ones who moved on their own schedule.
Ready to plan your migration? Contact Shreeji Softinfo Consultancy LLP for a Dynamics GP assessment and a tailored Business Central migration roadmap built for your US operations.
Frequently Asked Questions
Q: When does Microsoft Dynamics GP support officially end?
A: Microsoft ends product enhancements, regulatory and tax updates, and technical support for Dynamics GP on December 31, 2029. Security patches continue until April 30, 2031, after which GP is fully unsupported. These dates apply to USA customers exactly as they do worldwide.
Q: Is Microsoft still selling Dynamics GP licenses in the USA?
A: No. Microsoft discontinued new perpetual license sales on April 1, 2025, and ended new subscription license sales in April 2026. Existing customers can continue under current agreements until the lifecycle dates, but GP is closed to new business.
Q: Can I keep using Dynamics GP after support ends?
A: It depends on your license. Perpetual license holders can technically keep running GP after April 30, 2031, but with no security patches, no support, and no ability to add users. Customers on subscription or SPLA licensing must stop using and uninstall Dynamics GP after that date.
Q: How long does a GP to Business Central migration take?
A: A tightly scoped Dynamics GP to Business Central migration with clean data can be completed in 4 to 6 weeks, covering planning, configuration, data migration, testing and go-live. More complex environments, heavy customizations, multiple entities or several integrations typically run 2 to 3 months.
Q: How is a Business Central migration handled for US sales tax and 1099 reporting?
A: US sales tax is normally handled by connecting Business Central to a tax engine such as Avalara or Vertex rather than recreating GP’s tax schedules. Vendor 1099 data is mapped into Business Central’s IRS 1099 forms functionality and validated against a previous filing before go-live.
Q: Can I migrate my historical data from Dynamics GP to Business Central?
A: Yes. Microsoft provides migration tools for master data and balances, and open transactions can be brought across. Most organizations migrate open items plus one to two years of history and archive the remainder in a read-only database for audit and reporting.
Q: What happens to my GP customizations and ISV add-ons?
A: They must be re-evaluated rather than lifted across. Business Central uses a modern extension framework, and in many cases native functionality or an AppSource app replaces a legacy customization entirely, reducing long-term maintenance cost.