How do you keep historical data when leaving Dynamics NAV?

When you migrate away from Dynamics NAV, you can keep historical data by either migrating it directly into your new system, archiving it in a separate read-only environment, or retaining it in a decommissioned NAV instance for a defined retention period. The right approach depends on how frequently your teams need to access that data and what your legal or audit obligations require. This article walks through the key decisions you need to make to protect your historical data during a NAV migration.

What happens to your data when you migrate away from Dynamics NAV?

When you move away from Dynamics NAV, your historical data does not automatically transfer to the new system. You must make an active decision about what to do with it. Without a clear plan, data can become inaccessible, corrupted, or lost entirely during the transition. The migration process involves extracting data from NAV, transforming it to fit the new system’s data model, and loading it into the target environment.

In practice, most organisations migrating from NAV to a modern ERP such as Microsoft Dynamics 365 Business Central face a common challenge: the data structures in NAV do not map directly onto those in the new system. Fields, tables, and relationships often need to be reworked before any data can move. This transformation step is where errors are most likely to occur, particularly when dealing with years of accumulated transactional records, customer history, and financial data.

Beyond the technical complexity, there is also a business continuity dimension. If your teams lose access to historical purchase orders, invoices, or inventory records mid-migration, daily operations can stall. Planning the data migration as a structured workstream, rather than a last-minute activity, is what separates a smooth go-live from a disruptive one. You can explore ERP migration services that treat data migration as a dedicated discipline within the broader transformation programme.

Which historical data is worth migrating versus archiving?

Not all historical Dynamics NAV data needs to move into your new system. The general principle is to migrate data that users will actively reference in day-to-day operations and archive data that is needed for compliance, audit, or occasional lookup but not for regular business processes.

A practical way to think about this is to split your data into two categories:

Migrate: Open transactions, active customer and vendor master records, current inventory, ongoing projects, and any data that feeds into reporting or operational workflows in the new system.
Archive: Closed financial periods, completed orders, historical audit trails, and legacy records that must be retained for legal reasons but are unlikely to be accessed regularly.

The cutoff point for migration versus archiving is often defined by a combination of business need and data volume. Bringing five or ten years of closed transactions into a new ERP adds cost, complexity, and risk to the migration without delivering proportional value. Most organisations find that migrating one to three years of active historical data strikes the right balance, while older records go into a secure archive.

What are the main options for retaining Dynamics NAV historical data?

There are three main options for retaining historical Dynamics NAV data after you move to a new system, and many organisations use a combination of all three.

Migrate selected history into the new ERP

You bring a defined scope of historical records directly into Business Central or your target platform. This gives users a single system for both current and recent historical data, but it increases migration complexity and requires careful data mapping and cleansing.

Archive in a dedicated read-only environment

You export historical data from NAV into a structured archive, such as a data warehouse, a document management system, or a purpose-built archive tool. Users can query and retrieve records without touching the live ERP. This approach keeps the new system lean while still providing access to legacy data when needed.

Retain the legacy NAV instance

You keep the decommissioned NAV environment running in a read-only state for a defined period. This is the simplest option in the short term because no data transformation is required, but it carries ongoing infrastructure and licensing costs and is not a sustainable long-term solution.

The best option for your organisation depends on the volume of data involved, how frequently teams need to access it, your regulatory environment, and your budget for post-migration infrastructure.

How does data migration management protect data integrity during the transition?

Data migration management protects data integrity by applying a structured process of analysis, transformation, testing, and validation before any data moves into production. Without this discipline, errors introduced during extraction or transformation can corrupt records in the new system in ways that are difficult to detect and expensive to fix after go-live.

A rigorous approach to data migration management typically includes the following steps:

As-Is analysis: A thorough review of the current NAV data structures, identifying data quality issues, duplicate records, and gaps before migration begins.
To-Be mapping: Defining exactly how each field and table in NAV maps to the target system, including any transformation rules required.
Cleansing: Resolving data quality issues in the source before extraction, so problems are not replicated in the new environment.
Test migrations: Running the migration process multiple times in a test environment to validate that data arrives correctly and completely.
Reconciliation: Comparing record counts and key values between source and target to confirm nothing was lost or altered during the move.

This process reduces the risk of data loss, misaligned records, and compliance gaps. It also gives you documented evidence of data integrity, which is valuable for audit purposes after go-live.

How long should you keep historical Dynamics NAV data after go-live?

How long you should keep historical Dynamics NAV data after go-live depends primarily on your legal and regulatory obligations, which vary by country and industry. In most European jurisdictions, financial records must be retained for a minimum of seven years. Tax records, employment data, and contracts may carry different retention requirements depending on local law.

Beyond legal minimums, consider the following factors when setting your retention policy:

Audit and compliance requirements: If your organisation is subject to external audits, you may need to produce historical transaction records on demand for several years after go-live.
Business continuity needs: Some teams, particularly in finance and procurement, may need to reference historical records for trend analysis, contract renewals, or supplier negotiations.
Storage and infrastructure costs: Retaining data indefinitely is not free. Define a clear end date for each category of archived data and build a deletion schedule into your data governance policy.

A practical approach is to define retention periods by data category at the start of the migration project, not after go-live. This makes it easier to build the right archive structure from the beginning and avoids the common situation where historical data is kept indefinitely simply because no one decided otherwise.

How Optinus helps with Dynamics NAV data migration

We work with organisations migrating away from Dynamics NAV to ensure that historical data is handled correctly from the first day of the project to well after go-live. Our approach to data migration management is built around preventing data loss and errors, not just moving records from one system to another.

As-Is/To-Be analysis of your current NAV data structures to identify quality issues before they become migration problems.
Data mapping and transformation that accounts for the structural differences between NAV and your target platform, including Business Central.
Rigorous test migrations in a controlled environment before any data moves to production.
Reconciliation and validation to confirm data integrity at every stage of the transition.
Retention and archiving guidance to help you define what to migrate, what to archive, and for how long.

Whether you need support for a specific data migration workstream or a partner to manage the full NAV to Business Central migration, we cover the complete spectrum. Explore our data migration and ERP transformation services to see how we can support your programme.

Ready to talk through your NAV migration and what it means for your historical data? Get in touch with us and we will help you map out a clear, low-risk path forward.

home|

blog|