Who is this article for?

Administrators and implementation leads who need details on downtime, schedule, prerequisites, and single sign-on requirements for migration.

No elevated permissions are required.

This article explains the downtime, timing, prerequisites, and single sign-on considerations involved in the migration process.

1. Expected downtime

The expected downtime during the migration is approximately 2 hours. This window is planned to minimise disruption and ensure a smooth transition for users.

2. Migration timing

The migration is carried out outside of normal business hours to minimise disruption. The planned start times are:

• UK: 7:00 am GMT
• US: 2:00 am EST

This approach helps ensure that business operations can continue with minimal impact.

3. Prerequisites

All users must sign in using their email address. The review platform will also be updated to use email‑based login.

Before the migration can begin, the following must be in place:

• All users must have a valid email address.
• The administrator account must also have a valid email address.

Without a valid email address, the welcome email cannot be sent, and users and administrators will not be able to log in.

Once the migration is complete, existing usernames will be replaced with email addresses. All users will receive a Welcome email with instructions on how to sign in and set up their password.

4. Single sign-on requirements

If you use an identity provider for single sign-on, your data will be migrated as part of the process. However, you will need to update your Redirect URL and Entity ID. These values will be provided during the migration planning stage.

Your implementation engineer will coordinate the timing of these changes with you. If the Redirect URL and Entity ID are not updated correctly, users will not be able to access the platform after signing in.

5. Using the platform with single sign-on

The platform supports single sign-on as long as users authenticate using email addresses.

During the migration, the existing review platform username will be replaced with the single sign-on email address. This ensures that user accounts remain synchronised across both systems during sign-in.

6. Mixed username formats

Migration is still possible if only a small number of users are using non‑email usernames.

Before migration, those users will need to be updated to use email addresses as their usernames. Alternatively, those specific users can be configured to sign in using password‑based authentication for both systems.