Dynamics GP Is Ending: Your Migration Options, Honestly Compared

Microsoft Just Put a Date on It

Dynamics GP support ends December 31, 2029. Security patches continue until April 30, 2031. After that, you're on your own — no bug fixes, no tax table updates, no regulatory patches, no technical support from Microsoft.

If you're a CFO or controller running GP today, that timeline feels comfortable. 2029 is years away. But the ecosystem is already shrinking. The migration window isn't 2029. It's now through 2028, because the last 12 months before a deadline is when every GP shop tries to move at once — and every qualified implementation partner is booked solid.

This article is for finance and operations leaders at companies with 50 to 300 employees who know GP's clock is ticking but haven't committed to a direction yet.

What Happens If You Stay on GP

Staying on GP past 2029 isn't impossible. The software won't stop working on January 1, 2030. But here's what changes practically:

No more tax table updates. GP has historically shipped payroll tax updates multiple times a year. After end-of-support, those stop. You'll need a third-party payroll provider or manual updates — both add cost and risk.

No regulatory patches. Revenue recognition rules change. Lease accounting standards evolve. GP won't adapt. Your workarounds will multiply.

Shrinking partner ecosystem. GP partners are already migrating their own practices to Business Central. The number of consultants who actively work in GP is declining every quarter. Finding someone to customize a GP report or troubleshoot a Dexterity issue in 2028 will be harder and more expensive than it is today.

Hiring gets harder. New accountants and IT staff don't learn GP. They learn cloud-native ERPs. Running GP makes your finance team a harder hire.

Security risk accumulates. Security patches end April 2031. After that, any vulnerability discovered in GP's SQL Server integration, web client, or API layer stays unpatched. For companies with PCI DSS, SOC 2, or cyber insurance requirements, that's a material risk.

Integration brittleness. GP's integration story relies on eConnect, Web Services, and a SQL Server back-end. As the vendors around you modernize their APIs, maintaining GP integrations becomes custom middleware work — expensive and fragile.

Your Migration Options, Honestly Compared

There are four realistic paths for a GP shop in the 50–300 employee range.

1. Microsoft Dynamics 365 Business Central

The "stay in the family" option.

Strengths:

• Closest functional match to GP's accounting depth
• Native migration tooling from Microsoft (cloud migration tool supports GL, AP, AR, inventory, open POs/SOs)
• Deep Office 365 and Power BI integration
• Large partner ecosystem (the GP partners are moving here)

Weaknesses:

• Licensing adds up fast. Essentials is ~$70/user/month. Premium is $100/user/month. A 30-user company is looking at $25K–$36K/year in licensing alone
• Heavy customizations from GP (Dexterity mods, custom reports) don't migrate — they get rebuilt
• Implementation cost for a 50–150 user company typically runs $75K–$200K+

Best fit for: Companies deeply embedded in the Microsoft stack (Azure, O365, Power Platform) who value ecosystem continuity over cost.

2. Oracle NetSuite

The "move to cloud ERP" option.

Strengths:

• True multi-entity, multi-currency, multi-subsidiary out of the box
• Strong financial reporting (saved searches, financial report builder)
• Good fit for companies with complex revenue recognition or subscription billing

Weaknesses:

• Expensive. Base licensing starts around $999/month plus $99–$129/user/month. A 50-user company can easily hit $80K–$120K/year
• Customization (SuiteScript, SuiteFlow) requires NetSuite-specific developers
• Long implementation cycles — 6 to 12 months for mid-market is typical

Best fit for: Companies with $50M+ revenue, multi-subsidiary structures, or complex financial consolidation needs who can absorb the licensing cost.

3. SAP Business One

The "enterprise pedigree at SMB scale" option.

Strengths:

• Strong manufacturing and supply chain modules
• On-premise or SAP HANA Cloud deployment options
• SAP brand carries weight in certain industries

Weaknesses:

• The SAP ecosystem is expensive — implementation, licensing, and ongoing support
• Smaller partner network than Business Central or NetSuite in North America
• User interface feels dated compared to modern cloud ERPs

Best fit for: Manufacturing companies already in SAP's orbit or planning to grow into SAP S/4HANA eventually.

4. Odoo

The "open source, all-in-one" option.

Strengths:

• Dramatically lower licensing cost. Odoo Enterprise runs ~$24–$36/user/month. A 50-user company pays $14K–$22K/year — one-quarter to one-fifth of NetSuite or Business Central
• All modules included. No per-module licensing. Inventory, manufacturing, CRM, HR — all included
• Modern web UI. Your team learns it fast
• Open source core means full code access. Customizations are Python modules you own
• Strong international support (multi-currency, multi-language, 70+ country localizations)

Weaknesses:

• Accounting module is solid but less deep than GP or Business Central for complex US-specific scenarios. You'll likely keep a dedicated payroll provider like ADP or Gusto
• The Odoo partner ecosystem in North America is smaller than Microsoft's or Oracle's. Finding an experienced partner matters more
• Customizations require Python/JavaScript developers. Easier to hire than Dexterity or SuiteScript developers, but still a factor

Best fit for: Companies with 50–200 employees who want a full-featured ERP without six-figure annual licensing, especially in distribution, manufacturing, services, or e-commerce.

What an Odoo Migration Actually Looks Like

Since we do these migrations, here's what the process looks like for a typical 50–200 employee company moving from GP to Odoo.

Phase 1: Discovery and Scoping (2–4 weeks)

We map your current GP environment: which modules you use, what's customized, what integrations exist, and what your actual workflows look like. This phase produces a gap analysis and a migration plan.

Phase 2: Core Configuration and Data Migration Prep (4–6 weeks)

Chart of accounts mapped and configured in Odoo. Core modules set up: accounting, purchasing, inventory, sales, CRM — whatever your scope includes. Test data migration run with your actual GP data.

Phase 3: Custom Development and Integration (3–6 weeks, parallel with Phase 2)

Any custom reports, workflows, or integrations get built here. Common examples: EDI integration for distribution companies, custom pricing logic, industry-specific compliance reports, bank payment file format integration.

Phase 4: User Acceptance Testing (2–3 weeks)

Your team runs real scenarios in Odoo with migrated data. Month-end close simulation. Purchase order through receipt through AP through payment. This is where you find the gaps between "configured" and "works for us."

Phase 5: Go-Live and Cutover (1–2 weeks)

Final data migration, parallel run if your risk tolerance requires it, go-live, hypercare support for the first 2–4 weeks.

Total timeline: 3–5 months for a straightforward migration. 5–7 months if you have heavy customizations or complex integrations.

Total cost range: $40K–$120K for implementation, depending on scope and complexity, plus $14K–$22K/year in Odoo Enterprise licensing for 50 users. Compare that to $75K–$200K implementation plus $25K–$36K/year licensing for Business Central, or $100K–$250K implementation plus $80K–$120K/year for NetSuite.

The 3 Decisions That Determine Migration Success

1. Chart of Accounts: Migrate or Redesign?

Most GP charts of accounts are 15–20 years old. You have two options:

• Lift and shift your existing COA into Odoo. Faster migration, less disruption, but you carry forward structural debt.
• Redesign the COA for how you run the business today. Slower, requires more accounting team involvement, but you start clean.

Our recommendation: Redesign if your COA has more than 500 active accounts or if your CFO complains about reporting flexibility. Otherwise, migrate as-is and plan a COA cleanup in year two.

2. Data Migration: How Much History Do You Actually Need?

Every GP migration includes this conversation: "We need 10 years of transaction history in the new system." No, you don't. You need:

• Open transactions (unpaid invoices, open POs, pending receipts) — always migrate these
• Master data (customers, vendors, items, BOMs) — always migrate these
• Trial balances as of cutover date — always migrate
• Historical transactions — keep them accessible in GP (read-only) or archive to a reporting database

3. Internal Ownership: Who Runs This Project?

ERP migrations fail when they're treated as an IT project. This is a business project with technical components. You need:

• An executive sponsor (usually CFO or COO) who can make decisions and break tie votes
• A project lead from your side who knows the business processes — not someone from IT who's never closed the books
• Department leads who will own UAT for their area

Making the Call

If you're running Dynamics GP today, you have roughly 2–3 years to plan and execute a migration before the ecosystem pressure makes it urgent. The companies that start evaluating now will have better options and lower costs than the ones who start in 2028.

We run free migration assessments for companies considering the move from GP to Odoo. No pitch deck, no 47-slide presentation. A working session where we look at your GP environment, map it to Odoo, and give you a realistic scope and cost estimate.