What is migrated?

Celonis Product Documentation

What is migrated?

Data	Migrated?	Notes
All workspaces and analyses	Yes	Workspaces are migrated as packages into a new space.
Bookmarks	Yes	Includes shared and individual bookmarks
Published selections	Yes	Published selections are migrated as pinned selections.
Data connection	Yes
Member permissions	Yes	Includes permissions of users, groups, and applications
Analyst permissions	Partially	Includes permissions of users, groups, and applications For more information, see Permissions.
Analysis URLs	No	Includes: Shared selections Public links Links In button components
Analysis links in Transformation Center	No
PDF reports	No
PyCelonis APIs	No

Tip

The migration tool cannot be used more than once. As a test, you can migrate a few workspaces using Copy to Studio.

Content

A new, self-contained space named Migration Space will be created in Studio to hold all content migrated from Process Analytics. Any analyses you might already have in Studio will not be affected.

Draft is migrated to Studio, Published version is migrated to Apps. You do not need to publish

Inside Migration Space:

Each workspace in Process Analytics will be copied to Studio as a package.
Each analysis in Process Analytics will be copied to Studio as an analysis.
All workspace, analysis, and sheet names and IDs will be kept.
The published version of the analysis will be in Apps .
The draft version of the analysis will be in Studio .

Also migrated with each analysis:

Bookmarks, both shared and individual
Published selections, as Pinned Selections

Note

The migration tool will not create any views.

Data connection

The correct data model variable(s) will be created in each new package and automatically connected to the analyses in the package.

Note

The migration tool will not create any knowledge models.

Permissions in the Process Analytics Migration

All permissions of users with the Member role will be migrated. Member permissions are indicated by the icon. These users will immediately be able to view their new analyses in Studio.

However, some permissions of users with the Analyst role may not be migrated. Analyst permissions are indicated by the icon.

This is because the Analyst permissions in Process Analytics and Studio do not match exactly:

Process Analytics	Studio
Create analyses, Edit all analyses, and Edit workspace can be assigned separately to a user on a workspace.	Create analyses, Edit all analyses, and Edit workspace are bundled together into Edit package.
Delete all analyses and Delete workspace can be assigned separately to a user on a workspace.	Delete all analyses and Delete workspace are bundled together into Delete package.
A user can Delete workspace/Manage permissions on a workspace without being able to Edit workspace.	Edit package is required for Delete package/Manage permissions.
Edit analysis/Delete analysis can be assigned to a user on just one analysis in the workspace.	Edit analysis/Delete analysis do not exist. Edit package/Delete package allows a user to edit/delete all analyses in the package, or none.

Any analysts who have unmigrated permissions may not be able to edit their new analyses in Studio until you give them the required Studio permissions. For each of these users, you should review what each Studio permission allows you to do and decide on the appropriate permissions to give after migrating.

Note

The migration tool will not give the following Studio permissions to any user on the migration space:

Edit space: Allows you to rename or change the icon of the migration space
Delete space: Allows you to delete the entire migration space

Additionally, the following Process Analytics permissions have been deprecated in Studio:

Export content: Instead, you can use the pull command in Content CLI to export analyses as JSON files.
Edit analysis, Delete analysis, and Manage permissions: Asset level editing is not allowed because there can be dependencies between assets in a package.

Permission migration methods

There are two methods of migrating Analyst permissions:

Standard: Recommended for most permission setups. There will be fewer permissions that are not migrated compared to the restricted method, but users may get more editing privileges in Studio than they had in Process Analytics.
Restricted: Recommended for complex permission setups. Users will get the minimum possible permissions in Studio, only receiving Studio permissions if they have sufficient Process Analytics permissions. Compared to the standard method, there will be more permissions that are not migrated.

When choosing the permission migration method, consider your team’s needs when it comes to viewing and editing content. Remember that permissions at the data level will still apply either way.

Important

If you choose standard permission migration, users who have permission to Edit all analyses on a workspace in Process Analytics will receive increased permissions on the new package in Studio.

In addition to being able to edit all analyses in the package, they will be able to:

Create analyses in the package.
Edit the package itself.
Move the analyses to other packages that they can edit.
Move the package to other spaces where they can create packages.

Before choosing standard permission migration, verify that these additional permissions are acceptable. Users will not be able to see any data that their data permissions do not allow them to see.

Examples

EXAMPLE 1: ALL WORKSPACE PERMISSIONS

The user has all permissions on a Process Analytics workspace. After the workspace is migrated, the user gets all permissions on the Studio package.

EXAMPLE 2: INCOMPLETE WORKSPACE PERMISSIONS (NO EDIT WORKSPACE)

The user has all permissions except for Edit workspace on a Process Analytics workspace. The permissions the user gets on the Studio package depend on which method is chosen.

EXAMPLE 3: INCOMPLETE WORKSPACE PERMISSIONS (ONLY CREATE ANALYSES)

The user has Create analyses on a Process Analytics workspace. After the workspace is migrated, the user gets no permissions on the Studio package.