Microsoft Dynamics Migration & Upgrade Guide: Complete Overview

The Dynamics Migration Landscape

Microsoft's cloud-first strategy has driven a significant shift in how organizations manage their enterprise resource planning (ERP) systems. With on-premises support ending for legacy systems, thousands of organizations worldwide are evaluating their options for modernization. Whether running Dynamics GP, Dynamics NAV, Dynamics AX (now Dynamics 365 Finance and Operations), or Solomon (SL), companies face critical decisions about timing, budget allocation, architecture choices, and partner selection.

This guide provides a comprehensive overview of the migration landscape, helping you understand your options, plan realistic timelines, budget appropriately, and identify the partner expertise you'll need.

The Four Major Migration Paths

1. Dynamics GP to Business Central

Timeline: 4-8 months (typical SMB)
Cost: $50K-$250K (SMB); $250K-$500K (mid-market)
Complexity: Medium-High

Dynamics GP to Business Central is the most common migration path for small and mid-market organizations. GP has a 28-year history and still powers accounting operations for tens of thousands of companies globally. Unlike NAV (which is the direct predecessor to BC), GP requires more substantial reimplementation effort because BC represents a complete architectural rewrite.

Key considerations:

• Module mapping: GP's module structure (e.g., General Ledger, Accounts Payable, Accounts Receivable, Inventory, Manufacturing) doesn't align 1:1 with BC. Organizations must map processes and often reimagine workflows for cloud-native operations.
• Customizations: GP implementations typically carry 10-30 years of customizations. Most require simplification in BC; legacy custom logic often represents technical debt that modern cloud design eliminates.
• Data migration: Requires careful mapping of historical GL balances, open transactions, and legacy archives. Most successful projects migrate 3-5 years of detailed history and summarize older data.
• User base transition: GP users require training on fundamentally different UI paradigms. Cloud-first browser experience vs. rich desktop client shifts mental models.
• Reporting overhaul: GP's SQL Server Reporting Services architecture replaces with Power BI. A major undertaking that determines success perception among power users.

2. Dynamics NAV to Business Central

Timeline: 3-6 months (typical)
Cost: $30K-$150K (SMB); $150K-$300K (mid-market)
Complexity: Low-Medium

This is the most straightforward migration path. Dynamics NAV (launched 1983, evolved as C/Side platform) is Business Central's direct predecessor. Microsoft designed BC specifically to make NAV upgrades manageable by providing automated code translation, assisted setup wizards, and data migration frameworks.

Key considerations:

• Code conversion: C/AL code (NAV's native language) must convert to AL (Business Central's language). Microsoft's Conversion Toolkit handles 70-85% of code conversion automatically; remaining 15-30% requires manual review and refactoring.
• Version variance: NAV has multiple versions in the wild: NAV 2009, 2013, 2015, 2016, 2017, 2018. Upgrade complexity increases with version age. NAV 2018 conversions are straightforward; NAV 2009 requires significant translation work.
• Performance optimization: BC's modern SQL architecture requires rethinking complex queries optimized for old index strategies. Code that performed adequately in NAV may need re-architecture for cloud performance.
• Rapid iteration cycle: BC receives major updates every 6 months (spring/fall). Organizations must plan for continuous minor updates vs. NAV's annual update cycle, changing change management approaches.
• Cost advantage: Licensing costs often drop 30-50% for equivalent functionality as BC's cloud economics are superior to on-prem NAV licensing.

3. Dynamics SL (Solomon) to Business Central

Timeline: 5-9 months
Cost: $75K-$200K (typical)
Complexity: Medium

Solomon (SL) is less common than GP but has a solid installed base in professional services, construction, and project-based manufacturing. Support for SL ended in April 2021, creating urgency for migrations.

Key considerations:

• Project accounting expertise required: SL is strong in project-based accounting. Migrating organizations must ensure their BC partner understands project costing, billing, and intercompany transactions in project accounting contexts.
• Industry-specific configurations: Construction and professional services often have unique GL structures, project hierarchies, and revenue recognition rules built into SL. BC requires these to be explicitly configured.
• Limited partner pool: Fewer partners specialize in SL vs. GP/NAV migrations. Finding expertise is harder; partner selection becomes critical.
• Data complexity: SL typically has complex project hierarchies, resource allocations, and job costing structures that require careful translation to BC's project management framework.

4. Dynamics AX to Finance & Operations (D365 F&O)

Timeline: 8-18 months
Cost: $250K-$2M+
Complexity: High

AX migrations are the most complex and expensive. Dynamics AX (launched 2002) is a high-end, feature-rich ERP platform primarily used by mid-market and enterprise organizations in manufacturing, distribution, and complex supply chain environments.

Key considerations:

• Version matters hugely: AX 2009 vs. AX 2012 are vastly different. AX 2012 to F&O is more straightforward; AX 2009 requires extensive modernization work. Some organizations find it more practical to treat an AX 2009 migration as a net-new F&O implementation.
• X++ modernization: AX's native X++ language must be updated to current standards. Older X++ code patterns are often incompatible with modern F&O infrastructure. Complete codebase audits and refactoring are typical.
• LCS-based deployment: F&O deployments happen through Microsoft's Lifecycle Services (LCS), adding operational complexity and requiring new skillsets from operations teams.
• Scope creep risk is highest: AX's power and flexibility can lead organizations to attempt massive feature enhancements during migration. The most successful AX→F&O projects explicitly limit scope to essential functionality and defer enhancements to post-migration phases.
• Partner selection is critical: AX migrations require deep expertise in X++, supply chain functionality, manufacturing modules, and complex GL structures. Partner choices determine success/failure more than any other variable.

Timeline Frameworks by Project Type

Fast-Track Migrations (4-6 months)

For organizations willing to accept significant scope limitations and take moderate technical risks:

• Strict scope: Migrate core GL, AP, AR, Inventory only
• Minimize customizations: Accept 80% standard functionality
• Accelerated training: Compressed 4-week training cycle
• Phased data migration: Migrate 2-3 years of history initially, archive older data
• Limited reporting migration: Rebuild top 20 reports in Power BI; defer others
• Best for: Organizations with simple structures, low customization, and strong business readiness

Standard Migrations (6-12 months)

The baseline realistic timeline for most mid-market organizations:

• Full module migration: Typically GL, AP, AR, Inventory, Bank Rec, multi-entity
• Moderate customization support: 20-40% custom functionality
• Comprehensive training: 8-week training program with UAT
• Full data migration: 5+ years historical detail, complete master data cleanup
• Robust reporting: Top 50+ reports recreated in Power BI during project
• Post-go-live stabilization: 4-6 weeks intensive support
• Best for: Mid-market organizations with moderate complexity and standard change management maturity

Complex Enterprise Migrations (12-18+ months)

For organizations with high complexity:

• Multi-entity, multi-currency structures
• Complex supply chain, manufacturing, or project accounting
• Significant historical customizations
• Numerous third-party integrations
• Distributed teams across multiple geographies
• Heavy parallel run requirements (run old and new systems side-by-side for extended period)
• Best for: Enterprise organizations with complex structures that can't accept rapid timelines

Cost Breakdown and Budget Planning

Typical Cost Ranges (USD)

Cost Category	SMB (50-500 users)	Mid-Market (500-2,000 users)	Enterprise (2,000+ users)
Consulting & Implementation	$30K-$150K	$150K-$500K	$500K-$1.5M+
Data Migration Services	$5K-$15K	$15K-$50K	$50K-$150K+
Custom Development	$10K-$50K	$50K-$200K	$200K-$800K+
Testing & QA	$5K-$20K	$20K-$60K	$60K-$200K+
Training	$3K-$12K	$12K-$40K	$40K-$150K+
Licenses (Year 1)	$5K-$30K	$30K-$100K	$100K-$300K+
Infrastructure & Ops Setup	$2K-$8K	$8K-$25K	$25K-$80K+
Post-Go-Live Support (3 months)	$5K-$20K	$20K-$60K	$60K-$200K+
Total Estimated Range	$65K-$295K	$295K-$1.035M	$1.035M-$3.48M+

Often-Forgotten Costs

• Hidden third-party integrations: Many organizations discover undocumented integrations during migration planning. Budget 15-20% contingency for integration rework.
• Data cleanup: Migrating old systems often reveals master data issues (duplicate customers, conflicting GL accounts, missing GL balances). Expect $5K-$25K in data remediation costs.
• Interim infrastructure: Running dual systems during extended parallel runs costs extra cloud hosting or hybrid infrastructure. Can add $2K-$10K/month.
• Change management and communication: Often underfunded. Budget $10K-$50K for change management consulting, communications infrastructure, and executive coaching.
• Extended support and stabilization: Most projects budget 4-6 weeks of intensive post-go-live support. Budget $20K-$80K for this critical phase.

Key Decision Factors

System Age and Version

Older versions require longer, more expensive migrations. NAV 2018 vs. NAV 2009 can differ by 3-4 months and $50K-$75K in services costs.

Customization Burden

This is often the #1 hidden variable. Organizations with extensive customizations face harder choices: rewrite customizations in BC/F&O (expensive, delays go-live), or accept standard functionality and retire old features (organizational change).

Data Complexity

Clean, well-organized data accelerates migrations. Complex GL structures, legacy transaction hierarchies, and incomplete master data add weeks and significant costs.

User Base Size and Geographic Distribution

Distributed, large user bases require more comprehensive training programs, longer UAT periods, and more intensive post-go-live support.

Organizational Readiness

Organizations with strong project governance, clear change management discipline, and executive sponsorship execute migrations 2-3 months faster than those without.

Partner Capability and Availability

Right-sizing partner expertise to complexity is critical. Specialists in your industry vertical and specific product combination can reduce timelines by 25-40%.

Frequently Asked Questions