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

Define data migration project

Use a project as the basis for each data migration. Most connectivity elements are linked to a project, for example, documents, connectors, and tasks. Because these elements are related to a project, use a project to deploy a data migration.

For each data migration project, at least define the:
  • Applications that are used in the project.
  • Default connectors.
  • Data migration statuses.
  • Data migration areas.


Application Consultant Application Consultant Start Start Define project

Define project

Use a project as the basis for each integration. Most connectivity elements are linked to a project, for example, documents, connectors, and tasks. Because these elements are related to a project, you can also use a project to deploy connectivity setup and do version management.

For each project, you can also define the:
  • Subprojects that are run if you run the project.
  • Applications that are used in the project.
  • Default connectors.
  • Web service applications.

 Set up D365 FO connector Set up D365 FO connector Set up a connector of type D365 FO. Use this type to directly connect to a D365 FO database. Procedure 1. Click Connectivity studio Integration Design. 2. Click the Connectors tab. 3. Click New. 4. In the Connector field, type a value. Note: You are advised to not include, in the connector name, the name of the application to which you connect. Use the Application field to define the applicable application for the connector. 5. In the Project field, enter or select a value. 6. Define the applicable application for the connector. For a D365 FO connector, for example, select a 'D376 FO' application. In the Application field, enter or select a value. Note: - You can only select an application that is defined for the applicable project. You can define project applications on the Projects page. - You can type any existing application name, whether it is defined as project application or not. If the typed application is not defined as project application, it is automatically added to the project applications. 7. Make sure, the Connector type is D365 FO. 8. Sub-task: Set properties. 9. On the Properties tab, in the Target company field, enter or select a value. 10. You can use a template company as source company. If you run a message, the data is exported from the template company and imported in the target company. In a template company, you can, for example, define generally applicable master data. You can use this to set up the master data for a new company. To be able to use a template company, in the Connectivity studio parameters, define the template company for each target company. You can define several template companies. For example, with country-specific or industry-specific data. Select Yes in the Template company field. Note: Do not define source companies if you want to use a template company. 11. Sub-task: Select custom handler. 12. Expand the Custom section. 13. In the Handler field, you can enter or select a custom handler class. 14. Sub-task: Define source companies. 15. Define the source companies for the connector. You can define the source company for a connector in these ways: - One specific source company. - Several source companies. - No source company: Do not define a source company if you want to use the active company as the source company. As a result, the company from which a message is run is used as the source company. Expand the Source companies section. Note: Do not define source companies if you want to use a template company. 16. Click New. 17. In the Company accounts ID field, enter or select a value. 18. Sub-task: Define target companies. 19. You can define several target companies for the connector. Only use this to import simple single-level master data. For example, to initialize a company. Expand the Target companies section. Note: - You can use the target companies here in combination with the target company as defined on the Properties tab. - If import of a record fails in one company, the import of the records is undone in all defined target companies. 20. Click New. 21. In the Company accounts ID field, enter or select a value. 22. Sub-task: Set advanced options. 23. Expand the Advanced options section. 24. Select Yes in the Cross company disabled field. 25. Close the page. Notes You can change the type of an existing connector. If you do so, also fill in the applicable fields. For more information, refer to the topic about the setup of the newly chosen connector type.The environment type does not apply to a D365 FO connector. Set up Database connector

Set up Database connector

Set up a connector of type Database. Use this type to directly connect to an external database. This external database can be an on-premises database or a cloud database.
If you want to connect to an external database via ODBC and you run D365 FO:

  • In the cloud, use an Azure Service Bus to connect to the external database.
  • On-premises, you can connect to the external database without an Azure Service Bus. 
  • On-premises, you can also connect without an Azure Service Bus and additionally use Direct SQL to export data to the external database.

You can also directly connect to an Azure SQL database.

 

 Set up default connectors for data migration project Set up default connectors for data migration project You can migrate data from an AX2012 database to D365FO. To generate data migration messages based on selected tables, default connectors are required on the project. Define these default connectors for your data migration project: Database connector to connect to the AX2012 database. D365FO connector to connect to the current D365FO environment. Make sure, the right application is defined for these connectors. 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. Click Edit. 4. Expand the Default connector section. 5. Click New. 6. In the Connector field, enter or select a value. 7. In the Initialize field, you can keep the default value 'No'. 8. Close the page. Set up data migration statuses Set up data migration statuses You can set up statuses that you can apply to the data migration setup records. Using statuses is not mandatory. Statuses are useful to monitor the data migration setup. 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 Status. 5. Click New. 6. In the Status field, type a value. 7. Close the page. 8. Close the page. Set up data migration areas Set up data migration areas Set up data migration areas. Use data migration areas to:Group data migration setup records, for example, by functional area.Assign a level to data migration setup records.Areas are used to generate tasks and task dependencies for the data migration project. 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. Click Area. 4. Click New. 5. In the Area field, type a value. 6. In the Level field, enter a number. Note: Best practice: Do not use consecutive level numbers. This makes it easier to squeeze in additional areas later. 7. Close the page. 8. Close the page. End End

Activities

Name Responsible Description

Define project

Application Consultant

 		Use a project as the basis for each integration. Most connectivity elements are linked to a project, for example, documents, connectors, and tasks. Because these elements are related to a project, you can also use a project to deploy connectivity setup and do version management.
For each project, you can also define the:
  • Subprojects that are run if you run the project.
  • Applications that are used in the project.
  • Default connectors.
  • Web service applications.

Set up D365 FO connector

Application Consultant

Set up a connector of type D365 FO. Use this type to directly connect to a D365 FO database.

Set up Database connector

Application Consultant

Set up a connector of type Database. Use this type to directly connect to an external database. This external database can be an on-premises database or a cloud database.
If you want to connect to an external database via ODBC and you run D365 FO:

  • In the cloud, use an Azure Service Bus to connect to the external database.
  • On-premises, you can connect to the external database without an Azure Service Bus. 
  • On-premises, you can also connect without an Azure Service Bus and additionally use Direct SQL to export data to the external database.

You can also directly connect to an Azure SQL database.

 

Set up default connectors for data migration project

Application Consultant
You can migrate data from an AX2012 database to D365FO. To generate data migration messages based on selected tables, default connectors are required on the project.
Define these default connectors for your data migration project:
  • Database connector to connect to the AX2012 database.
  • D365FO connector to connect to the current D365FO environment.
Make sure, the right application is defined for these connectors.

Set up data migration statuses

Application Consultant

 		You can set up statuses that you can apply to the data migration setup records. 
Using statuses is not mandatory. Statuses are useful to monitor the data migration setup.

Set up data migration areas

Application Consultant

 		Set up data migration areas. Use data migration areas to:
  • Group data migration setup records, for example, by functional area.
  • Assign a level to data migration setup records.
Areas are used to generate tasks and task dependencies for the data migration project.

See also

Provide feedback