Migrate your organization’s Webex data to the European Union data center in Control Hub
The migration feature in Control Hub can help you migrate your Webex common application data to a data center within the EU if the data resides in a US data center, and your organization is based in the EU and your organization uses Webex common application data from a US data center. After enabling this feature, you will be able to automate data migration to the EU, including user profiles and analytics data.
A limited number of customers are currently testing this feature. This feature is expected to go live within two to three months for all customers who are eligible.
Prerequisites
The following services cannot be available at the EU data center in order for your organization to migrate:
-
Broadworks Webex
-
In the past, Spark Call was used before Webex Calling was introduced.
-
Webex Instant Connect can be used with Virtual Care and Epic.
-
Call Center for Webex
What data gets migrated
The migration involves migrating all Webex identity data to the EU data center, including name, email, and group memberships. Data from Webex Messaging, Devices, and Calling will also be migrated.
There will be no migration of CCUC analytics at the moment.
Impacts to your Webex services
During the migration
Once migration begins,
-
Depending on the size of your organization, it may take less than one hour to migrate your data in a Webex environment with fewer than 10,000 users, or upwards of eight hours in a Webex environment with more than 100,000 users. In order for your data migration to be successful, please pick a date when you are available to accommodate the downtime that will be required.
-
If you wish to manage a Control Hub-managed site, you will not be able to access Control Hub, or any messaging, calling, Webex contact center, or meeting features that are available on Managed Sites managed by Control Hub.
-
Your organization will be automatically disabled if single sign-on (SSO) has been set up in your organization.
-
A Webex Edge for Devices-registered on-premises device and a cloud-registered device will not be able to join a meeting or make a call using Webex Edge for Devices.
-
In certain cases, bulk deletes or changes made to workspaces or devices before a migration may not succeed if the migration continues to interrupt the actions.
-
Once the migration has started, we will be sending out an email notification to all full administrators at the company, and we will be updating them every two hours on the progress of the migration.
What to do after the migration is complete
-
It would be best to reconfigure SSO if you have setup SSO in your organization before doing the migration. Here are the steps to reconfigure SSO:
-
The metadata should be exported to the IdP.
-
Metadata should be imported into SP in order to be used.
-
-
If you created activation codes for devices in advance of the migration, but did not use them prior to the migration, then you will need to generate them again.
-
As part of the migration process, your organization will be revoked the access tokens for all bots that were created by your organization. There will be an HTTP 401 error on the server if you attempt to access the bots because the token is invalid or has expired, so you will get an HTTP 401 error. Your bots’ access tokens must be regenerated and updated to use the new code in order to use the new token with all of your bots. To do this, go to https://developer.webex.com/my-apps, click on Regenerate Access Tokens for each bot you have created.
-
Your users may need to reconfigure some of these settings if a local setting has been configured in the desktop or mobile app client of your Webex App. There will be a reset of the following settings after the migration has been completed:
-
Calling
-
Preferences for audio and video
-
Accessibility
-
Preferences for messaging
-
Devices
There will be no changes to other local settings such as general settings, notification preferences, appearance (for instance dark mode), and privacy settings after the migration has taken place (no changes will be made).
-
Schedule your migration date
In the case of a small organization with less than 10,000 users, migration may take around one hour to complete, and in the case of a large organization with around 100,000 users, it can take up to eight hours. Schedule your migration on a day when your organization will experience the least amount of downtime as possible.
- Go to Customers > Services > Updates & Migration from the customer’s account information in https://admin.webex.com.
- Under the Common application data section, click on View details to see more information about the data.
- You can schedule the migration by clicking on Schedule migration.
- Once you have selected a date for the migration to begin, click on the Schedule button.
Your migration will take place on the scheduled date at 9:00PM CET and will begin at that time. The migration should be rescheduled if possible or cancelled if possible, at least one day before the migration begins if you would like to make any changes to the migration date.
Reschedule your migration date
You should always make any changes to the migration date one day before the original date of the migration if you decide to reschedule it.
- On http://admin.webex.com, you can access Services > Updates & Migration by going to the customer view of the site.
- In the section called Common application data, click View details.
- If you wish to reschedule, select that option.
- Click on the Reschedule button after you have selected a date.
Cancel your scheduled migration date
You should make any changes one day before the original scheduled date in case you decide to cancel your migration. Otherwise, we will be unable to keep your migration.
- Go to Customers > Services > Updates & Migration from the customer’s account information in https://admin.webex.com.
- Under the Common application data section, click on View details to see more information about the data.
- You can cancel the migration by selecting Cancel migration.