Migrating tables and fields between extensions
Migrating tables and fields between Business Central extensions using migration.json, in both directions along the dependency graph, plus the India Data Migration Toolkit for upgrading from Dynamics NAV 2016 India. It answers questions about moving table ownership, ordering, and constraints.
Path: Business Central on-premises > Upgrade > Related articles > Migrating tables and fields between extensions · tier official · system platform · narrative reviewed (checked by Opus)
Overview
This section covers how to move table and field data from one extension to another during development and deployment. The general page explains the constraints, the roles of the releasing and receiving extensions, the direction of the dependency graph, how the migration.json file is used, and the order of synchronization.
Two task pages follow from that. One covers moving tables and fields to an extension down the dependency graph, where ownership goes to an extension lower in the dependency chain. The other covers moving them up the dependency graph, which needs a transition extension and a two-stage deployment. Start with the general page, then pick the page that matches the direction of your move.
A separate page describes the India Data Migration Toolkit, which supports upgrading from Dynamics NAV 2016 India version to Business Central 2021 release wave 2 in two steps. It covers localization data, not customizations.
Key points
- The general page defines the releasing and receiving extensions, dependency direction, and synchronization ordering for table and field migration.
- migration.json is the file used to describe the transfer of table ownership between extensions.
- Moving down the dependency graph transfers ownership to an extension lower in the dependency chain; it involves table extension objects, data preservation, and field renames (2020 release wave 1 version 16.5).
- Moving up the dependency graph uses a transition extension and a two-stage deployment, and mentions enum type fields (2020 release wave 1 version 16.5).
- The India Data Migration Toolkit upgrades Dynamics NAV 2016 India version to Business Central 2021 release wave 2.
- The India toolkit uses a two-step migration, covers localization data but not customizations, and involves deprecated table handling and permissions reconfiguration.
Learn pages
- India Data migration Toolkit Overview: Specifies India Data Migration Toolkit Overview
- Migrating Tables and Fields Between Extensions: Explains how to migrate tables and fields from one extension to another.
- Moving Tables and Fields to Extensions Down the Dependency Graph: Explains how to move tables and fields from an extension to another extension that is down the dependency graph.
- Moving Tables and Fields to Extensions Up the Dependency Graph: Explains how to move tables and fields from an extension to another extension that is up the dependency graph
Business Central pages and reports
The pages, reports and queries this hub’s Learn pages name (ms.search.form, API reference), joined to the code by exact object id (data/index/docs-objects.json); a page shows the table it runs on.
Learn also names 1 object with no object page: page/19010.
Source: Microsoft Learn (CC BY 4.0). Descriptions are Learn’s own.