Migration procedure

This topic shows the procedure to ingest metadata in Collibra via lineage harvester (Tableau integration v2) and migrating your Tableau assets.

Steps

  1. Integrate Tableau via Jobserver (Tableau integration v1).
    For complete information, see Working with Tableau via Jobserver.
  2. Integrate Tableau via the lineage harvester or Edge (Tableau integration v2).
    When integration is complete, you will have:
    • A domain in Collibra with custom Tableau integration v1 assets and their custom attributes and relations.
    • A domain in Collibra with Tableau integration v2 assets.
  3. For every out-of-the-box v2 attribute type for which the value was manually edited in the v1 assets, create a custom asset type in Collibra, to ensure that the values of those attribute types in your v1 assets are not overwritten. For more information, see About the Tableau migration.
  4. In the domain to which you will import assets in step 9, create a view with the characteristics you want to migrate.
    Important Any characteristics that are not included in the view will be ignored during export.
  5. Export Tableau v1 assets to an Excel file. Name this file "v1".
  6. Export Tableau v2 assets to an Excel file. Name this file "v2".
  7. Map the assets in files v1 and v2.
    Tip  To accomplish this mapping, you can perform a VLOOKUP based on the asset Name in file v1. For more information, see Microsoft's documentation on how to use the VLOOKUP function in Excel.
  8. Copy the required characteristics from file v1 to file v2.
  9. Once you've reviewed your v2 file, to see that column headers and values look correct, you can import the file back into Collibra.
  10. Verify that the metadata that you manually added to your integration v1 assets has been retained in your v2 assets.
  11. If you've reviewed the migration results and everything looks fine, you can delete your Tableau integration v1 assets and any assets of custom asset types.

Naming convention

When you synchronize Tableau, Collibra follows a strict naming convention for the names of the new assets. Each asset has a display name and full name. The full name represents the asset path from asset to the database it belongs to. You can freely edit the display name. However, you should never edit the full name, because Data Catalog needs it for a successful migration. Changing the full name may also break the synchronization process.

Warning We highly recommend that you not edit the full names of any Tableau assets. Doing so will likely lead to errors during the migration and synchronization process.