There are two different paths to help you migrate from Treasure Data Console (v4) to Treasure Data Console (v5): a full migration or a testing scenario where you can test a few parent segments before performing a full migration.

Full Migration

A full migration migrates everything under a Parent segment at once; no partial migration is supported. The following list identifies the details behind a full migration:

  • Move objects: All objects under a parent segment are moved from Treasure Data Console (v4) to Treasure Data Console (v5). The objects are moved, not duplicated in Treasure Data (v5).
  • Non-synchronized and irreversible: The migration operation is not reversible. Additionally, Treasure Data cannot distinguish objects moved from v4 to v5.
  • Object IDs: The object IDs stay the same after migration. For example, an activation ID in a workflow reference does not change.

Test Treasure Data Console (v5) Before Migration

You can select a few Parent Segments and move them to Treasure Data Console (v5), where you can test the segments before requesting a full migration.

None of the existing segments or other objects are migrated until you complete your testing and request a full migration.

  • No labels