Is It Time to Migrate from NAV 2013 to Business Central? Here’s a Proven, Phased Approach for SMEs
Still using Microsoft Dynamics NAV 2013?
Discover how your business can move to Business Central SaaS using a structured, phased migration plan. Learn how to manage customisations, data, integrations, and users without disruption, while preparing for long-term success.
Introduction
If your business is still running Microsoft Dynamics NAV 2013, you’re not alone, but the clock is ticking. With end-of-support dates looming and modern ERP expectations rising, now is the time to start planning your move to the cloud.
Migrating from NAV 2013 to Microsoft Dynamics 365 Business Central (SaaS) offers more than just an upgrade. It delivers a complete transformation in how your organisation operates, scales, and gains real-time visibility.
In this blog, we outline a proven, phased migration plan tailored for UK-based companies with complex NAV installations; those with large databases, multiple customisations, third-party add-ons, and high user counts. You’ll see how a phased approach minimises risk and delivers long-term ERP value.
Related Article: Is NAV Still Supported
Why Migrate from NAV 2013?
Microsoft Dynamics NAV 2013 is a robust system, but it’s over a decade old. On-premise architecture, manual upgrades, and heavy custom code make it increasingly difficult to support modern, agile business needs.
Key reasons to move:
- Microsoft support for NAV 2013 has ended
- Growing limitations on scalability and integrations
- High infrastructure and maintenance costs
- Manual upgrade paths and technical debt
- No native AI, real-time analytics, or cloud flexibility
Migrating to Business Central SaaS eliminates these blockers by offering a fully cloud-based ERP with automatic updates, advanced reporting, Microsoft Copilot integration, and seamless Microsoft 365 integration.
Related Article: What You Get With Business Central
Your NAV 2013 Environment
Let’s assume a typical legacy setup:
- 450GB NAV database
- 10 bespoke modules (written in C/AL)
- 3 third-party ISV add-ons
- 5 companies
- 120 users
- Integrated warehouse management system (WMS)
The goal: to move this complex environment to Business Central SaaS using a structured, phased approach with minimal disruption and no seasonal blackout.
If you find this article useful, click and subscribe to our newsletter - Business Central Uplugged - helping you use what you've already paid for!
The Phased Migration Plan
Phase 1: Discovery & Readiness Assessment (4 Weeks)
This phase lays the foundation by auditing your current NAV implementation:
- Inventory of customisations, third-party tools, and integrations
- Analysis of company-specific processes and data volumes
- Identification of custom code to be converted or retired
- Fit-gap analysis between current functionality and Business Central standard features
📊 Estimated effort: 20–25 consultant days
Phase 2: Converting Bespoke Modules & Add-Ons (6–10 Weeks)
NAV 2013 used C/AL code. Business Central SaaS uses AL extensions, requiring a complete refactor of your customisations.
- Rebuild 10 bespoke modules as AL extensions
- Identify any obsolete or replaceable features
- Work with ISV vendors to secure SaaS-compatible versions or reimplement missing functionality
- Begin planning for WMS migration and integration
📊 Estimated effort: 50–70 days
⚠️ This phase carries high risk due to technical complexity.
Phase 3: Data Migration Strategy (6–8 Weeks)
With a 450GB database, migrating all historical data is neither necessary nor cost-effective.
- Define cut-off rules for each of the 5 companies
- Migrate current-year and open balances only
- Archive historical data in a secure, searchable format (e.g. Azure data lake or Power BI warehouse)
- Use Microsoft’s Data Migration Tool to automate transfer to BC
📊 Estimated effort: 30–40 days
Phase 4: WMS & Integration Migration (6–8 Weeks)
Rebuild existing integrations using modern APIs or Power Automate flows:
- Ensure real-time or batch synchronisation as required
- Redesign WMS integration with Business Central SaaS architecture in mind
- Perform sandbox testing to validate data movement
📊 Estimated effort: 25–40 days
Phase 5: User Training & Change Management (4–6 Weeks)
Preparing your 120 users for Business Central is critical for adoption and success:
- Deliver training by department (e.g. finance, sales, warehouse)
- Configure Role Centres and permissions for different user types
- Develop UAT scripts and go-live playbooks
- Provide internal champions and training resources
📊 Estimated effort: 20–30 days
Phase 6: Phased Go-Live & Hypercare (10–12 Weeks)
Instead of one “big bang”, go-live one company at a time:
- Migrate and activate Company 1, support for 2–3 weeks
- Repeat for each subsequent company
- Use Application Insights to monitor system performance post-deployment
- Provide hypercare and minor adjustments
📊 Estimated effort: 30–40 days
Related Article: Microsoft’s Bridge to the Cloud 2 Offer
Timeline Overview
| Phase | Duration | Effort (Days) |
|---|---|---|
| Discovery | 4 weeks | 20–25 |
| Extension Rebuild | 6–10 weeks | 50–70 |
| Data Migration | 6–8 weeks | 30–40 |
| Integration & WMS | 6–8 weeks | 25–40 |
| User Training & UAT | 4–6 weeks | 20–30 |
| Phased Go-Live | 10–12 weeks | 30–40 |
Total Duration: ~9–12 months
Total Consultant Effort: ~200–300 days
⚠️ Key Risks and How to Mitigate Them
| Risk | Mitigation Strategy |
|---|---|
| Legacy custom code not reusable | Rebuild as extensions in AL |
| WMS not BC-compatible | Engage early and test in sandbox |
| Add-ons unavailable for SaaS | Replace with standard BC functionality or partner apps |
| Data migration slow or error-prone | Clean and compress data pre-migration |
| User resistance to change | Deliver training and UAT per role |
FAQs: Migrating from NAV 2013 to Business Central
Why should SMEs move from NAV 2013 to Business Central SaaS?
NAV 2013 is out of mainstream support, limiting security, compliance and feature updates. Business Central SaaS offers modern cloud functionality, regular updates and scalability.
What are the main benefits of a phased migration approach?
A phased approach reduces risk by migrating functionality step by step. It allows core finance to go live first, while other modules (e.g. warehouse, reporting, integrations) are added in later phases.
What challenges are common when migrating from NAV 2013?
Challenges include large databases, outdated customisations, third-party add-ons that may not be compatible, and data quality issues. Each requires planning and remediation.
How should SMEs handle customisations during migration?
Review customisations to decide if they are still needed. Many can be replaced by standard Business Central functionality or extensions. Only critical customisations should be rebuilt.
How do third-party add-ons impact the migration?
Add-ons used in NAV may not have direct equivalents in SaaS. Alternatives include replacing with built-in features, sourcing updated ISV extensions, or redeveloping using AL.
How long does a phased migration from NAV 2013 take?
Timelines vary by scope, but a typical SME migration takes 4–6 months. Larger databases or extensive customisations may extend this to 9–12 months.
What data should be migrated from NAV 2013?
Usually master data (customers, vendors, items, chart of accounts), open entries (orders, invoices, balances) and selected historical data. Full transaction history is often archived separately.
Can SMEs continue running NAV and Business Central in parallel?
Yes. During phased rollout, NAV can run in parallel for non-migrated functions. This reduces disruption but requires careful planning for data synchronisation.
What is the role of testing in a phased migration?
Testing is critical at each phase. Unit tests, integration tests and user acceptance testing (UAT) confirm that migrated processes and data behave as expected before go-live.
How can SMEs minimise downtime during migration?
Plan a clear cut-over weekend, migrate open transactions last, use trial runs to estimate timings, and communicate with users. A phased approach also spreads risk across multiple go-lives.
Why Business Central SaaS is the Right Move
-
Lower total cost of ownership: No hardware, patching, or upgrade costs
-
Seamless Microsoft 365 integration: Outlook, Excel, Teams
-
Real-time financials & dashboards via Power BI
-
AI-powered features with Microsoft Copilot
-
Scalable platform: Add apps, users, and new locations anytime
-
Automatic updates: No more costly version upgrades
You future-proof your ERP and make your business more agile, while reducing long-term costs.
Migrating from NAV 2013 to Business Central SaaS is a major step forward for any business, especially those with heavy customisations, multiple entities, and complex workflows.
With a phased, structured approach, the process can be smooth, predictable, and transformative.
If your organisation is ready to modernise, improve productivity, and cut long-term costs, now’s the time to start your Business Central journey.
Next Steps:
Want help planning your NAV to Business Central migration?
Book a free consultation with our ERP migration specialists today. We also promise to save you at least 30% on Migration services!
Enter your details below or call us on +44 (0) 1782 976577