Additional options
Cancel a migration
If you want to change the migration settings before a migration has run, you must first cancel the migration. You cannot cancel a migration or change the settings once the migration has started running.
To cancel a migration, click View migration details > Cancel migration in the banner at the top of Process Analytics when the migration is in queue.
![]() |
Notify all users by email of the migration to Studio
You can send a system-generated email to all users notifying them of the migration. To do this, select the Notify all users by email of the migration to Studio checkbox when setting up your migration.
Below is what the email will look like. The team name and admin email will be adapted to your situation.
![]() |
Unlock a workspace
By default, all workspaces and analyses will automatically be locked for editing after the migration has run successfully. This means all users have read-only access.
![]() |
To unlock a workspace, click > Unlock
in the workspace options menu.
Note
Changes made to an unlocked workspace will not sync to Studio. You must copy the workspace to Studio again to avoid losing the changes.
Reorganize content in Studio
You can reorder packages within a space, or analyses within a package, by dragging and dropping them on the side panel.
To move a package to a different space:
Make sure you are in Studio
.
On the package you want to move, click
> Move to Space
.
Choose the target space from the dropdown.
Click Move.
Important
Moving packages using the above method is the only way to keep bookmarks. If you use Copy to , your bookmarks will not be copied with the package.
To move an analysis to a different package:
Make sure you are in Studio
.
On the analysis you want to move, click
> Copy to
.
Follow the steps to select the target team, space, and package.
Click Copy.
Important
The above method will not copy bookmarks. If you want to keep your bookmarks, you can use Content CLI to pull the bookmarks from the original analysis and push them into the copy. For more information, see the Content CLI documentation.