Is the migration tool right for me?
If your migration has specific requirements or you need greater flexibility, the migration tool might not be right for you. Here is a comparison of the Migration Tool and Copy to Studio:
Functionality | Migration Tool | Copy to Studio |
---|---|---|
Migrate workspace and analysis content | All workspaces | One workspace |
Migrate bookmarks | Yes | Yes |
Migrate published selections | Yes | Yes |
Migrate data connection | Yes | Yes |
Migrate permissions | Yes | Optional |
Option for standard or restricted permission migration | Yes | Restricted permission migration only |
Migrate dependencies | No | No |
Button components that open an analysis using Open Document | Yes | No |
Option to notify end users by email of the migration to Studio | Yes | No |
Workspace locking | Yes | Optional |
Yes | Analysis banner only | |
Migration report | Yes | No |
Rename packages during setup | No | Yes |
Run time | Scheduled overnight | Immediate |
Usage | One time | Unlimited |
Accessible by | Admins only | Analysts and admins |
Consider the following factors before migrating:
What data and how much data you are migrating: The migration tool is designed to migrate all Process Analytics workspaces in a single migration. If you do not want to migrate everything, or if you want to migrate in batches, use Copy to Studio. For example, this might apply if most of your analyses are obsolete or have been migrated already.
What organizational structure you are planning to have in Studio: The migration tool migrates content into one space. You can reorganize content after it has been migrated, but it might be easier to use Copy to Studio if you plan to change the structure drastically, for example by moving the packages to different spaces. To learn about the differences in content organization between Process Analytics and Studio, see Content organization.
If you want to run a test migration: If you are still unsure about what the migrated content or permissions will look like in Studio, use Copy to Studio to do a test run first. You cannot use the migration tool more than once.