Data migration

When you migrate from the Sterling™ Order Management System on-premises platform to the SaaS platform, you must migrate your data.

Data migration includes, master data, configuration data, and transaction data.

Migrating configuration data

You can migrate your configuration data from on-premises to the on-cloud platform by using the Configuration Deployment Tool (CDT).

  1. Download the latest developer toolkit from Self Service to your local workstation and set it up.

    For more information, see Setting up a developer toolkit environment.

  2. Export the Configuration Deployment Tool (CDT) from on-premises and import the same to a local developer toolkit.
  3. After you successfully import the configuration data to your local developer toolkit, run the functional or regression test suite through scripts or manually perform the functional or regression testing. This ensures that all the configurations are successfully imported, functionality is not broken, and the application is functioning as expected.
  4. Perform a CDT export from the developer toolkit, and import the configuration data to the target cloud environment. Run the functional or regression test suite through scripts or manually perform the functional or regression testing.
  5. Verify the configuration data in your local developer toolkit and export the data from the developer toolkit to the target cloud environment and verify.

Master data migration

To import your master data, use data feeds and integration servers. For example, catalog data, inventory supply, or external demands.

To migrate the master data, use data feeds that leverage IBM® MQ-based integration approach.

Do not use the Configuration Deployment Tool (CDT) to migrate your master data, as the large volume might cause an out-of-memory error.
Note:
  • For data migration, the Secure File Transfer Protocol (SFTP) is not supported.
  • Data feeds must be through IBM MQ and not FTP as the file operations are not permitted in the on-cloud platform.

Transaction data migration

There are no specific tools for migrating transaction data from on-premises to Sterling Order Management System SaaS. You can instead use APIs for data migration. Use the importOrder API for movement of order from your on-premises instance to a cloud instance. Alternatively, the restoreOrder API provided by the application restores data from history tables to transaction tables. You can instead customize the restoreOrder API to retrieve order data from transaction tables and transfer it to an external order repository.