---
title: "From Navision to Business Central – How the Contents of Customized and New Tables Are Transferred"
id: "997940"
type: "post"
slug: "navision-to-business-central-transferring-customized-and-new-tables"
published_at: "2025-09-12T12:57:03+00:00"
modified_at: "2026-09-02T06:06:58+00:00"
url: "https://ioi.gmbh/en/2025/09/12/navision-to-business-central-transferring-customized-and-new-tables/"
markdown_url: "https://ioi.gmbh/en/2025/09/12/navision-to-business-central-transferring-customized-and-new-tables.md"
excerpt: "1. Prepare the structures in Business Central First you create or adjust the target structures in Business Central. These tables later hold the content from the old NAV system, including any new fields or adjusted tables that the new system..."
taxonomy_category:
  - "DataMigrate Pro"
  - "Support &amp; Documentation"
---

Contents

- [1. Prepare the structures in Business Central](#1-prepare-the-structures-in-business-central)
- [2. Read structures into mapping structures](#2-read-structures-into-mapping-structures)
- [3. Write the mapping structures back to NAV and configure the assignment](#3-write-the-mapping-structures-back-to-nav-and-configure-the-assignmen)
- [4. Start the data transfer to BC](#4-start-the-data-transfer-to-bc)
- [5. Alternative procedure](#5-alternative-procedure)

## 1. Prepare the structures in Business Central

First, the target structures are created or adjusted in Business Central. These tables will later hold the content from the old NAV system – including new fields or adjusted tables that are required for the new system.

*Example structure in NAV*

Excerpt `Provisionsposten.Table.al`

```
namespace Customer.Provision;

using Microsoft.Sales.Setup;
using Microsoft.Sales.Document;
using Microsoft.Inventory.Item;
using Microsoft.Sales.Customer;

table 70103 "Provisionsposten IOI"
{

    //DrillDownFormID = Form50006;
    //LookupFormID = Form50006;

    fields
    {
        field(1; "Entry No."; Integer)
        {
            Caption = 'lfd. Nr.';
        }
        field(8; Buchungsdatum; Date)
        {
        }
        field(9; "Document Type"; Option)
        {
            Caption = 'Document Type';
            OptionCaption = 'Quote,Order,Invoice,Credit Memo,Blanket Order,Return Order';
            OptionMembers = Quote,"Order",Invoice,"Credit Memo","Blanket Order","Return Order";
        }
        field(10; "Document No."; Code[20])
        {
            Caption = 'Document No.';
        }
```

## 2. Read structures into mapping structures

These BC structures are then read into the mapping system. There they serve as the basis for assigning the source tables and fields to the target tables and fields.

## 3. Write the mapping structures back to NAV and configure the assignment

The structures that have been read in are then transferred to NAV.

```
DataMigratePro -t loadconfiguration
```

That is where the relationships are configured: which table from NAV corresponds to which table in BC? Which fields are to be transferred, and which are keys?

## 4. Start the data transfer to BC

With this complete mapping, the transfer of the content can begin. The data from NAV is transferred automatically into the new structures according to the defined relationships and mappings.

```
DataMigratePro -t putdata -s 50001 -d 70103
```

## 5. Alternative procedure

The transfer can also be configured directly through mapping files. Here is an extract for the example above

```
{
    "Provisionsposten": [
        {
            "FieldNo": 1,
            "FieldName": "Entry No.",
            "MappedName": "Entry No_",
            "Validate": true
        },
        {
            "FieldNo": 8,
            "FieldName": "Buchungsdatum",
            "MappedName": "Buchungsdatum",
            "Validate": true
        },
        {
            "FieldNo": 9,
            "FieldName": "Document Type",
            "MappedName": "Document Type",
            "Validate": true
        },
        {
            "FieldNo": 10,
            "FieldName": "Document No.",
            "MappedName": "Document No_",
            "Validate": true
        },
        .
        .
        .
   ],
    "ValidateOnInsert": true,
    "ValidateOnModify": true,
    "ValidateOnDelete": true
}
```

With this Json, steps 1. – 4. are not necessary. The data is then transferred with the following command:

```
DataMigratePro -t putdata -s 50001 -d 70103 -m path/to/mapping/file.json
```

*Status message during the transfer*

About the author

#### Sascha Marquardt

Responsible for the partner programme, the licensing business and commercial project delivery.

Keep reading## More from the IOI blog

[DataMigrate Pro DataMigrate PRO Synch-Service Setting up and running the service bus listener as a Windows service – from the prerequisites to settings.json 24. October 2025 · 4 minutes](https://ioi.gmbh/en/2025/10/24/datamigrate-pro-synch-service/)
[DataMigrate Pro Working with Configuration Data Six ways to move configurations between Business Central, the local installation and a ZIP archive – with the matching commands 23. October 2025 · 2 minutes](https://ioi.gmbh/en/2025/10/23/working-with-configuration-data/)
[DataMigrate Pro Step-by-Step Guide for the Migration to Business Central From the AppSource install to the first migration run – the complete DataMigrate Pro sequence 9. October 2025 · 3 minutes](https://ioi.gmbh/en/2025/10/09/step-by-step-guide-migration-to-business-central/)

## From reading to action. Book your upgrade check.

In the free upgrade check we analyse your current Navision or NAV version and show you the direct path to Business Central – including effort, sequence and a fixed-price range.

[Book a free Upgrade-Check →](/en/business-central-upgrade-check/)
[Give us a quick call: +49 214 8402 3000](tel:+4921484023000)

✓ Directly from any Navision or NAV version

✓ Live test while the legacy system keeps running

✓ C/AL→AL conversion included

✓ Fixed-price range and timeline afterwards
