Migrating from Legacy ERP to Business Central - A Proven Roadmap

Code: BC-IMPL-04  

Category: Migration & Upgrade  

Target Audience: IT Directors, CFOs, Business Owners  

Reading Time: 12 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 SME pricing. But migration from legacy systems is complex—data conversion, process re-engineering, user adoption, and business continuity all demand careful planning.

With QUALIA Technik GmbH's 20+ years of ERP migration experience, we've successfully transitioned 150+ companies from legacy platforms to Business Central with zero data loss, minimal downtime, and rapid user adoption.

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

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

| Aspect | Migration | Greenfield |

|--------|-----------|------------|

| Historical Data | Migrate years of history | Start with opening balances only |

| Timeline | Longer (data conversion) | Shorter (clean start) |

| Risk | Data integrity, mapping errors | Learning curve, missing history |

| Cost | Higher (conversion effort) | Lower (no conversion) |

| User Adoption | Compare to old system | No comparison baseline |

| Best For | Audit requirements, trend analysis | Clean slate, poor data quality |

QUALIA Recommendation: Migrate critical master data and 2-3 years of transactional history; archive older data in read-only format. This balances completeness with migration complexity.

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 QUALIA 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 (QUALIA + 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:

• QUALIA 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:

• QUALIA 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:

• QUALIA 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

• QUALIA available for escalations only

• Monthly review calls (1 hour)

Focus Areas:

• Knowledge transfer (QUALIA 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 QUALIA 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

QUALIA Recommendation:

• 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 QUALIA)

• 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 (QUALIA Workflow)

• Complex business logic (QUALIA Rule Engine)

• Advanced reporting (Power BI dashboards)

• 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

QUALIA Managed Services:

• Bronze Plan: €500/month

  - Email support (48-hour response)

  - Quarterly health check

  - BC update notifications

• Silver Plan: €1,200/month

  - Phone + email support (8-hour response)

  - Monthly health check

  - Proactive optimization recommendations

  - 10 hours/month included (additional hours €120/hour)

• Gold Plan: €2,500/month

  - Priority support (2-hour response)

  - Weekly check-ins

  - Dedicated consultant

  - 25 hours/month included (rollover up to 50 hours)

  - Quarterly executive business review

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.

QUALIA Technik GmbH has successfully migrated 150+ companies from legacy systems to Business Central. We've learned from every project, refined our approach, and built tools that accelerate migration while reducing risk.

Your successful migration 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 (on-site team during critical period)  

✅ Post-go-live optimization (continuous improvement)

Ready to start your migration journey?

Contact QUALIA today for a complimentary migration assessment. We'll review your current system, identify challenges, and provide a detailed roadmap with timeline and budget.

Contact Us

QUALIA Technik GmbH  

📧 Email: migration@qualia-technik.com  

📞 Phone: +49 (0) 123 456 7890  

🌐 Web: www.qualia-technik.com/bc-migration  

Free Migration Assessment: [calendly.com/qualia-migration-assessment]

Copyright © 2025 QUALIA Technik GmbH. All rights reserved.