1. To-Increase Dynamics 365 for Finance & Operations
  2. Connectivity studio
  3. General
  4. Do a data migration from AX2012 to D365 FO

Design data migration

To design a data migration from AX2012 to D365 FO, you can use the ODBC mapping generator. Using a Database connector with an ODBC connection to the AX2012 database, you can easily map the desired AX2012 tables to the related D365 FO tables.


Application Consultant Application Consultant Start Start Select tables to be mapped Select tables to be mapped For a data migration from AX2021 to D365 FO, you can generate messages based on data migration setup records. Before you can do so, select the AX2012 tables which data you want to migrate to D365 FO. As a result, the related data migration setup records are created with the selected AX2012 tables as source table. If in D365 FO a table exists with the same name, this is automatically set as target table. To select the tables from the AX2021 database, the default Database connector, as defined for the data migration project, is used. Procedure 1. Click Connectivity studio Integration Design. 2. Click Projects. 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. In the Migration group, click Migrate. 5. Click Select tables. 6. Use the Filter to find the desired source table. 7. In the upper list select the desired source tables. 8. In the bottom section, click + (Add). 9. Click OK. 10. Close the page. 11. Close the page. Define data migration setup Define data migration setup When you have selected the AX2012 tables which data you want to migrate to D365 FO, the related data migration setup records are created. Complete the created data migration records. Procedure 1. Click Connectivity studio Integration Design. 2. Click Projects. 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. In the Target table field, enter or select a value. 8. In the Status field, enter or select a value. 9. In the Area field, enter or select a value. 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 defines the sequence of the tasks within the area. In the Area sublevel field, enter a number. Note: Best practice: Do not use consecutive sublevel numbers. This makes it easier to squeeze in additional records later. 11. Close the page. 12. Close the page. Generate data migration message Generate data migration message You can generate messages based on the data migration setup records. If you generate a message, this is generated: An ODBC document based on the source table in AX2012. A D365FO document based on the target table in D365 FO. A message with the: Default Database connector of the data migration project as source connector. Default D365FO connector of the data migration project as target connector. Generated ODBC document as source document. Generated D365FO document as target document. Mapping of the document record and record fields that exist in both the source document and the target document. Be aware that a generated message often needs some fine-tuning due to differences between the AX2012 table and D365FO table. Procedure 1. Click Connectivity studio Integration Design. 2. Click Projects. 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. In the Migration group, click Migrate. 5. In the list, find and select the desired data migration records. 6. Click Create message. 7. Click OK. 8. Close the page. 9. Close the page. Review and complete data migration setup Review and complete data migration setup As a result of the message generation, this is generated: An ODBC document based on the source table in AX2012. A D365FO document based on the target table in D365 FO. A message with the: Default Database connector of the data migration project as source connector. Default D365FO connector of the data migration project as target connector. Generated ODBC document as source document. Generated D365FO document as target document. Mapping of the document record and record fields that exist in both the source document and the target document. The message is added to the data migration setup record. For each data migration setup record, review and complete the generated documents and message. Procedure 1. Click Connectivity studio Integration Design. 2. Click Projects. 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. In the list, find and select the desired data migration record. 6. Click to follow the link in the Message field. 7. Sub-task: Review and complete source document. 8. On the Action Pane, click Design. 9. In the Source group, click Document. 10. Close the page. 11. Sub-task: Review and complete target document. 12. On the Action Pane, click Design. 13. In the Target group, click Document. 14. Close the page. 15. Sub-task: Review and complete message. 16. In the list, click the link in the selected row. 17. Close the page. 18. Close the page. 19. Sub-task: Complete data migration setup record. 20. On the ODBC mapping generator page, click Edit. 21. In the list, find and select the desired data migration setup record. 22. In the Status field, enter or select a value. 23. Select the Active check box. 24. Close the page. 25. Close the page. Notes RecIdOn data migration, in D365 FO, new RecIds are created for records, which do not match with the AX2012 RecIds. On migration message generation, if an AX2012 field refers to a RecId, it is assumed that the related record is already migrated. Therefore, on the migration message, the field mapping is marked as 'External reference'. Applying external references, makes it possible to link an AX2012 RecId to the related D365 FO RecId.You are advised to check the fields that are marked as external reference. Is the related table migrated before the current table is migrated? If not, you can solve it in one of these ways:Add the data migration of the applicable table to the data migration setup. Add it before the table migration setup for the current table. In this case, on the migration message, for the applicable field mapping, you can keep the 'External reference' check box selected.Add the applicable table to the generated source document and target document of the migration message for the current table. Also add the related record and field mapping to the generated migration message for the current table. In this case, on the migration message, for the applicable field mapping, clear the 'External reference' check box.For more information, refer to: Apply external reference.Financial dimensionsFinancial dimensions are also handled as RecIds. This is fine if the applicable financial dimensions are migrated before the current table is migrated.You are advised to check the financial dimension fields. Is the related financial dimension migrated before the current table is migrated? If not, you can solve it in one of these ways:Add the data migration of the applicable financial dimension tables to the data migration setup. Add these before the table migration setup for the current table. In this case, on the migration message, for the applicable financial dimension field mapping, you can keep the 'External reference' check box selected.For each applicable financial dimension, add a separate field to the source document and target document. Also add the related field mapping to the generated migration message for the current table. For each financial dimension field mapping, select the Dimension set or the Ledger field option and fill in the related fields. Also, remove the remove the original financial dimension field mapping from the message.For more information, refer to:Apply dimension setApply ledger Generate tasks for data migration project Generate tasks for data migration project When you have reviewed and completed the data migration setup records with related message and documents, you can generate tasks based on the records. The tasks are created based on the areas and sublevels as assigned to the data migration setup records in this way: A root task is created for the record which area has the lowest level and which area sublevel is the lowest as well. A task is created beneath the root task for the record with the same area and the next area sublevel. If such a record does not exist, a task is created for the record which area is the next level and which area sublevel is the lowest for that area. A task is created beneath the previous task for the record with the same area and the next area sublevel. If such a record does not exist, a task is created for the record which area is the next level and which area sublevel is the lowest for that area. Step 3 is repeated till a task is created for each record. To each created task, the message is added as defined for the related data migration setup record. Note: If records exist with the same area and area sublevel, only one task is created based on these records. And for all these records, the messages are added to this one task. On task generation, when a message is added to a task, and the related data migration setup record is: Active, the related message action is set to 'Run'. So, if the task is run, the message is run. Not active, the related message action is set to 'Skip'. So, if the task is run, the message is not run. Example For a data migration project, these data migration setup records are used: Note the use of the status, areas, area sublevels, and record activation. The generated task structure, as shown on the Project page, is: The generated tasks with added messages, and the set message actions are: Task Message Action Area: 10 level: 10 CUSTGROUP Run VENDGROUP Skip Area: 20 level: 10 INVENTTABLE Skip Area: 30 level: 20 VENDTABLE Run Area: 30 level: 30 PURCHTABLE Skip Area: 40 level: 20 CUSTTABLE Run Area: 40 level: 30 SALESTABLE Skip Procedure 1. Click Connectivity studio Integration Design. 2. Click Projects. 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 Create tasks. 6. To answer the question, click OK. 7. Close the page. 8. Sub-task: Review the generated tasks. 9. Refresh the Project page. 10. Expand the Tasks section. 11. On the Action Pane, click Design. 12. In the Tasks group, click Tasks. 13. Close the page. 14. Close the page. End End

Activities

Name Responsible Description

Select tables to be mapped

Application Consultant

For a data migration from AX2021 to D365 FO, you can generate messages based on data migration setup records. Before you can do so, select the AX2012 tables which data you want to migrate to D365 FO. As a result, the related data migration setup records are created with the selected AX2012 tables as source table. If in D365 FO a table exists with the same name, this is automatically set as target table.

To select the tables from the AX2021 database, the default Database connector, as defined for the data migration project, is used.

Define data migration setup

Application Consultant

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

Generate data migration message

Application Consultant

You can generate messages based on the data migration setup records. If you generate a message, this is generated:

  • An ODBC document based on the source table in AX2012.
  • A D365FO document based on the target table in D365 FO.
  • A message with the:
    • Default Database connector of the data migration project as source connector.
    • Default D365FO connector of the data migration project as target connector.
    • Generated ODBC document as source document.
    • Generated D365FO document as target document.
    • Mapping of the document record and record fields that exist in both the source document and the target document.
Be aware that a generated message often needs some fine-tuning due to differences between the AX2012 table and D365FO table.

Review and complete data migration setup

Application Consultant
As a result of the message generation, this is generated:
  • An ODBC document based on the source table in AX2012.
  • A D365FO document based on the target table in D365 FO.
  • A message with the:
    • Default Database connector of the data migration project as source connector.
    • Default D365FO connector of the data migration project as target connector.
    • Generated ODBC document as source document.
    • Generated D365FO document as target document.
    • Mapping of the document record and record fields that exist in both the source document and the target document.
  • The message is added to the data migration setup record.
For each data migration setup record, review and complete the generated documents and message.

Generate tasks for data migration project

Application Consultant

 		When you have reviewed and completed the data migration setup records with related message and documents, you can generate tasks based on the records.
The tasks are created based on the areas and sublevels as assigned to the data migration setup records in this way:
  1. A root task is created for the record which area has the lowest level and which area sublevel is the lowest as well.
  2. A task is created beneath the root task for the record with the same area and the next area sublevel. If such a record does not exist, a task is created for the record which area is the next level and which area sublevel is the lowest for that area.
  3. A task is created beneath the previous task for the record with the same area and the next area sublevel. If such a record does not exist, a task is created for the record which area is the next level and which area sublevel is the lowest for that area.
  4. Step 3 is repeated till a task is created for each record.
To each created task, the message is added as defined for the related data migration setup record. Note: If records exist with the same area and area sublevel, only one task is created based on these records. And for all these records, the messages are added to this one task.
On task generation, when a message is added to a task, and the related data migration setup record is:
  • Active, the related message action is set to 'Run'. So, if the task is run, the message is run.
  • Not active, the related message action is set to 'Skip'. So, if the task is run, the message is not run.

Example

For a data migration project, these data migration setup records are used:

Note the use of the status, areas, area sublevels, and record activation.
The generated task structure, as shown on the Project page, is:
The generated tasks with added messages, and the set message actions are:

Task

Message

Action

Area: 10 level: 10

CUSTGROUP

Run

VENDGROUP

Skip

Area: 20 level: 10

INVENTTABLE

Skip

Area: 30 level: 20

VENDTABLE

Run

Area: 30 level: 30

PURCHTABLE

Skip

Area: 40 level: 20

CUSTTABLE

Run

Area: 40 level: 30

SALESTABLE

Skip


See also

Provide feedback