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: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:
|
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.
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:
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:
Areas are used to generate tasks and task dependencies for the data migration project. |
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:
|
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.
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:
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:
Areas are used to generate tasks and task dependencies for the data migration project. |
Related to | Notes |
---|---|
Define data migration project |
  |