1. Data Management
  2. Connectivity Studio
  3. General
  4. Do a data migration from AX2012 to D365 FO

Data migration prerequisites

Before you design the data migration, install an XPO in AX2012 to manage the enum migration.


Application Consultant Application Consultant Install XPO on AX2012 Install XPO on AX2012 In D365 FO, enums can be extendable. For extendable enums, the enum value numbering is not fixed. Therefore, an enum value number in AX2012 can be different from the number of the related enum value in D365 FO. To prevent a mismatch of enum values when migrating data, migrate enums based on the enum value name instead of the enum value number. To do so, on the AX2012 environment: Download and extract the SharedProject_Ax2012PrepMigrateD365FO ZIP file. Install the SharedProject_Ax2012PrepMigrateD365FO.xpo file. As a result, these enum transformation tables are installed in AX2012: BisDmMigrationtableFieldEnum BisDmMigrationenumValue Run the BisDmMigrationCreateEnumValues job. As a result, you can migrate the enum values based on the names instead of the numbers. Notes When data migration messages are generated, the enum value transformations are taken into account. As a result, on the source document (ODBC document), for an enum field, the:Type is set to String instead of Integer.Enum name is filled.Example: Start Start End End

Activities

Name Responsible Description

Install XPO on AX2012

Application Consultant

In D365 FO, enums can be extendable. For extendable enums, the enum value numbering is not fixed. Therefore, an enum value number in AX2012 can be different from the number of the related enum value in D365 FO.

To prevent a mismatch of enum values when migrating data, migrate enums based on the enum value name instead of the enum value number. To do so, on the AX2012 environment:
  1. Download and extract the SharedProject_Ax2012PrepMigrateD365FO ZIP file.
  2. Install the SharedProject_Ax2012PrepMigrateD365FO.xpo file. As a result, these enum transformation tables are installed in AX2012:
    • BisDmMigrationtableFieldEnum
    • BisDmMigrationenumValue
  3. Run the BisDmMigrationCreateEnumValues job.
As a result, you can migrate the enum values based on the names instead of the numbers.

Provide feedback