How do you move your Dynamics NAV data to the cloud?

To move your Dynamics NAV data to the cloud, you migrate it to Microsoft Dynamics 365 Business Central — the cloud-based successor to NAV. The process involves cleaning and mapping your existing data, using Microsoft’s built-in migration tools or partner-developed tools, and running a structured cutover to switch from your on-premise environment to the cloud. The sections below walk through each part of that process in practical detail.

What happens to your data when you migrate Dynamics NAV to the cloud?

When you migrate Dynamics NAV to the cloud, your data is extracted from the on-premise SQL database, transformed to match Business Central’s data structures, and loaded into the new environment. The migration does not simply copy a database — it maps your existing records to a different schema, which means data quality and structural alignment matter from the start.

In practice, this affects several data categories differently. Master data such as customers, vendors, and items typically transfers with relatively low complexity. Transactional history, open entries, and balances require more careful handling because Business Central may store or process them in ways that differ from NAV. Custom fields, modifications, and third-party add-ons built on top of NAV can create additional complexity, especially if those customisations have no direct equivalent in Business Central.

The migration also affects how historical data is accessed after go-live. Many organisations choose to migrate only open transactions and a defined period of history into Business Central, keeping older data in a read-only archive or reporting environment. This reduces migration scope and risk while still giving users access to the records they need day to day.

What is the difference between a NAV upgrade and a cloud migration?

A NAV upgrade replaces your existing version of Dynamics NAV with a newer on-premise version, keeping the same deployment model. A cloud migration moves your environment entirely to Microsoft’s SaaS platform, Business Central Online, which changes not only the software version but also how the system is hosted, maintained, and updated.

The distinction matters practically because the two paths carry different implications for your IT infrastructure, customisations, and long-term costs. An upgrade keeps your server infrastructure in place and allows you to retain heavily customised code, but it still requires you to manage hosting, updates, and security yourself. A cloud migration removes that infrastructure responsibility entirely — Microsoft handles updates, uptime, and security — but it requires you to replace or rebuild customisations using Business Central’s extension model rather than direct code modifications.

For most organisations running NAV today, a cloud migration is the more forward-looking choice. Microsoft has moved its development investment firmly into Business Central Online, and on-premise support for older NAV versions has a defined end date. That said, the right path depends on your customisation complexity, integration landscape, and internal capacity to manage the transition.

How do you prepare your Dynamics NAV data before moving to the cloud?

Preparing your Dynamics NAV data for a cloud migration starts with a thorough As-Is analysis of your current data structures — understanding what data you have, where it lives, how clean it is, and what actually needs to move. Skipping this step is one of the most common reasons migrations run into problems after go-live.

Concrete preparation steps include:

Data audit: Identify duplicate records, inactive accounts, outdated master data, and inconsistencies that have accumulated over years of use.
Data cleansing: Remove or archive data that does not need to move. Migrating unnecessary records adds cost and risk without adding value.
Field mapping: Map each data field in NAV to its equivalent in Business Central. Where no direct equivalent exists, decide early whether to transform the data or handle it differently.
Scope definition: Agree on how much transactional history to migrate versus archive. Open items, current balances, and a defined lookback period are typically sufficient for most operational needs.
Test migration: Run at least one full test migration into a Business Central sandbox before the live cutover. This surfaces data quality issues and mapping errors in a safe environment.

At Optinus, we use rigorous As-Is/To-Be analysis as the foundation of every data migration management engagement. That structured approach is specifically designed to prevent data loss and errors before they reach the production environment.

What tools are used to migrate Dynamics NAV data to Business Central?

The primary tool for migrating Dynamics NAV data to Business Central is Microsoft’s Cloud Migration extension, which is built directly into Business Central Online. This extension connects to your on-premise NAV database and handles the transfer of master data, transactions, and historical records through a guided setup process.

Beyond Microsoft’s native tooling, several other tools and approaches are commonly used depending on migration complexity:

RapidStart Services: A Business Central configuration tool that supports data import via Excel templates — useful for structured master data loads and initial setup.
Custom ETL scripts: For complex transformations or large data volumes, SQL-based extract, transform, and load scripts give migration teams more precise control over how data is shaped before it enters Business Central.
Third-party migration tools: Several Microsoft partners offer tools built specifically for NAV-to-Business Central migrations, with pre-built mappings and validation checks for common data structures.
Staging environments: Running data through a staging database before loading into Business Central allows teams to validate and clean records without affecting the live system.

Tool selection should follow the complexity of your data landscape, not the other way around. A straightforward migration with clean data and few customisations may work well with Microsoft’s native extension. A more complex environment with extensive modifications, integrations, or large data volumes typically benefits from a more controlled, scripted approach.

What are the biggest risks in a Dynamics NAV cloud migration?

The biggest risks in a Dynamics NAV cloud migration are data quality issues, customisation loss, integration failures, and poor cutover planning. Each of these can cause disruptions that range from minor post-go-live corrections to serious operational problems that affect customers and financial reporting.

Data quality risk is the most common. Years of accumulated inconsistencies, duplicates, and incomplete records in NAV do not fix themselves during migration — they move into Business Central and become harder to correct once users are working in the live system. Early data cleansing and structured test migrations reduce this risk significantly.

Customisation risk is specific to NAV environments that have been heavily modified over time. Business Central does not support the same kind of direct code changes that NAV allowed. Custom functionality needs to be rebuilt as extensions or replaced with standard Business Central features, and that process takes time and careful scoping.

Integration risk affects organisations that have connected NAV to other systems — warehousing, e-commerce, payroll, or reporting tools. Those integrations need to be rebuilt or reconfigured for Business Central, and they need to be tested thoroughly before go-live.

Cutover risk is the final critical area. The cutover is the moment you switch from NAV to Business Central in a live environment, and it leaves very little room for error. A poorly planned cutover — one without a detailed runbook, clear rollback criteria, and real-time monitoring — can result in downtime, data inconsistencies, or a failed go-live that forces a rollback. You can explore our full range of services to see how structured cutover and migration management fit together as part of a complete transformation approach.

How Optinus helps with your Dynamics NAV cloud migration

We support organisations through every phase of a Dynamics NAV to Business Central migration — from the initial data audit through to post-go-live hypercare. Here is what that looks like in practice:

As-Is/To-Be analysis of your current NAV data structures, so you know exactly what needs to move and what can be left behind
Data cleansing and field mapping to ensure records arrive in Business Central clean, correctly structured, and ready for use
Test migration management with rigorous validation procedures to catch errors before they reach the live environment
Cutover planning and execution with real-time monitoring and a clear rollback plan, so operational continuity is never at risk
Hypercare and aftercare after go-live, so your team has support during the period when issues are most likely to surface
Available on-site and remote, across the Netherlands, Belgium, and internationally

If you are preparing for a Dynamics NAV migration and want a clear picture of where you stand before committing to a roadmap, get in touch with our team or learn more about what we do.

home|

blog|