---
title: "Define data migration setup"
slug: "define-data-migration-setup"
description: "Migrate AX2012 data to D365 F&SCM with our step-by-step guide on setting up data migration records and managing project areas effectively."
tags: ["Task topic"]
status: "update"
updated: 2026-10-05T12:11:30Z
published: 2026-10-05T12:11:30Z
canonical: "docs.staedean.com/define-data-migration-setup"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Define data migration setup

When you have selected the AX2012 tables which data you want to migrate to D365 F&SCM, the related data migration setup records are created. Complete the created data migration records.

### Steps

1. Click **Connectivity studio - Integration Design**.
2. Click **Projects**.

> [!NOTE]
> **Note**
> 
> Your currently active project is opened. This is the project as shown in the **Project** field on the **Integration design** workspace. Make sure your data migration project is selected.
3. On the **Action Pane**, click **Design**.
4. Click **Migrate**.
5. Click **Edit**.
6. In the list, find and select the desired data migration record.
7. If in D365 F&SCM no table exists with the same name as a selected AX2012 table, no table is automatically set as target table. In this case, manually define the desired target table.

In the **Target table** field, enter or select a value.
8. Assign the applicable status to the data migration record.

You can only assign a status as set up for the data migration project.

In the **Status** field, enter or select a value.
9. Define the area for the data migration setup record.

Use data migration areas to:

Areas are used to generate tasks and task dependencies for the data migration project.

You can only define areas that are set up for the data migration project.

In the **Area** field, enter or select a value.
  - Group data migration setup records, for example, by functional area.
  - Assign a level to data migration setup records.
10. If several data migration setup records belong to the same area, define the sublevel of each of the records within the area.

When tasks are generated, the sublevel determines the sequence of tasks within the area.

In the **Area sublevel** field, enter a number.

> [!NOTE]
> **Note**
> 
> Best practice: Do not use consecutive sublevel numbers. This makes it easier to add records later.
11. Close the page.
12. Close the page.

<style> p[data-block-id] {font-size:1rem;} ul li p[data-block-id] {margin-bottom: 0;} ul[data-type="taskList"] li div p[data-block-id] {margin-bottom: 0;} ol li p[data-block-id] {margin-bottom: 0;} table tbody th p[data-block-id] { margin-bottom: 0;} blockquote p[data-block-id] {margin-bottom: 0 !important;} &nbsp;p[data-block-id]:empty::after {content: "\00A0";} </style>