Migration paths with Data Migration Tool (DMT)

Data Migration Tool (DMT) is a utility that allows you to migrate data between OneSpan authentication products. You can import CSV files or transfer data from OneSpan Authentication Server Appliance to OneSpan Authentication Server, or vice versa. You can also migrate data from one supported ODBC database to another one.

DMT connects to the administrative interfaces of both the source and the destination systems, or uses a source file as input, to transfer the data to the destination product.

Data Migration Tool (DMT) only supports migration between products of the same product version (major and minor version). Backward and forward progression of data migration are not supported, i.e. you cannot migrate from a newer product to an older one or from an older product to a newer one.

Note that the product version (major and minor) of DMT and the products to migrate must match; however, it is allowed to use DMT with a patch level (third component in version number) equal or lower, e.g. DMT 3.26.2 with OneSpan Authentication Server 3.26.3.

Available migration paths for Data Migration Tool (DMT)

Data Migration Tool 3.26 supports the following migration paths:

From Authentication Server Framework:

  • Authentication Server Framework 3.x (CSV file) to OneSpan Authentication Server 3.26 (ODBC)

From OneSpan Authentication Server:

  • OneSpan Authentication Server 3.26 (ODBC) to OneSpan Authentication Server 3.26 (ODBC)
  • OneSpan Authentication Server 3.26 (ODBC) to OneSpan Authentication Server Appliance/OneSpan Authentication Server Virtual Appliance 3.26

From OneSpan Authentication Server Appliance/OneSpan Authentication Server Virtual Appliance:

  • OneSpan Authentication Server Appliance/OneSpan Authentication Server Virtual Appliance 3.26 to OneSpan Authentication Server Appliance/OneSpan Authentication Server Virtual Appliance 3.26
  • OneSpan Authentication Server Appliance/OneSpan Authentication Server Virtual Appliance 3.26 to OneSpan Authentication Server 3.26 (ODBC)

Data Migration Tool limitations

You should be aware of some limitations when migrating data with Data Migration Tool:

  • If the source system is not taken offline during the (test) migration, some changes made on the source system during the (test) migration will be omitted from the migration and will not appear on the destination system.
  • Changes made on the source system after completing the (test) migration will not appear on the destination server automatically. There is no connection between the data stores. If changes are made on the source system, they need to be made on the destination system as well.
  • Data Migration Tool does not allow data migration if maker–checker authorization is enabled on either the source or the destination system. Both, the source and the destination system need to have maker–checker authorization disabled.

  • Replication

    Do not set up replication between the source and destination data stores.