Migrating a project allows you to transfer your project to a different license. Project migration can be used for project handover and delivery, transferring projects between teams, or placing projects in a license dedicated to retaining past projects. Once a project is migrated, the origin license team will no longer have access to the project, unless they are migrated to the destination license too. 

• Requirements
• Migrating a project in the same region
  • User migration details
• Migrating a project to a different region

Requirements

To move a project to a different license you need the following capabilities and permissions:

• The destination license must have an available project slot to receive a migrating project.
• License administrator or project owner license permissions in the source license.
• License administrator or content creator license permissions in the destination license.

Migrating a project in the same region

When the destination license is in the same region, you can migrate a project entirely in Revizto Workspace. This migration type maintains most Revizto Workspace settings for the project, and maintains the project tags. Revizto automatically applies authentication methods for migrated users based on the authentication method settings in the destination license. Please see Configuring single sign-on authentication for more details on Revizto authentication methods.

To start a project migration:

1. Sign in to ws.revizto.com.
   • If you are a member of several licenses, ensure that the correct license is selected.
2. Go to Tools, then select My Projects. 

3. Select the project to be migrated. 
4. Click the edit icon next to the License field.
5. Select the destination license to migrate the project and click Change.

Clash tests and issue location tags are a feature of the Revizto + license. Projects moved to a standard license can no longer user clash tests or location tags. Previously existing issues generated by clash tests or using location tags will stay available.

User migration details

Individual tool settings do not migrate with users. However, settings can be saved by using Export and brought into the new project with Import . For detailed instructions on migrating tool settings, such as search sets or appearance templates, see Importing and exporting tool settings. 

The number of users that are migrated is determined by the available user capacity. Migrated users are added to the destination license with the guest role when able, or collaborator role. For more information on license roles see Roles in the license. 

Revizto assigns each user a project role in the new license that matches their access rights from the original license. If an equivalent role doesn't exist, a copy is created in the destination license with the following format: <role name (source license name)>.

License administrators from the source license will receive a role with all available project rights if they are not a license administrator in the destination license. License administrators in the destination license will receive the license administrator project role. If the project owner is not migrated, the person performing the migration will be assigned the project owner role. For more information on project roles see Managing project roles.

Migrating a project to a different region

Revizto license regions are not connected, therefore projects cannot be migrated directly between different license regions. However, you can transfer a project to a license in another region by saving it locally and syncing it to the destination license region. This will create your uploaded project as a "New project" on the destination license region.

As a new project the following apply:

• Prior Revizto Workspace tools and data are disconnected and will need to be recreated. These include reports, dashboards, workflows, project tags, project roles, user notifications, and authentication methods. 
• Version history cannot be transferred between license regions, so Revizto Workspace activity, versions, and project log will start fresh when synced. 
• Issue IDs will change, as issues are recreated when uploaded to a different Revizto license region.

This method will not migrate users or their individual tool settings. To migrate users from one license region to another see Importing and exporting users. To migrate tool settings see Importing and exporting tool settings.

To manually migrate a Revizto project:

1. From the Revizto application, open the project.
2. Sync all current data from the cloud by clicking Sync on the primary tool bar. Sync will be grayed out when your project is up to date. 
3. Navigate to the Project menu and click Save as to save a local copy of your project.
   • Give the project a clear name that indicates it is being migrated when saving your local copy. This is helpful when uploading the project to a different Revizto license region.
   • When finished naming the project copy, click Done. 
4. Close the project from the Project menu, and sign out by clicking <your account name> then clicking Sign Out.
5. Click Sign In to sign into your account again, this time selecting the region of the destination license.
6. Open the project you are migrating. The project will be labeled "Local."
7. Click Sync, then Upload to save the project to the cloud.