This article is intended for project owners and license administrators. It describes how to migrate projects between licenses issued in different regions. 

• Prerequisites
• Principles and limitations
• Migrating projects to a different region
• FAQ

See also:

• Migrating projects to a license issued in the same region

Prerequisites

We recommend that a single person who has enough rights in both licenses performs the migration. You can migrate a project to a license issued in another region if the following conditions are met:

• You are the project owner or a license administrator in the source license.
• You are a content creator or a license administrator in the destination license.
• A project slot is available in the destination license.

Principles and limitations

Project migration to a different region has the following limitations:

• Issue IDs might change.
• Shared issue filters lose their shared status.
• Only the latest versions of sheets and scenes are migrated. The project version history is not migrated.
• In authoring tools (Revit, Navisworks, and so on), all export settings and export scheduler settings are not migrated.
• Integrations (Autodesk Construction Cloud, Asite, Box, Procore, and Microsoft SharePoint) are not migrated.
• Clash tests are not migrated. You can migrate them manually by exporting them to a file.
• Reports and dashboards are not migrated.
• Project tags are not migrated.
• Project log in Revizto Workspace is not migrated.
• Project members that had unsynced project changes before the migration cannot sync them after the migration.
• User notification settings are not migrated.
• Project members with "Pending" and "Pending approval" statuses are not migrated.

If you migrate a project from a Revizto+ license to a standard license, the following rules apply:

• Clash automation becomes unavailable. To restore access to clash automation, upgrade your license to Revizto+.
• Issues generated by clash tests stay available.
• Existing location tags stay intact. Filtering issues by location tags is allowed. New issues won’t have location tags.
• Zones stay intact. Zone objects stay hidden. You can unhide the objects by excluding them from the zones search set.

User account settings are always migrated.

Migrating projects to a different region

Project migration consists of the following steps:

• Before migration: checklist
• Migrating a project

Before migration: checklist

Before you migrate a project, do the following:

1. Check the prerequisites.

2. If there are project members with "Pending" status, ask them to register at Revizto Workspace by following the registration link that was emailed to them.

3. If there are project members with "Pending approval" status, ask a license administrator to approve them. Wait until the approved project members register at Revizo Workspace.

4. If your project includes license members that are not eligible for the Guest role in the destination license, ensure that the destination license has free slots for all of them.

5. If you use SSO authentication, configure the authentication methods in the destination license to minimize manual correction of user authentication methods. For more information, see Adding authentication methods.

6. Schedule the migration, inform the project members about the downtime, and ask them to close the project before the migration starts.

Migrating a project

To migrate a project:

1. At ws.revizto.com, sign in to the source region and export the license members to a spreadsheet.

2. At ws.revizto.com, sign in to the destination region and import the license members from the spreadsheet.

   When you import license members from a spreadsheet, you specify a single role that is granted to all of them. If the destination license has several authentication methods, you also specify an authentication method for all of them.

   We recommend that you split the spreadsheet into several parts, one for each combination of a role and authentication method. This helps you to avoid manual correction of license roles and authentication methods.

3. If any of the imported license members have "Suspended" status, correct this. For more information, see Recovering suspended license members.

4. If your project includes clash tests, in the Revizto application, sign in to the source region and export the clash tests to a file.

5. In the Revizto application, sign in to the source region and save a local project copy (Project > Save As).

6. In the Revizto application, sign in to the destination region, open the local project copy, and sync it.

7. If the source project has custom project roles, re-create them in the destination project.

8. Add people to the destination project and grant them the correct project roles.

9. Re-create the items and settings that were not migrated in the destination project. If you exported clash tests before migration, import them to the destination project.

10. Archive the source project.

11. Instruct the project members to sign in to the destination region and review their personal settings. Then they can continue their work in the new project.

FAQ

Q: The version history of the project and the versions history of its sheets are not migrated. Is there any way to view them after the migration?

A: You can view the version history of the project and the versions history of its sheets in the archived source project. We recommend that you ask the project owner to do it, as they can access the project without restoring it from an archive.

Q: How can I view the old Revizto Workspace project log after migrating the project to a license issued in a different region?

A: It is available in the source license. To view it, at ws.revizto.com, sign in to the source license, open the license log, and apply a filter by this project.