Data Migration

The recommended approach for any data migration is to upload the original zip files that the Data Collector produced.    
This can be done via the UI
If you no longer have those zip files, or you have a very large number of zip files then use the steps outlined below

Note: Do not uninstall your existing version of Transformation Advisor until you have exported any data necessary for your migration.

The steps for data migration are slightly different depending on where you have deployed Transformation Advisor

Data Migration on Red Hat OpenShift Container Platform

Complete the following steps to migration your data

Back up your existing database

  1. Export your data directory from the couchDB container
  2. Export the data you currently have in Transformation Advisor
    • Use the bulk export API in TA 2.5. Full details can be found here
    • /advisor/v2/collectionArchives/bulkExport
    • /advisor/v2/workspaces/{workspaceId}/collectionArchives/bulkExport

Install Transformation Advisor

  1. Install Transformation Advisor 3.0 on a different OCP cluster
    • If you do not have another OCP cluster available then complete the following steps
      1. Detach the PersistentVolumeClaim that is used by Transformation Advisor 2.5.x from the Transformation Advisor instance. Doing this will allow you to keep the Transformation Advisor data when you uninstall Transformation Advisor 2.5.x. If you need to revert to Transformation Advisor 2.5.x for any reason, you can re-install 2.5.x and specify the preserved PersistentVolumeClaim as an existingClaim in the configuration. Read Preserving the PersistentVolumeClaim for details on how to detach the PersistentVolumeClaim.
      2. Uninstall your existing Transformation Advisor 2.5.x
      3. Install Transformation Advisor 3.0

Import your data

  1. Import your exported data into Transformation Advisor 3.0 using the bulkImport API. Full details can be found here
    • /advisor/v2/collectionArchives/bulkImport


  1. If you have installed Transformation Advisor on a new cluster you should not delete your old Transformation Advsior instance