Migrating from Legacy ERP to Business Central: A Proven Roadmap

Part 9 of 11 in the Business Central Implementation Series

Published: January 2026 | Reading Time: 14 minutes

Introduction: The Legacy ERP Dilemma

Your current ERP system has served you well for years—maybe it's Dynamics NAV, QuickBooks Enterprise, Sage, SAP Business One, or even a custom-built system. But now you're facing mounting challenges:

• End-of-support deadlines: Your vendor is forcing an upgrade or discontinuing support

• Rising maintenance costs: Annual support fees increasing while functionality stagnates

• Integration nightmares: New tools (e-commerce, CRM, BI) won't integrate with your legacy system

• Cloud imperative: Remote work and multi-location operations demand cloud access

• Compliance pressure: New regulations requiring capabilities your system doesn't have

• Talent shortage: Hard to find IT staff who know your outdated platform

The Question Isn't "Should We Migrate?"—It's "How Do We Migrate Successfully?"

Microsoft Dynamics 365 Business Central offers a modern, cloud-first ERP platform with enterprise capabilities at SMB pricing. Migration from legacy systems is complex—data conversion, process re-engineering, user adoption, and business continuity all demand careful planning.

Successful migrations require experienced implementation partners who understand both legacy platforms and Business Central capabilities. Industry research shows that organizations working with Microsoft Solutions Partners achieve 30-40% faster time-to-value and higher user adoption rates.

This guide provides a proven roadmap for your migration journey—from assessment through go-live and beyond.

🔄 Quick Answer: When Should I Migrate from Legacy ERP to Business Central?

Migrate to Business Central when your legacy ERP reaches end-of-support, becomes too costly to maintain, lacks modern capabilities (cloud, mobile, AI), or creates integration and compliance challenges.

Key Migration Triggers:

1. End-of-Support Deadline – Vendor discontinuing support (e.g., NAV 2018 extended support ended Oct 2025)

2. Rising Maintenance Costs – Annual fees 18-22% of license cost with limited innovation

3. Cloud Imperative – Remote work, multi-location needs require cloud accessibility

4. Integration Challenges – New tools (Power Platform, e-commerce, CRM) won't integrate with legacy

5. Compliance Requirements – GDPR, SOX, industry regulations need modern controls

6. Talent Shortage – Difficult to find/retain staff with legacy platform expertise

7. Scalability Limits – Growth constrained by system capacity or performance

8. Competitive Disadvantage – Competitors leveraging modern ERP capabilities (AI, automation, analytics)

Migration Timeline Estimates:

• Dynamics NAV → BC: 8-16 weeks (moderate complexity, high automation)

• QuickBooks → BC: 12-20 weeks (data model differences, process re-engineering)

• Sage/SAP Business One → BC: 16-28 weeks (complex data, extensive customizations)

• Custom/Homegrown → BC: 24-36 weeks (poor documentation, data quality issues)

Success Factors: Experienced Microsoft Solutions Partner, 2-3 years historical data migration (not entire history), comprehensive testing (minimum 2 full UAT cycles), role-based training before go-live, and 8-12 weeks hypercare support.

💡 Pricing & Timeline Note
All cost estimates and timelines in this article reflect typical Business Central implementations as of January 2026.

• Geographic Context: Estimates based on Western Europe and North America markets

• Regional Variation: Implementation costs vary significantly by region (typically 30-60% lower in Eastern Europe, Asia-Pacific, and Latin America)

• Microsoft Licensing: Verify current prices at aka.ms/BCPricing as these change periodically

• Effort-Based Budgeting: Use the consulting hours estimates with your local partner's rates for accurate budgeting

These are reference estimates for planning purposes. Request detailed quotes from Microsoft Solutions Partners for your specific requirements.

The Migration Landscape: Understanding Your Options

Common Migration Scenarios

Scenario 1: Dynamics NAV to Business Central

• Complexity: Moderate (similar platforms)

• Timeline: 8-16 weeks

• Data Migration: 80% automated (table structure compatibility)

• Customization Migration: Review and re-implement (some custom code may not be needed with modern BC features)

• User Retraining: Minimal (familiar interface)

Scenario 2: QuickBooks to Business Central

• Complexity: Moderate-High (different data models)

• Timeline: 12-20 weeks

• Data Migration: Manual mapping required (chart of accounts restructuring)

• Process Re-engineering: Significant (QuickBooks is entry-level, BC offers advanced capabilities)

• User Retraining: Substantial (different navigation and terminology)

Scenario 3: Sage (50, 100, 300, X3) to Business Central

• Complexity: High (proprietary data structures)

• Timeline: 16-24 weeks

• Data Migration: Complex mapping (especially Sage X3 with manufacturing)

• Customization Analysis: Sage customizations often need complete rebuild

• User Retraining: Substantial (different workflow paradigms)

Scenario 4: SAP Business One to Business Central

• Complexity: High (enterprise-class system)

• Timeline: 20-28 weeks

• Data Migration: Complex (multi-level master data, extensive transactional history)

• Reporting Replication: SAP Crystal Reports must be redesigned for BC

• User Retraining: Substantial (different UI philosophy)

Scenario 5: Custom/Homegrown System to Business Central

• Complexity: Very High (unknown data quality, undocumented logic)

• Timeline: 24-36 weeks

• Data Migration: Extensive discovery required (data quality often poor)

• Business Process Documentation: Often doesn't exist (must reverse-engineer)

• User Retraining: Complete (no reference point)

Migration vs. Greenfield Implementation

Industry Best Practice: Migrate critical master data and 2-3 years of transactional history; archive older data in read-only format. This balances completeness with migration complexity while maintaining audit trails.

Phase 1: Assessment & Planning (3-4 Weeks)

Discovery Workshop (Week 1)

Objective: Understand current state and define migration scope.

Activities:

1. Current System Documentation:

• Platform version and edition

• Database size and growth rate

• Number of companies/locations/currencies

• User count (active vs. total licenses)

• Customizations inventory (reports, forms, workflows, integrations)

• Integration points (CRM, e-commerce, EDI, banking)

2. Data Quality Assessment:

3. Business Process Review:

• Map current workflows (quote-to-cash, procure-to-pay, order-to-fulfillment)

• Identify pain points and workarounds

• Document customizations: Are they still needed? (Often, no—BC's modern features may eliminate the need)

• Review reporting requirements (which reports are critical vs. nice-to-have)

4. Integration Inventory:

Gap Analysis (Week 2)

Objective: Compare current system capabilities to Business Central out-of-box functionality.

Gap Analysis Framework:

Functional Gaps:

Customization Analysis:

Integration Roadmap:

Migration Strategy Document (Week 3)

Deliverable: Comprehensive migration plan approved by stakeholders.

Contents:

1. Executive Summary

• Current system challenges

• Business case for Business Central

• Timeline and budget

• Risk mitigation plan

• Success criteria

2. Scope Definition

3. Data Migration Plan

4. Cutover Plan

5. Training Plan

Project Planning (Week 4)

Project Timeline:

Project Team:

Budget:

Phase 2: Business Central Configuration (5 Weeks)

Week 5-6: Foundation Setup

Company Configuration:

Navigate: Companies → Create New

General Information:
  - Company Name: [Your Company Inc.]

Chart of Accounts:

Master Data Templates:

Week 7-8: Module Configuration

Sales & Receivables:

Purchase & Payables:

Inventory Management:

Manufacturing (if applicable):

Week 9: Custom Development & Integrations

Custom Development Projects:

Integration Development:

Phase 3: Data Migration (4 Weeks)

Week 10-11: Migration Script Development

Migration Tools:

Migration Script Development Process:

Script 1: Chart of Accounts

Script 2: Customers

Script 3: Customer Ledger Entries

Scripts 4-10: Similar development for:

• Vendors (650 records)

• Vendor Ledger Entries (open invoices)

• Items (4,200 SKUs)

• BOMs (320 production BOMs)

• Inventory Ledger Entries (opening balances by location)

• Open Sales Orders (current orders in process)

• Open Purchase Orders (expected receipts)

Week 12: Migration Testing

Test Migration Cycle 1 (Week 12, Monday):

Issue Log Example:

Test Migration Cycle 2 (Week 12, Thursday):

Phase 4: User Training (2 Weeks)

Week 13: Super User Training

Day 1: BC Fundamentals

• BC Navigation (Role Center, search, favorites)

• Common tasks (creating orders, posting journals, running reports)

• Keyboard shortcuts and efficiency tips

• Personalization (customize your workspace)

Day 2: Module Deep Dive

• Finance team: G/L, AR, AP, Bank Reconciliation

• Warehouse team: Receipts, Putaway, Picks, Shipments, Inventory Journals

• Sales team: Quotes, Orders, Credit Memos, Customer Management

• Purchasing team: Requisitions, Purchase Orders, Vendor Management

Day 3: Advanced Topics & Troubleshooting

• Dimension usage (department/project costing)

• Reporting and analytics (filters, sorting, exporting)

• Error messages and resolution

• Where to find help (in-app help, knowledge base, support)

Day 4: Go-Live Support Preparation

• Common user questions (and answers)

• Escalation process (when to call implementation partner vs. handle internally)

• Week 1 support schedule (super users on call)

Week 14: End User Training

Role-Based Training Sessions (see Phase 1 training plan):

• Smaller groups (8-10 users per session)

• Hands-on exercises with real scenarios

• Practice in sandbox (replicate their actual work)

• Q&A and open discussion

Training Materials Provided:

• User guides (PDF and online, 20-40 pages per role)

• Video tutorials (50+ videos, 3-7 minutes each, searchable library)

• Quick reference cards (laminated, desk reference)

• FAQ knowledge base (continuously updated)

Phase 5: User Acceptance Testing (2 Weeks)

Week 15-16: UAT Execution

UAT Objectives:

• Validate BC configuration matches requirements

• Ensure data migration accuracy

• Confirm integrations working correctly

• Train users on real system before go-live

• Build confidence and identify any last-minute issues

UAT Test Plan:

Test Scenario 1: Quote-to-Cash Process

Test Case: Create quote, convert to order, ship, invoice, receive payment

Steps:
  1. Sales rep creates sales quote for existing customer
  2. Add 5 items with different pricing (standard, discount, promotional)
  3. Convert quote to sales order
  4. Check inventory availability (should warn if insufficient stock)
  5. Warehouse picks and ships order
  6. Post shipment (creates invoice)
  7. Send invoice via email to customer
  8. Receive payment and apply to invoice
  9. Verify payment posted to G/L and bank account
  
Expected Results:
  ☐ Quote creates correctly with accurate pricing
  ☐ Order conversion preserves all data
  ☐ Inventory allocated and reduced upon shipment
  ☐ Invoice matches order exactly
  ☐ Email sends successfully with PDF attachment
  ☐ Payment applies correctly, customer balance = 0
  ☐ G/L entries correct (revenue, COGS, cash)

Tester: Sales Rep + Warehouse User + AR Specialist
Duration: 45 minutes
Status: [PASS | FAIL | BLOCKED]
Issues Found: [List any problems encountered]

Test Scenarios 2-20: Cover all critical business processes:

• Procure-to-Pay (requisition → PO → receipt → invoice → payment)

• Inventory Receiving (PO receipt, quality check, putaway)

• Production Order (material consumption, routing, output posting)

• Month-End Close (depreciation, accruals, reconciliations)

• Sales Return (RMA, credit memo, inventory return)

• Transfer Order (warehouse-to-warehouse inventory movement)

• New Customer Setup (credit check, terms, pricing)

• New Vendor Setup (onboarding workflow)

• Bank Reconciliation (import bank feed, match transactions)

• Financial Reporting (P&L, Balance Sheet, Cash Flow)

• Inventory Cycle Count (physical inventory, adjustments)

• Sales Commission Report

• Purchase Price Variance Analysis

• Customer Aging Report

• Inventory Valuation Report

• Budget vs. Actual Report

• Dimension-Based Costing Reports

• Multi-Currency Transactions

• Intercompany Transactions

• Integration Testing (e-commerce orders, CRM sync)

UAT Issue Resolution:

Phase 6: Go-Live & Cutover (1 Week)

Pre-Go-Live Checklist (Week 17, Monday-Thursday)

Final Preparations:

Cutover Weekend (Week 17, Friday-Sunday)

Friday Evening (5:00 PM - 11:00 PM):

Saturday (9:00 AM - 6:00 PM):

9:00 AM: Detailed data validation
  - G/L: Trial balance matches legacy
  - AR: Customer balances match, aging reports reconcile
  - AP: Vendor balances match
  - Inventory: Item quantities and values match by location
  - Open Orders: All in-process orders present

11:00 AM: Super user testing
  - 8 super users log in simultaneously
  - Execute test scenarios (create order, post invoice, etc.)
  - Verify workflows functioning
  - Confirm reports generating correctly

1:00 PM: Lunch break

2:00 PM: Issue resolution
  - Address any discrepancies found
  - Rerun import scripts if necessary (rollback and reload)
  - Document workarounds for minor issues

4:00 PM: Final reconciliation
  - All balances confirmed matching legacy
  - All critical issues resolved
  - Test transactions posted and rolled back (ensure posting works)

5:00 PM: Go/No-Go decision checkpoint
  - Steering committee reviews status
  - Criteria for GO: 95%+ confidence, all critical issues resolved
  - Criteria for NO-GO: Data integrity concerns, major functionality broken
  - Decision: [GO | NO-GO]

Sunday (10:00 AM - 4:00 PM):

10:00 AM: Final system checks
  - User access verified (all employees can log in)
  - Integrations tested (place test e-commerce order)
  - Email functionality confirmed
  - Printer connectivity verified

12:00 PM: Documentation finalization
  - Known issues documented (workarounds communicated)
  - Support procedures reviewed
  - On-call schedule confirmed

2:00 PM: Final go/no-go decision
  - Executive sponsor approval
  - Confidence level: [%]

Go-Live Monday (Week 18, Day 1)

Day 1 Timeline:

7:00 AM: Support team on-site (Implementation partner + Super Users)
  - Set up support "command center" (conference room)
  - Laptops ready, phone lines open
  - Issue tracking spreadsheet prepared

8:00 AM: Employees arrive, begin using BC
  - Super users at each department (hands-on coaching)
  - First transactions: Sales orders, PO receipts

9:00 AM: First hour checkpoint
  - Issue count: [X critical, Y minor]
  - System performance: [Good | Concerns]
  - User sentiment: [Confident | Struggling | Frustrated]

12:00 PM: Lunch debrief
  - Review morning issues
  - Identify patterns (common user questions)
  - Update FAQ document in real-time

3:00 PM: Afternoon checkpoint
  - Cumulative transactions: [X orders, Y invoices posted successfully]
  - Critical issues: [Resolved | In progress]

5:00 PM: End of Day 1 debrief
  - Success metrics: [X% of planned transactions completed]
  - Issue summary: [Y issues logged, Z resolved]
  - Plan for Day 2: [Focus areas]

Phase 7: Post Go-Live Support (12 Weeks)

Week 1-2: Intensive Support (On-Site)

Support Model:

• Implementation partner consultant on-site full-time (5 days/week)

• Super users available full-time

• Support hours: 7:00 AM - 6:00 PM

• After-hours on-call: Critical issues only

Focus Areas:

• Answer user questions immediately (don't let frustration build)

• Identify process improvements (BC way vs. legacy way)

• Monitor system performance (any slowdowns or errors)

• Fine-tune configuration (adjust settings based on real usage)

• Update training materials (FAQ additions)

Daily Metrics:

Week 3-4: Transition to Remote Support

Support Model:

• Implementation partner consultant remote (available via phone/Teams)

• Super users continue in-person support

• Support hours: 8:00 AM - 5:00 PM

• Response time: <2 hours for critical, <8 hours for normal

Focus Areas:

• Month-end close (first full month in BC)

• Financial reporting validation (compare BC reports to legacy)

• Integration monitoring (e-commerce, CRM data flow)

• Performance optimization (identify slow queries, large reports)

Week 5-8: Optimization Phase

Support Model:

• Implementation partner consultant available on-demand

• Super users handle 80% of questions

• Weekly check-in calls (30 minutes)

Focus Areas:

• Process refinement (eliminate workarounds, implement BC best practices)

• Additional training (advanced features, power user techniques)

• Report development (custom reports identified during go-live)

• Integration enhancements (additional automation opportunities)

Week 9-12: Handoff to Client

Support Model:

• Super users fully self-sufficient

• Implementation partner available for escalations only

• Monthly review calls (1 hour)

Focus Areas:

• Knowledge transfer (Partner documents all custom code, configurations)

• Support plan transition (move to standard maintenance agreement)

• Phase 2 planning (additional modules, integrations, or locations)

• Continuous improvement recommendations

Critical Success Factors

1. Executive Sponsorship

Why It Matters:

• Budget authority for scope changes

• Decision-making when trade-offs required

• User adoption enforcement (using BC is not optional)

• Removes organizational roadblocks

Best Practice: CFO or COO as executive sponsor, reviews project weekly.

2. Dedicated Project Manager

Why It Matters:

• Single point of coordination (avoids confusion)

• Keeps project on timeline

• Manages stakeholder communication

• Tracks issues to resolution

Best Practice: Internal PM (50% time commitment minimum), strong relationship with implementation partner PM.

3. Data Quality

The #1 Reason Migrations Fail: Poor data quality discovered mid-project.

Mitigation Strategy:

• Data assessment in Phase 1 (before committing to timeline)

• Data cleanup before extraction (fix in legacy system)

• Automated validation scripts (catch errors early)

• Accept imperfection (80/20 rule: fix critical issues, document the rest)

4. User Buy-In

Why It Matters:

• Change resistance can derail project

• Users find workarounds instead of learning new system

• Low adoption = ROI not achieved

Mitigation Strategy:

• Involve users in design decisions (they're more committed to what they help build)

• Communicate benefits early and often (what's in it for them)

• Celebrate early wins (post success stories)

• Gamify adoption (leaderboard for who processes most orders in BC first week)

5. Realistic Timeline

Why It Matters:

• Rushed implementations lead to errors, poor training, user frustration

• Overly conservative timelines lose momentum

Industry Best Practice Timelines:

• Small SME (10-25 users, simple processes): 12-16 weeks

• Mid-Size SME (25-75 users, moderate complexity): 18-24 weeks

• Complex SME (75+ users, manufacturing, multi-location): 24-36 weeks

Red Flags:

• "We need to go live in 6 weeks" (not realistic unless very simple)

• "Take as long as you need" (project will drift, lose focus)

Common Pitfalls & How to Avoid Them

Pitfall 1: Scope Creep

What It Looks Like:

• "While we're migrating, let's also implement advanced warehouse management"

• "Can we add e-commerce integration too? How about EDI?"

• Project timeline doubles, budget overruns

How to Avoid:

• Strict scope control: "In scope" vs. "Phase 2"

• Change request process: Document, estimate, get approval before proceeding

• Deliver core migration first, enhancements later

Pitfall 2: Inadequate Testing

What It Looks Like:

• UAT rushed or skipped ("we'll test in production")

• Go-live issues that should have been caught in testing

• Loss of confidence, demands to roll back

How to Avoid:

• Allocate 2 weeks for UAT (non-negotiable)

• Super users must test their own scenarios (not just implementation partner)

• Test migrations: Minimum 2 full test cycles before production

Pitfall 3: Training Shortcuts

What It Looks Like:

• "We'll train as we go after go-live"

• Users expected to figure it out from online help

• Productivity plummets week 1, users frustrated

How to Avoid:

• Role-based training before go-live (not optional)

• Hands-on exercises (not just watching demos)

• Training materials available 24/7 (videos, guides, FAQs)

• Super users prepared to coach (not just answer questions)

Pitfall 4: Underestimating Change Management

What It Looks Like:

• Focus only on technical migration, ignore people side

• Users resist new system, find workarounds, complain

• Benefits not realized despite successful technical migration

How to Avoid:

• Communication plan: Monthly updates during project

• Involve users early (design decisions, process review)

• Celebrate wins (success stories, recognition)

• Leadership reinforcement (executives use BC, talk about it positively)

Post-Migration: Ongoing Support & Optimization

Month 1-3: Stabilization

Focus: Ensure system stability, resolve lingering issues.

Activities:

• Weekly check-ins with super users

• Monitor system performance (slow queries, bottlenecks)

• Refine processes (eliminate workarounds)

• Additional training (advanced features)

Month 4-6: Optimization

Focus: Maximize BC value, improve efficiency.

Activities:

• Process automation opportunities (Power Automate workflows, approval workflows)

• Complex business logic (AL extensions, codeunit development)

• Advanced reporting (Power BI dashboards, custom BC reports)

• Integration enhancements (API connections, real-time data)

Month 7-12: Expansion

Focus: Add capabilities beyond initial scope.

Activities:

• Additional modules (Service Management, Advanced Warehouse)

• Additional locations (multi-site rollout)

• Additional companies (subsidiaries, acquisitions)

• Additional integrations (EDI, e-commerce platforms)

Ongoing: Continuous Improvement and Support

Post-Implementation Support Options:

Work with your implementation partner to establish an ongoing support plan that fits your needs:

Typical Support Tiers:

• Basic Support: Email support with 24-48 hour response times, quarterly health checks

• Standard Support: Phone and email support with faster response times (4-8 hours), monthly reviews, allocated hours for minor changes

• Premium Support: Priority support with 1-2 hour response times, dedicated consultant, proactive monitoring, included hours for ongoing optimization

Support Activities:

• System health monitoring and performance optimization

• Business Central update management (testing and deployment)

• User training refreshers and advanced feature education

• Minor configuration changes and report development

• Integration monitoring and troubleshooting

• License optimization and usage analysis

Choosing the Right Support Level:

• Consider your internal IT capabilities (less internal expertise = higher support tier needed)

• Evaluate system criticality (mission-critical systems warrant premium support)

• Plan for growth (expansion plans may require higher ongoing support)

Many organizations start with standard support post-go-live and adjust based on actual needs over the first 6-12 months.

❓ Frequently Asked Questions (FAQ)

1. Should I migrate from Dynamics NAV to Business Central?

Answer: Yes, migration from Dynamics NAV to Business Central is highly recommended, especially if you're on NAV 2009-2018, as Microsoft has ended mainstream support and offers limited extended support. Business Central provides modern capabilities, cloud benefits, and long-term viability that NAV cannot match.

Why Migrate from NAV to Business Central?

1. Support and Viability Concerns

NAV Support Timeline:

Impact of Unsupported Systems:

• No security patches or bug fixes (compliance and security risks)

• No new features or improvements

• Increasing difficulty finding NAV-skilled consultants and developers

• ISV (Independent Software Vendor) apps for NAV discontinued

• Liability in case of data breach or system failure

• Regulatory compliance risks (many frameworks require vendor-supported software)

2. Business Central Advantages Over NAV

Modern Architecture:

• Cloud-First: SaaS deployment with 99.9% SLA, geo-redundant backups, auto-scaling

• Multi-Tenancy: Manage multiple companies/entities efficiently

• AL Extensions: Modern development framework (vs. C/AL in NAV)

• API-First Design: RESTful APIs for integrations (vs. web services in NAV)

Advanced Capabilities NAV Lacks:

Cost Comparison (5-Year TCO for 50 users):

Dynamics NAV (On-Premises):

• Software licensing: $120,000 (perpetual + 18% annual maintenance)

• Annual maintenance: $21,600/year × 5 = $108,000

• Server infrastructure: $50,000 (hardware refresh)

• SQL Server licensing: $25,000

• IT staff time (maintenance, patches, backups): $30,000/year × 5 = $150,000

• Disaster recovery/backup: $10,000/year × 5 = $50,000

• Total 5-Year Cost: $503,000

Business Central (Cloud SaaS):

• Subscription: $70/user/month × 50 × 12 months × 5 years = $210,000

• Implementation partner support (annual retainer): $20,000/year × 5 = $100,000

• No infrastructure costs (included)

• Minimal IT staff time (Microsoft manages infrastructure): $5,000/year × 5 = $25,000

• Total 5-Year Cost: $335,000

Savings: $168,000 over 5 years (33% reduction)

3. Migration Complexity: NAV to BC

Good News: NAV to BC is Easier Than Other Migrations

Why NAV Migrations Are More Straightforward:

• Common Heritage: BC is NAV's direct successor; many table structures identical

• Data Mapping: 70-80% of NAV tables map directly to BC equivalents

• Automated Tools: Microsoft Cloud Migration Tool automates much of data conversion

• Code Migration: C/AL customizations can be converted to AL (though re-evaluation recommended)

• User Familiarity: UI very similar (Role Centers, navigation patterns)

NAV to BC Migration Timeline (50-100 users, moderate customizations):

4. Customization Considerations

NAV Customizations: Migrate, Replace, or Eliminate?

Approach:

Step 1: Inventory NAV Customizations

• Custom reports (how many? which are critical?)

• Modified standard pages/forms (what changes? why?)

• Custom tables and fields (business-specific data)

• Workflow customizations (approvals, notifications)

• Integration customizations (EDI, e-commerce, CRM)

Step 2: Evaluate Each Customization

Decision Matrix:

Cost Implications:

• Migrate (rebuild): $5,000-$20,000 per customization (AL development time)

• Replace (AppSource): $20-$200/user/month for ISV apps

• Replace (Power Platform): Included with M365 licenses (no additional cost)

• Eliminate: $0 (if BC standard functionality sufficient)

Best Practice: Rebuild only business-critical customizations; leverage BC standard features and AppSource apps for everything else. Typical result: Reduce customizations by 50-70%.

5. Data Migration Strategy

What to Migrate from NAV:

Master Data (Full migration recommended):

• Chart of Accounts (review and optimize structure)

• Customers (active + inactive with balances)

• Vendors (active + inactive with balances)

• Items (active + discontinued if transaction history migrated)

• Fixed Assets (all assets in service)

• Bank Accounts

• Dimensions (review dimension structure; BC supports more sophisticated dimension framework)

Transactional Data (Partial migration):

• Migrate: Last 2-3 fiscal years (balances, open documents, transaction history for trending)

• Archive: Older data in NAV read-only instance or data warehouse for audits

• Why Partial: Reduces migration complexity and BC database size; older data rarely accessed

Opening Balances:

• General Ledger: As of go-live date (reconcile to NAV trial balance)

• AR/AP: Open invoices and payments (aged summaries match)

• Inventory: On-hand quantities and values (reconcile to physical count)

Microsoft Cloud Migration Tool:

What It Does:

• Automates data extraction from NAV database

• Maps NAV tables to BC tables (using Microsoft's predefined mappings)

• Converts data types and formats

• Handles company/tenant creation in BC

• Provides data validation reports

What It Doesn't Do:

• Migrate customizations (must be manually rebuilt)

• Fix data quality issues (garbage in, garbage out)

• Optimize chart of accounts or master data structure

• Migrate non-standard fields (custom tables require manual mapping)

Tool Limitations:

• Only supports NAV 2013 R2 and later (earlier versions require intermediate upgrade)

• On-premises NAV to BC Online only (not on-prem BC)

• Requires Azure subscription and technical expertise to configure

6. User Training Needs

Training for NAV Users Migrating to BC:

Good News: Minimal retraining needed for core functionality (80-90% of NAV users comfortable within 1-2 weeks).

What's Familiar:

• Role Centers (nearly identical layout)

• Navigation (departments, search, favorites)

• Core transactions (sales orders, purchase orders, journals)

• Posting processes (similar workflows)

What's New (Training Required):

Total Training Estimate for NAV Users:

• End Users: 8-12 hours (vs. 16-24 for new-to-ERP users)

• Super Users: 16-24 hours (deep dive on new features)

• Administrators: 24-40 hours (cloud admin, extensions, APIs)

7. When NOT to Migrate from NAV

Scenarios Where Staying on NAV (Temporarily) Makes Sense:

Heavily Customized NAV with Limited Budget:

• If NAV has $200K+ in custom code critical to business operations

• Migration cost would be $300K-$500K to rebuild customizations

• Consider: Stay on NAV in extended support while budgeting for phased BC migration over 2-3 years

Very Small Organization (<5 users, simple needs):

• If current NAV usage minimal (basic GL, AR/AP only)

• BC subscription ($70/user/month) may be more expensive than NAV perpetual license already paid

• Consider: Evaluate lower-cost solutions (QuickBooks Online, Xero) or stay on NAV as long as feasible

Pending Merger/Acquisition:

• If company being acquired or merging within 12 months

• New parent company may have different ERP strategy

• Consider: Delay migration until acquisition finalizes

NAV 2017/2018 with Recent Customization Investment:

• If significant customizations recently developed (last 1-2 years)

• Still on extended support until 2026

• Consider: Plan migration for 2026-2027, maximizing recent investment

8. Migration ROI

Expected ROI from NAV to BC Migration:

Benefits (Annual, 50-user example):

• IT infrastructure savings (servers, SQL licensing, maintenance): $40,000-$60,000

• Productivity improvements (faster processes, better reporting): $30,000-$50,000

• Reduced support costs (cloud managed by Microsoft): $15,000-$25,000

• New capabilities enabling revenue growth (e-commerce integration, mobile sales): $50,000-$100,000

• Total Annual Benefits: $135,000-$235,000

Costs (50-user migration):

• Implementation (partner fees, data migration, training): $150,000-$250,000

• BC subscription (first year): $42,000 (50 users × $70/month × 12)

• Internal labor (project team time): $30,000-$50,000

• Total First-Year Cost: $222,000-$342,000

Ongoing Annual Costs:

• BC subscription: $42,000

• Partner support retainer: $20,000-$30,000

• Internal admin time: $15,000-$25,000

• Total Annual Ongoing: $77,000-$97,000

ROI Calculation (5-Year):

• Total Benefits (5 years): $135K-$235K × 5 = $675,000-$1,175,000

• Total Costs (5 years): $222K-$342K + ($77K-$97K × 4) = $530,000-$730,000

• Net Benefit: $145,000-$445,000

• ROI: 27-61% over 5 years

• Payback Period: 18-30 months

Conclusion: Should You Migrate?

✅ YES, migrate from NAV to BC if:

• On NAV 2016 or earlier (unsupported)

• On NAV 2017/2018 with <18 months until extended support ends

• Need cloud capabilities (remote work, multi-location, mobile)

• Want modern features (AI, Power Platform, embedded analytics)

• Struggling with NAV maintenance costs and aging infrastructure

• Finding difficulty hiring/retaining NAV expertise

⏸️ MAYBE, consider waiting if:

• On NAV 2017/2018 with support until 2026 and recent customization investment

• Pending merger/acquisition or business restructuring

• Need time to budget for migration (plan for 2025-2026)

❌ NO, don't migrate from NAV if:

• NAV meeting all business needs with minimal customizations

• Very small operation (<5 users) with simple requirements and alternative is more cost-effective

• Planning business wind-down or sale within 2-3 years

Bottom Line: For most organizations, NAV to BC migration is inevitable and advisable. The question is timing—and sooner is generally better than later, given Microsoft's roadmap and support timelines.

2. How much does it cost to migrate from QuickBooks to Business Central?

Answer: QuickBooks to Business Central migration costs typically range from $50,000 to $200,000 depending on organization size, data complexity, customization needs, and implementation approach. This includes software licensing, implementation services, data migration, training, and project management.

Detailed Cost Breakdown:

1. Business Central Licensing (Annual Subscription)

BC Essentials ($70/user/month):

• Financial Management (GL, AR, AP, bank rec)

• Sales and Purchase order management

• Basic Inventory

• Jobs (project accounting)

• Best for: Most small businesses migrating from QuickBooks

BC Premium ($100/user/month):

• All Essentials features PLUS:

• Service Management

• Advanced Manufacturing

• Advanced Warehouse Management

• Best for: Manufacturing or service companies

Team Members ($8/user/month):

• Read-only access, limited write capabilities

• Timesheets, expense reports, approvals

• Best for: Employees who need limited system access

Example Licensing Cost (25 users: 15 Full, 10 Team Members):

• 15 × $70 × 12 = $12,600/year

• 10 × $8 × 12 = $960/year

• Total Year 1 Subscription: $13,560

2. Implementation Services (Partner Fees)

Small Business Migration (10-25 users, QuickBooks Pro/Premier):

Medium Business Migration (25-100 users, QuickBooks Enterprise):

3. Data Migration Costs

QuickBooks to BC Data Challenges:

Chart of Accounts Restructuring:

• QuickBooks: Simpler, often unstructured account numbering

• Business Central: Requires standardized numbering and account types

• Effort: 10-20 hours for mapping and restructuring ($1,500-$4,000)

Customer/Vendor Master Data:

• QuickBooks: Basic fields (name, address, terms)

• Business Central: More detailed (credit limits, payment methods, dimensions, pricing groups)

• Effort: 20-40 hours for data cleanup and enrichment ($3,000-$8,000)

Item Master Complexity:

• QuickBooks: Basic item records (description, cost, price)

• Business Central: Units of measure, item categories, replenishment systems, costing methods

• Effort: 30-60 hours for 1,000-5,000 items ($4,500-$12,000)

Historical Transaction Migration:

• QuickBooks: 2-3 years of invoices, bills, payments (typical migration scope)

• Effort: 40-80 hours for extraction, transformation, loading, validation ($6,000-$16,000)

• Alternative: Migrate opening balances only (GL, AR, AP); keep QuickBooks read-only for history (saves $5,000-$12,000)

Total Data Migration Costs: $15,000-$40,000 (depending on data volume, quality, and historical scope)

4. Training Costs

QuickBooks Users Need Substantial Retraining:

QuickBooks is entry-level accounting software; Business Central is mid-market ERP. Users accustomed to QuickBooks simplicity need comprehensive training on BC's more sophisticated functionality.

Training Requirements by Role:

Training Delivery:

• Instructor-led sessions (in-person or virtual): Most effective for complex topics

• E-learning modules (Microsoft Learn): Supplement formal training

• Hands-on sandbox practice: Required (2-4 weeks before go-live)

5. Customization and Integration Costs

Common Customizations for QuickBooks Migrations:

Custom Reports:

• QuickBooks users often have customized reports (P&L, balance sheet formats, management reports)

• BC alternative: Power BI reports ($2,000-$8,000 for 5-10 custom reports)

Integrations (replacing QuickBooks ecosystem):

Total Integration Costs: $10,000-$40,000 (depending on number of integrations and complexity)

6. Internal Labor Costs

Your Team's Time Investment:

7. Additional Costs

Contingency (10-15% of total budget):

• Unexpected data issues, scope changes, extended testing

• Cost: $8,000-$25,000

Post-Go-Live Support (Hypercare, 4-8 weeks):

• Partner support: $15,000-$30,000

• Internal overtime: $5,000-$10,000

• Total: $20,000-$40,000

Total Migration Cost Summary:

Small Business (10-25 users, QuickBooks Pro/Premier):

Medium Business (25-100 users, QuickBooks Enterprise):

Cost-Saving Strategies:

1. Limit Historical Data Migration:

• Migrate opening balances only (GL, AR, AP, Inventory) instead of 2-3 years of transactions

• Keep QuickBooks read-only for historical reporting

• Savings: $10,000-$25,000

2. Leverage Standard BC Functionality:

• Avoid custom reports; use Power BI templates

• Use AppSource apps instead of custom development

• Savings: $10,000-$30,000

3. Phased Training Approach:

• Train super-users; they train peers (train-the-trainer model)

• Use Microsoft Learn for self-paced basics

• Savings: $5,000-$15,000

4. Phased Implementation:

• Go-live with core finance and order management first

• Add advanced features (service management, advanced warehouse) in Phase 2

• Spreads cost over time; reduces initial complexity

ROI of QuickBooks to BC Migration:

Benefits (Annual, 25-user example):

• Productivity improvements (automation, workflows): $30,000-$50,000

• Better inventory management (reduced stockouts, overstock): $20,000-$40,000

• Scalability (support growth without additional software): $15,000-$30,000

• Improved reporting and decision-making: $10,000-$25,000

• Multi-company/multi-currency (if applicable): $20,000-$50,000

• Total Annual Benefits: $95,000-$195,000

Payback Period: 12-24 months (typical for QuickBooks to BC migration)

When QuickBooks to BC Migration Makes Sense:

✅ Migrate from QuickBooks if:

• Outgrowing QuickBooks Enterprise limits (users, list size, features)

• Need multi-company consolidation (QuickBooks lacks robust consolidation)

• Require advanced inventory management (lot tracking, bin locations, advanced warehouse)

• Need manufacturing capabilities (BOMs, production orders, capacity planning)

• Expanding internationally (multi-currency, multi-language)

• Want integrated CRM and project management

• Need better reporting and analytics (Power BI)

❌ Stay on QuickBooks if:

• Very small business (<10 users, simple needs)

• QuickBooks Online or Desktop meeting all current and foreseeable needs

• Budget constraints (BC has higher TCO)

• No growth plans requiring advanced ERP capabilities

Bottom Line: QuickBooks to Business Central migration costs $50K-$200K depending on size and complexity, but delivers significant ROI through productivity, scalability, and advanced capabilities that QuickBooks cannot provide. Expect 12-24 month payback period for most organizations.

3. What is the difference between ERP upgrade and ERP migration?

Answer: Upgrade means moving to a newer version of your existing ERP system while retaining most configurations and customizations. Migration means switching to a completely different ERP platform, requiring data conversion, process re-engineering, and re-implementation.

Detailed Comparison:

1. Definitions

ERP Upgrade:

• Moving from one version to another within same product family

• Examples:

  • Dynamics NAV 2017 → NAV 2018

  • SAP Business One 9.3 → 10.0

  • NetSuite 2023.1 → 2023.2

ERP Migration:

• Switching from one ERP system to a different ERP platform

• Examples:

  • QuickBooks → Business Central

  • Sage 50 → NetSuite

  • SAP Business One → Dynamics 365 Business Central

  • On-premises NAV → Cloud Business Central (technically a migration due to architecture change)

2. Comparison Table

3. Upgrade Deep Dive

Why Upgrade?

• Security Patches: Vendor releases security fixes for supported versions only

• Compliance: Regulatory changes require system updates (tax rates, reporting formats)

• New Features: Access to improved functionality, performance, integrations

• Vendor Support: Mainstream support ends for older versions (forcing upgrade to remain supported)

• Integration Requirements: New tools/apps may only support latest ERP versions

Upgrade Types:

Minor Version Upgrade (e.g., NAV 2018 → NAV 2018 CU 15):

• Cumulative updates (CU) with bug fixes and minor enhancements

• Timeline: 1-2 weeks (testing and deployment)

• Cost: Minimal ($2,000-$10,000 for partner assistance)

• Risk: Very low (incremental changes)

Major Version Upgrade (e.g., NAV 2016 → NAV 2018):

• Significant new features, UI changes, deprecated functionality

• Timeline: 6-12 weeks (testing, custom code review, training)

• Cost: $20,000-$80,000 (depending on customization complexity)

• Risk: Moderate (customizations may need updates, testing critical)

Platform Upgrade (e.g., On-Prem NAV → Cloud Business Central):

• Fundamentally different architecture (on-prem vs. SaaS)

• While technically an "upgrade" within Microsoft Dynamics family, behaves more like migration

• Timeline: 12-20 weeks (effectively a re-implementation)

• Cost: $100,000-$300,000 (treat as migration project)

• Risk: High (architecture change, customization rebuild in AL, user adoption)

Upgrade Challenges:

Custom Code Conflicts:

• Upgraded version may change standard objects your customizations modify

• Requires code merge and testing

• May need to refactor customizations to align with new version paradigms

Data Structure Changes:

• New fields, deprecated fields, changed field types

• Usually handled by vendor upgrade scripts, but custom tables/fields need manual review

User Interface Changes:

• Major upgrades often include UI redesigns

• Users need training on new navigation, changed workflows

• Resistance to change even within same system

Testing Requirements:

• Must test ALL critical business processes (not just new features)

• Regression testing ensures upgrade didn't break existing functionality

• Typical: 2-4 weeks of UAT before production upgrade

4. Migration Deep Dive

Why Migrate?

• End of Product Life: Vendor discontinuing product (e.g., NAV sunsetting in favor of BC)

• Outgrown Current System: Need capabilities current ERP can't provide

• Cloud Transformation: Legacy on-prem system; need cloud-native solution

• M&A Activity: Acquired company on different ERP; consolidate to single platform

• Total Cost of Ownership: Legacy system too expensive to maintain vs. modern alternatives

• Competitive Disadvantage: Outdated technology limiting business agility

Migration Phases:

Phase 1: Assessment & Planning (4-6 weeks):

• Current system audit (customizations, integrations, data quality)

• New system selection and proof of concept

• Migration roadmap and budget

Phase 2: Design & Build (8-16 weeks):

• Requirements gathering (from scratch, even if migrating similar processes)

• New ERP configuration

• Data mapping (old schema → new schema)

• Customization development (rebuild business-critical custom logic)

• Integration development (CRM, e-commerce, etc.)

Phase 3: Data Migration (4-8 weeks):

• Data extraction from legacy system

• Data cleansing (fix quality issues before loading)

• Data transformation (map to new ERP structure)

• Data loading and validation

• Reconciliation (ensure no lost or corrupted data)

Phase 4: Testing (4-6 weeks):

• System Integration Testing (SIT)

• User Acceptance Testing (UAT)

• Performance testing

• Integration testing

Phase 5: Training (3-4 weeks):

• Comprehensive training on new system (not just "what's new")

• Hands-on practice in sandbox environment

• Super-user certification

Phase 6: Cutover & Go-Live (1-2 weeks):

• Final data load

• Legacy system shutdown

• Go-live support

Phase 7: Hypercare (4-8 weeks):

• Intensive post-go-live support

• Issue resolution

• Process optimization

Total Timeline: 28-50 weeks (6-12 months typical)

Migration Challenges:

Data Complexity:

• Different data models (e.g., QuickBooks flat file structure vs. BC relational database)

• Data quality issues in legacy system (duplicates, incomplete records, inconsistencies)

• No direct mapping for some fields (requires business decisions on how to handle)

Customization Rebuild:

• Legacy customizations must be evaluated: rebuild, replace with standard, or eliminate

• Different customization frameworks (e.g., NAV C/AL → BC AL; SAP Crystal Reports → BC Power BI)

• Opportunity cost: Time spent rebuilding vs. new development

Process Re-engineering:

• New ERP may require different workflows (e.g., QuickBooks simple invoicing → BC sales order → shipment → invoice workflow)

• Change management critical (users resist new processes even if more efficient)

Integration Ecosystem:

• Third-party apps integrated with legacy ERP may not support new ERP

• Requires new integrations or switching to new third-party vendors

• Example: Salesforce integration with old ERP needs complete rebuild for new ERP

User Adoption:

• Users comfortable with legacy system (even if inefficient)

• New system = learning curve, productivity dip, frustration

• Requires strong change management, training, executive sponsorship

5. Decision Matrix: Upgrade vs. Migrate

Choose UPGRADE When:

✅ Current ERP meeting business needs with minor gaps

✅ Vendor actively developing product (regular updates, long-term roadmap)

✅ Upgrade path available and supported by vendor

✅ Customizations can be preserved or easily updated

✅ Budget constraints (upgrade 70-90% cheaper than migration)

✅ Low tolerance for business disruption

✅ Short timeline required (upgrade in 2-4 months vs. migration in 6-12 months)

Choose MIGRATION When:

✅ Current ERP at end-of-life (vendor discontinuing support)

✅ Significant functional gaps (current ERP lacks critical capabilities)

✅ Cloud transformation required (legacy on-prem only)

✅ Total cost of ownership unsustainable (aging infrastructure, high maintenance)

✅ Competitive disadvantage (outdated technology limiting growth)

✅ M&A standardization (consolidating multiple ERP systems)

✅ Poor data quality (migration = opportunity to cleanse and restructure)

6. Cost Comparison Example

Scenario: Manufacturing Company, 50 Users, Dynamics NAV 2016

Option A: Upgrade to NAV 2018

Option B: Migrate to Business Central (Cloud)

Cost Difference: Migration is 5-6x more expensive than upgrade.

BUT: Consider Long-Term ROI

NAV 2018 Upgrade (5-Year TCO):

• Upgrade cost: $100,000

• Annual maintenance: $25,000/year × 5 = $125,000

• Infrastructure (servers, SQL, IT time): $50,000/year × 5 = $250,000

• Future upgrade (NAV 2018 → ??? in 3-5 years): $75,000-$150,000

• Total 5-Year Cost: $550,000-$625,000

• Note: NAV 2018 support ends 2026; another upgrade/migration forced soon

Business Central Migration (5-Year TCO):

• Migration cost: $450,000

• Annual subscription: $42,000/year × 5 = $210,000

• Annual support/enhancements: $30,000/year × 5 = $150,000

• No infrastructure costs (cloud)

• No forced upgrades (continuous updates included)

• Total 5-Year Cost: $810,000

TCO Difference: BC $185K-$260K higher over 5 years

However, BC Provides:

• Modern capabilities (AI, Power Platform, mobile, embedded analytics) = productivity gains

• Cloud benefits (99.9% SLA, geo-redundancy, auto-scaling) = reduced risk

• No future upgrade costs (continuous updates) = budget predictability

• Long-term viability (Microsoft's strategic platform) = no forced migration in 5 years

ROI Justification: If BC delivers $50K-$100K/year in productivity and capability benefits, it pays for TCO difference and provides net positive ROI.

7. Special Case: NAV to Business Central

Is NAV → BC an Upgrade or Migration?

Microsoft calls it: "Migration" (using Cloud Migration Tool)

Why it's more like migration:

• Architecture change (on-prem C/SIDE → cloud AL extensions)

• Customizations must be rebuilt (C/AL → AL)

• Different licensing model (perpetual → subscription)

• Cloud infrastructure (Azure) vs. on-prem servers

Why it feels like upgrade:

• Same vendor (Microsoft)

• Similar UI (Role Centers, navigation)

• Table structure compatibility (80%+ direct mapping)

• User familiarity (minimal retraining)

Bottom Line: Treat NAV → BC as hybrid: easier than migrating to SAP or Oracle, but more complex than upgrading NAV 2016 → 2018.

Conclusion:

• Upgrade = Stay on same platform, move to newer version (lower cost, lower risk, faster)

• Migration = Switch to different platform (higher cost, higher risk, but long-term strategic benefits)

• Decision depends on: Vendor roadmap, functional needs, budget, timeline, risk tolerance

• For most NAV/Sage/QuickBooks users: Migration to Business Central is inevitable and advisable given vendor end-of-life timelines and BC's modern capabilities

Conclusion: Your Migration Success Starts Here

Migrating from legacy ERP to Business Central is a significant undertaking—but with proper planning, experienced guidance, and a proven methodology, it's also a transformational opportunity.

Successful migrations share common characteristics: comprehensive assessment, detailed planning, rigorous testing, effective training, and strong post-go-live support. Organizations that invest in these fundamentals achieve faster time-to-value, higher user adoption, and greater ROI from their Business Central investment.

Your successful migration roadmap includes: ✅ Comprehensive assessment (understand current state, identify risks)
✅ Detailed migration plan (timeline, budget, resources)
✅ Automated data migration (minimize manual effort, maximize accuracy)
✅ Role-based training (users confident before go-live)
✅ Rigorous testing (catch issues before production)
✅ Cutover support (experienced team during critical period)
✅ Post-go-live optimization (continuous improvement)

Key Takeaways:

• Choose an experienced Microsoft Solutions Partner with proven legacy ERP migration expertise

• Allocate adequate time (12-36 weeks depending on complexity)

• Involve users early and often throughout the project

• Test thoroughly before go-live (minimum 2 full test cycles)

• Plan for 12 weeks of hypercare support post-go-live

• View migration as process improvement opportunity, not just system replacement

Migration from legacy ERP to Business Central positions your organization for modern, cloud-first operations with capabilities that grow with your business.

This is Part 9 of an 11-part series on Business Central Implementation. Continue with Part 10 to learn about ongoing Business Central support and optimization strategies.

Related Articles:

• Part 1: Foundation, Discovery & Planning

• Part 4: Data Migration Strategy & Execution

• Part 8: Go-Live, Hypercare & Continuous Improvement

• Part 10: Business Central Support and Optimization

Copyright © 2025 QUALIA Technik GmbH. All rights reserved.