# NAV to Business Central Data Migration Mapping Worksheet

> Source: https://netray.co/tools/nav-to-business-central-data-migration-mapping-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Track each NAV table you plan to migrate, the target in Business Central, the method, volume and status, and total the effort.

## Category

erp-migration

## Erp

Microsoft Dynamics 365 Business Central

## Audience

- Migration lead
- NAV consultant
- BC partner consultant

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### NAV table

**Key:** source

**Type:** text

#### Business Central target

**Key:** target

**Type:** text

#### Method

**Key:** method

**Type:** select

**Options:**

- Technical upgrade
- Configuration package
- RapidStart
- Journal import
- Custom script
- Do not migrate

#### Records

**Key:** records

**Type:** number

#### Load minutes per 1000

**Key:** mins_per_k

**Type:** number

#### Load time (min)

**Key:** load_min

**Type:** number

**Expr:** records / 1000 * mins_per_k

**Format:** decimal

#### Status

**Key:** status

**Type:** select

**Options:**

- Not started
- Mapped
- Test loaded
- Reconciled
- Signed off

#### Owner

**Key:** owner

**Type:** text

**Rows:**

**Source:** G/L Account (15)

**Target:** G/L Account

**Method:** Configuration package

**Records:** 650

**Mins per k:** 2

**Status:** Mapped

**Owner:** Finance lead

**Source:** Customer (18)

**Target:** Customer

**Method:** Configuration package

**Records:** 4200

**Mins per k:** 4

**Status:** Test loaded

**Owner:** Sales admin

**Source:** Vendor (23)

**Target:** Vendor

**Method:** Configuration package

**Records:** 1800

**Mins per k:** 4

**Status:** Test loaded

**Owner:** Purchasing

**Source:** Item (27)

**Target:** Item

**Method:** Configuration package

**Records:** 12500

**Mins per k:** 6

**Status:** Mapped

**Owner:** Materials

**Source:** Item Ledger Entry (32)

**Target:** Item Journal opening stock

**Method:** Journal import

**Records:** 3600

**Mins per k:** 5

**Status:** Not started

**Owner:** Inventory

**Source:** Cust. Ledger Entry (21)

**Target:** Gen. Journal opening entries

**Method:** Journal import

**Records:** 950

**Mins per k:** 5

**Status:** Not started

**Owner:** Finance lead

**Source:** Production BOM Line (99000772)

**Target:** Production BOM Line

**Method:** Custom script

**Records:** 28000

**Mins per k:** 3

**Status:** Mapped

**Owner:** Engineering

**Source:** Job Ledger Entry (169)

**Target:** History report only

**Method:** Do not migrate

**Records:** 0

**Mins per k:** 0

**Status:** Signed off

**Owner:** Project office

**Totals:**

#### Total records

**Key:** records

**Agg:** sum

**Format:** integer

#### Total load time (min)

**Key:** load_min

**Agg:** sum

**Format:** decimal

**Summary:**

#### Estimated load hours

**Key:** load_hours

**Expr:** sum_load_min / 60

**Format:** decimal

**Primary:** true

#### Average minutes per 1000 records

**Key:** avg_rate

**Expr:** sum_load_min / (sum_records / 1000)

**Format:** decimal

**Notes:** Minutes per 1000 records are planning inputs that you measure in a test load, the example values are not benchmarks. A technical upgrade moves data in place and does not need per-table loading, so use this for selective or fresh-start migrations.

## Content

**Intro:** Moving from Dynamics NAV to Business Central means deciding, table by table, what to migrate, how, and how long it will take. This worksheet makes those decisions visible and gives you a first estimate of load time.

**Sections:**

#### How to use the worksheet

**Body:** List every NAV table or data set that matters, including custom tables. Choose the target in Business Central and the method. Enter record counts from a SQL query or the Table Information page, and a measured load rate from a test load. The tool computes load time per row and in total. Update the status column during the project, and filter by owner for weekly status calls.

**Bullets:**

- Include custom tables and fields from add-ons
- Decide early which history is migrated and which stays archived
- Record the reconciliation evidence for each master data set

#### Choosing a migration method

**Body:** A technical upgrade converts the whole database and keeps history but needs the customization converted to extensions first. A fresh start with configuration packages loads clean master data and opening balances, and is common when the old database has years of clutter. Journal imports are used for opening balances. Custom scripts handle structures such as BOMs. Choose the lightest method that meets audit needs.

#### Estimating and testing loads

**Body:** Load time depends on validation logic, number of subscribers and hardware, so measure it in a test environment. Run at least two full test loads before cutover. The first finds mapping errors, the second proves the timing and the reconciliation. Use the totals here to plan the cutover window and to decide whether to freeze the legacy system for hours or a weekend.

#### Common mistakes

**Body:** Migrating everything by default is the main mistake, since old history makes the new system slower and harder to reconcile. Another is ignoring custom fields that carry business meaning. Teams also forget to load numbering state so new documents start with duplicates of old numbers. Finally, not reconciling each load immediately makes errors hard to trace.

**Cta:** If your NAV database needs profiling before a migration, we can analyze it on-premises and report duplicates, dormant records and custom table usage.

**Faq:**

#### Should we do a technical upgrade or a fresh start?

**Answer:** A technical upgrade keeps all history but requires converting customizations to extensions. A fresh start is cleaner and often faster for heavily customized or cluttered databases. The choice depends on audit needs, customization volume and how much history users need online.

#### How do I get record counts from NAV?

**Answer:** On the NAV client use the Table Information window, or run a COUNT query against the SQL database for on-premises installations. Count per company if you have several, because each company has its own table instances.

#### What is a configuration package?

**Answer:** It is a Business Central feature to export and import data between companies or environments using packages of tables. It validates fields on import, so it is slower than raw SQL but safer for master data.

#### How many test loads are enough?

**Answer:** Plan at least two complete rehearsals. The first reveals mapping and data quality problems, the second confirms timing and reconciliation. Large or complex databases often need three before the team is comfortable.

## Search terms

nav to business central data migration, dynamics nav migration mapping, navision data migration template, business central configuration package migration, nav to bc upgrade table mapping, dynamics nav data cleansing plan, navision to business central excel

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json