From NAV 2013 to Business Central: How SME's Can Make the Transition Step by Step

Is your organization still reliant on Microsoft Dynamics NAV 2013?
It’s time to look ahead! Discover how you can transition to Business Central SaaS easily and without disruption using a smart step-by-step plan. From customizations and data to integrations and users—this approach prepares your business for the future.

Introduction

Many organizations are still running on Microsoft Dynamics NAV 2013. Does this sound familiar? Then it’s important to know that time is running out. With support for NAV ending and the demands on modern ERP solutions increasing, now is the perfect moment to consider a move to the cloud.

Migrating to Microsoft Dynamics 365 Business Central SaaS is more than just an upgrade: it’s a complete transformation in how your organization operates, grows, and gains real-time insights.

In this blog, you’ll find a proven step-by-step plan to smoothly transition even the most complex NAV environments—with large databases, extensive customizations, add-ons, and users.

Why Transition from NAV 2013?

NAV 2013 was a powerful system for many years, but it’s now outdated. Its on-premises nature, manual updates, and heavy customizations make it increasingly difficult to respond flexibly to modern business needs.

Key reasons to migrate:

• No more Microsoft support for NAV 2013
• Limited scalability and integration options
• High infrastructure and maintenance costs
• Manual updates and technical debt
• No AI, real-time analytics, or cloud flexibility

With Business Central SaaS, you eliminate these bottlenecks: automatic updates, smart reporting, Microsoft 365 integration, and AI features like Copilot ensure your organization is future-ready.

A Typical NAV 2013 Landscape

Picture a classic setup:

• 450GB NAV database
• 10 custom modules (C/AL)
• 3 external add-ons
• 5 legal entities
• 120 users
• Connected warehouse management system (WMS)

The goal? To migrate this complex setup to Business Central SaaS in phases, without seasonal disruptions.

The Phased Migration Plan

Phase 1: Analysis and Preparation (4 weeks)

• Inventory of customizations, add-ons, and integrations
• Process and data volume analysis
• Fit-gap analysis between NAV and standard Business Central
• 📊 Effort: 20–25 consultancy days

Phase 2: Converting Customizations and Add-Ons (6–10 weeks)

• Refactor 10 custom modules into AL extensions
• Identify and replace obsolete functionalities
• Collaborate with vendors for SaaS-compatible versions
• Define WMS integration strategy

• 📊 Effort: 50–70 consultancy days
  
  

Phase 3: Data Strategy (6–8 weeks)

• Determine which data needs to be migrated
• Migrate current data, archive historical data (e.g., Azure Data Lake)
• Leverage Microsoft migration tools
• 📊 Effort: 30–40 consultancy days

Phase 4: Integrations and WMS (6–8 weeks)

• Rebuild integrations using modern APIs or Power Automate
• Conduct sandbox tests for data flows
• Reconnect WMS to SaaS architecture
• 📊 Effort: 25–40 consultancy days

Phase 5: Training and Change Management (4–6 weeks)

• User training per department (finance, sales, warehouse)
• Configure role centers and permissions
• Develop UAT scripts and go-live playbooks
• 📊 Effort: 20–30 consultancy days

Phase 6: Phased Go-Live and Post-Go-Live Support (10–12 weeks)

• Go live step by step for each legal entity
• Monitor with Application Insights
• Execute hypercare and minor optimizations
• 📊 Effort: 30–40 consultancy days

Risico’s en oplossingen

Why Business Central SaaS?

• Lower costs – No servers or expensive upgrades
• Microsoft 365 integration – Outlook, Excel, Teams
• Real-time insights – Power BI dashboards
• AI and automation – Microsoft Copilot
• Scalable – Add apps, users, and locations as needed
• Automatic updates – Always up to date

With Business Central SaaS, your ERP becomes the backbone of an agile, future-proof organization.

Ready to Take the Next Step?

The transition from NAV 2013 to Business Central SaaS is significant, but with a structured approach, the process remains manageable and delivers maximum value.