Dynamics NAV to Business Central: what happens to historical data

Upgrade or fresh start: the choice that decides your history#

The choice between a technical upgrade and a fresh implementation decides how much NAV history reaches Business Central. Because Business Central grew out of NAV, a supported upgrade can carry the database forward with posted entries intact, although older NAV versions may need intermediate upgrade steps and heavily modified databases need their customizations rebuilt first.

Many distributors still choose a fresh start. They want to drop years of modifications, clean up the chart of accounts and item numbering, and begin on standard Business Central with extensions. That path usually brings over master data and open balances only, leaving history in the NAV database. Your Microsoft partner can confirm which paths your version supports.

What typically stays behind in a fresh start#

A fresh start typically leaves behind the transaction-level history that explains how the business ran. For a distributor, that is the record of every order, shipment, return and price change, not just the balances that survive into the new system.

The loss is easy to miss at go-live. Business Central opens with correct balances and active customers, and the gap appears later, when someone needs a customer's purchase history for a rebate claim, a warranty lookup or a forecast built on several years of item movement.

• 1Posted sales invoices, shipments, credit memos and their lines.
• 2Posted purchase receipts and invoices, including vendor item references.
• 3Item ledger and value entries, which hold the full inventory movement and costing history.
• 4Warehouse entries and bin movements from the warehouse management functions.
• 5Archived sales and purchase document versions showing how orders changed.
• 6Comment lines and record links, where staff left notes on customers, items and orders.
• 7The change log, if it was enabled, showing who edited prices, credit limits and item setup.
• 8Custom tables for things like rebates, special pricing agreements or EDI staging.

Custom tables and fields are where history gets stranded#

Custom tables and fields are where NAV history most often gets stranded, because Business Central uses AL extensions rather than the C/AL modifications many NAV databases carry. A field added to the customer table for a buying group, or a whole table for vendor rebate tracking, has no place to land until a developer recreates it as an extension.

Projects under time pressure tend to rebuild only what is needed going forward. The history in those fields stays in NAV, and with it the knowledge of what the fields meant. That knowledge often lives with a long-serving developer or controller, which is a good reason to document it before the people who built the system move on.

Ways to keep the left-behind history usable#

Left-behind NAV history stays usable only if someone can still query it and understand the results. There are four common approaches, and many companies combine two of them, such as a restorable backup plus a reporting copy.

An archive checklist before the NAV server is retired#

An archive checklist protects against the problems that surface only after the old server is gone. The technical details below are the ones IT teams most often regret skipping.

Two quirks deserve special attention. NAV stores option fields as integers, so a document type stored as a small number means nothing without the mapping from the table definition. And NAV prefixes table names with the company name in SQL, so a database holding several companies needs a map of which prefix belongs to which legal entity.

• 1Take a full SQL Server backup and test a restore on a separate server.
• 2Export table and field definitions, including option value captions.
• 3Document which company prefix belongs to which legal entity.
• 4Decode notes stored in the record link table, where the text sits in a binary field.
• 5Collect attachments referenced by file path on network shares, which are not inside the database.
• 6Record who can access the archive and how it is secured.

Illustrative: a wholesale distributor moves to Business Central#

Illustrative: a fictional wholesale distributor of janitorial supplies has run NAV for many years, with custom tables for manufacturer rebates and a field on sales lines recording why a salesperson overrode the price. It chooses a fresh implementation of Business Central online, bringing customers, items, vendors, open orders and opening balances.

Before the cutover, the IT director restores a copy of the NAV database to a reporting server, exports the table definitions with option captions, decodes record link notes and copies the attachment share. The controller writes a one-page description of each custom table. Later, when sales leadership asks how price overrides affected margin by customer, the answer comes from the archive in an afternoon instead of a forensic project.

Why left-behind NAV history can still have value#

Left-behind NAV history can still have value beyond reporting. Order changes, credit memos with reasons, price overrides, returns and purchase order revisions are the kind of linked operational records AI developers look for when building procurement and distribution tools, provided they can be read and their meaning is documented.

SourceX starts with a metadata-only fit check: which NAV version, which record families, how many years and which custom tables exist. If a package proceeds, it runs through the SourceX five-step transaction of Supply, Rights, Preparation, Approval and Delivery, with personal and customer-identifying details removed and a SourceX Evidence Packet documenting provenance, rights and release authorization. The records are licensed, not sold.