This article is intended for project owners and license administrators. It describes how to migrate projects between licenses issued in the same region. For details, see the following sections:

• Prerequisites
• Principles and limitations
• Migrating projects
• Troubleshooting

See also:

• Migrating projects to a license issued in a different region

Prerequisites

You can migrate a project to another license if the following conditions are met:

• You are the project owner in the source project 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

Revizto attempts to migrate a project with all its members, their statuses, roles, and authentication settings. However, there are some limitations.

For details, see the following sections:

• Project members
• License roles
• License member statuses
• Authentication settings
• Project roles
• Clash tests and clash issues
• Revizto zones and location tags
• Miscellaneous

Project members

Revizto migrates all project members, with the following exceptions:

• Project members with "Pending" status are not migrated.

• Project members with "Pending approval" status are not migrated.

• Project members that are neither full members of the destination license nor eligible for the Guest role in the destination license are migrated only if free user slots are available in the destination license.

• If the number of project members that require free user slots in the destination license exceeds the number of free slots, some of them are migrated to available slots. The rest are not migrated.

If a project member is not a member of the destination license, they are added to the license and the following rules apply:

• Company, department, and office location are not migrated.

• Domain username is migrated only if the project member is assigned an Active Directory authentication method when they are added to the destination license.

  To learn how Revizto assigns authentication methods to migrated project members, see Authentication settings. 

• Personal settings (such as first name, last name, two-factor authentication, and notification settings) are not changed because they are shared across all licenses.

License roles

If a project member is not a member of the destination license, they are added to the license with the following roles:

• If they are eligible for the Guest role in the destination license, they get that role. This does not require a free license slot.

• If they are not eligible for the "Guest" role in the destination license, they get the Collaborator role. This requires a free license slot. If there are no slots available, they are not migrated.

License member statuses

If a project member is not a member of the destination license, they are added to the license and Revizto attempts to assign an authentication method to them.

• If Revizto cannot assign an authentication method, the project member becomes suspended with the following reason: "This user is suspended because they have not been set an active authentication method."

• If Revizto can assign an authentication method, see the following table.

  Source license status	Destination license status
  Active or Suspended	Active Exception: if the new authentication method is Active Directory and the project member's domain username is blank, the project member becomes suspended with the following reason: "This user is suspended because they have not been set a domain username."
  Deactivated	N/A A deactivated license member cannot be a part of a project team. Therefore, they cannot be migrated.

If a project member is a deactivated member of the destination license, they are removed from the project.

Authentication settings

If a project member is not a member of the destination license, they are added to the license and Revizto attempts to assign an authentication method to them as follows:

1. If the destination license has a single authentication method, assign this method. Otherwise go to the next step.

2. If the project member’s email domain is associated with an authentication method in the destination license, assign this method. Otherwise go to the next step.

3. If the license has a default authentication method, assign this method. Otherwise go to the next step.

4. Leave the authentication method blank.

Project roles

When you migrate a project to another license, Revizto assigns each project member a role with the same access rights that they had in the source project. Revizto uses the following algorithm to map project roles between the source and destination licenses:

• If a source role and a destination role include the same set of rights, assign the destination role to the project members that had the source role. The destination role might have a different name.

• If a destination role with the same set of rights is not found, create a copy of the source role in the destination license and assign it to the project members that had the source role. The new role has the same name followed by the source license name in parentheses. For example, "MyRole (MyLicense)".

• If a project member is a license administrator in the destination license, they get the License administrator project role.

• If a project member is a license administrator in the source license but not a license administrator in the destination license, they get a role that includes all available project rights.

• If the project owner is not migrated because there is no free license slot, the person who performs the migration becomes the new project owner.

Clash tests and clash issues

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

• Clash tests become unavailable. To restore access to clash tests, upgrade your license to Revizto+.

• Issues generated by clash tests stay available.

Revizto zones and location tags

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

• Existing location tags stay intact. Filtering issues by location tags will be 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.

Miscellaneous

The following rules apply to project migration:

• Project tags are migrated.

• Project log records are not migrated.

• Project members that had unsynced project changes before the migration can sync them after the migration.

Migrating projects

Project migration consists of the following steps:

• Before migration: checklist
• Changing project license
• After migration: checklist

Before migration: checklist

Before you change the project license, 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.

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 settings. For details, see Authentication settings.

6. Inform the project members about a short downtime, and ask them to close the Revizto application before the migration starts. They do not have to sign out.

Changing project license

To change a project license:

1. Sign in to ws.revizto.com.

2. Ensure that the source license is selected.

   

3. Do one of the following:

   • If you are a project owner, go to Tools, select My Projects, and open the project.

     

   • If you are a license administrator, go to License Management Tools, select Project Directory, and open the project.

     

4. Click Migrate to another license to the right of the project license.

   Troubleshooting:

   • When I attempt to change the project license, the Migrate to another license button is unavailable.

5. Select a license and click Change.

   Troubleshooting:

   • When I attempt to change the project license, the destination license is not on the list.

After migration: checklist

After you change the project license, do the following:

1. Review the list of project members and ensure that all of them are migrated.

   If any of the project members are missing, there are no free license slots for them. Free the license slots, and then add the missing members to the project.

2. In the list of license members, apply a filter by project and do the following:

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

   • Review the authentication settings of the project members and correct them if necessary.

3. Review the names of project roles and correct them if necessary.

Troubleshooting

Q: When I attempt to change the project license, the Migrate to another license button is unavailable.

A: You do not have enough rights. You must be the project owner in the source project or a license administrator in the source license.

Q: When I attempt to change the project license, the destination license is not on the list.

A: You do not have enough rights. You must be a content creator or a license administrator in the destination license.

Q: How can I view the old project log after changing the project license?

A: It is available in the source license. To view it, open the license log and apply a filter by this project.