Prerequisites

In order for your organization to be eligible to migrate across regions, your organization must not have any of the following services:

• Webex for Broadworks
• Spark Call (before the upgrade to Webex Calling)

What data gets migrated

All data associated with Webex Identity, such as name, email address, and user groups, are migrated to the destination region. Analytics data for Webex Calling, Messaging, and Devices will also be migrated after the Webex Identity migration is completed.

Impacts to your Webex services

During the migration

Once the migration begins:

• Data migration may take less than one hour to complete for Webex organizations with less than 10,000 users, and may take up to eight hours for organizations with around 100,000 users. Please schedule your data migration on a date when you can accommodate for the required downtime.

  Make sure that all batch jobs will be completed before the scheduled migration starts.

• You won't have access to Control Hub, and users won't be able to access any messaging, calling, Webex contact center, and meeting services for Control Hub-managed sites.
• If your organization has set up single sign-on (SSO), it'll be automatically disabled.
• On-premises devices registered with Webex Edge for Devices and cloud-registered devices won't be able to join meetings or make calls.
• Workspace or device bulk delete or change actions started right before the migration may be interrupted by the migration and may not complete successfully.
• We'll send out email reminders to administrators of the organization, and then status updates every two hours while the update's in progress.

What happens after the migration and required actions from you

• If your organization has set up SSO, then after the migration users can't sign in until SSO is reconfigured as follows:
  • Download SP metadata.
  • Import this metadata to the IdP.
  • Activate SSO by going to Organization settings > Authentication and toggling Single sign-on to on.
• Device activation codes that were generated but not used before the migration will have to be generated again.
• Devices may take up to 24 hours to be fully operational after the migration. You can manually reboot devices to speed up this process.
• If your organization uses Okta integration to synchronize Okta users into Control Hub, you need to regenerate the bearer access token as specified in steps 3 and 4 under Configure Okta for user synchronization in this article.
• Analytics data won't appear immediately after the migration. Analytics data migration will continue in the background and lasts up to two to three days. There are no actions required from you to bring back analytics data. It will reappear automatically. The impact is that you won't see analytics data in Control Hub until two or three days after the completion of migration.
• The migration will reset the local databases of users if they're using UCM Calling. As a result, call histories will be reset and the history of previous calls will no longer be available.

Impacts to end users

• At the start of the migration, users are signed out of Webex App. Users must sign back in again during or after the migration.
• If your users configured local settings in their desktop and mobile clients of the Webex App, then they need to reconfigure some of these settings. The following settings will be reset after the migration:
  • Calling
  • Audio and video preferences
  • Accessibility
  • Messaging preferences
  • Devices

  Other local settings such as general settings, notification preferences, appearance (e.g. dark mode), and privacy settings will be preserved (no change) after the migration.

Impacts to integrations

There are many types of integrations possible with Webex, and they're usually authorized by users. User tokens to integrations are revoked once the common application data migration starts. In order for the integrations to continue working, users with the right privileges will need to reauthorize their access to those integrations.

Other integrations that aren't authorized by users will need to be reauthorized by either administrators or compliance officers. For example, the Events API integrations can only be reauthorized by compliance officers.

• Embedded apps—Access and refresh tokens for users aren't migrated, so users must authorize embedded apps again after the common application data migration has finished. This is usually done by signing in to the embedded app.
• Integrations—Access and refresh tokens for users aren't migrated, so users must authorize integrations again after the common application data migration has finished.
  • Some integrations are configured in Control Hub and may be deactivated during the migration. One example is the ThousandEyes integration, which is turned off during the migration and needs to be reconfigured. The apps page in Control Hub is also a good reference to see what integrations were turned off.
  • Integrations with Data Loss Prevention solutions need to be reauthorized by compliance officers.
  • Webex Contact Center task integrations and connectors must be reauthorized.
  • If your users have built any Webex API integrations, the access and refresh tokens associated with those integrations will no longer work.
• Service Apps need to be reauthorized. The client needs to ask for a new access and refresh token.
• If your organization has created bots, the access token for each bot will be revoked as part of the migration. If you try to access the bots, you'll get an HTTP 401 error since the access token will be invalid or expired. You must regenerate the access token for all of your bots, and update your bot configurations to use the new access token. This can be done by accessing https://developer.webex.com/my-apps, selecting each bot you've created, and then clicking on Regenerate Access Token.

If your users are having trouble signing in to Cisco.com with a linked Webex account after the migration, you can let them know that they can request to unlink their accounts from Webex to fix the problem.