Pregled

If your organization is based in one region but your Webex data resides in a different region, you may be eligible to migrate your Webex data to your own region through the migration feature in Control Hub.

This feature is available eligible to customers in Europe, Canada, and Middle East who want to migrate their Webex common application data to their regions.

Analytics data migration doesn't apply to organizations migrating between a US or EU data center to a Canadian or United Arab Emirates (UAE) data center.

Koji podaci se migriraju

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.

Exceptions to what data gets migrated are:

  • CCUC analytics data won't be migrated at this time. CCUC analytics data will be migrated as part of the messaging data migration.
  • Analytics data migration doesn't apply to organizations migrating between a US or EU data center to a Canadian or United Arab Emirates (UAE) data center.
  • CCUC Directory Sync configurations will not be migrated. You need to provision the CCUC Directory Sync in the destination region post migration.

Uticaji na Webex usluge

Tokom migracije

Kada migracija počne:

  • Data migration may take less than 1 hour to complete for Webex organizations with less than 10,000 users, and may take up to 8 hours for organizations with around 100,000 users. Zakažite migraciju podataka na datum kada možete da se smestite za potrebno vreme dospeća.

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

  • Nećete imati pristup Kontrolnom čvorištu i korisnici neće moći da pristupe porukama, pozivima, Webex kontakt centru i uslugama sastanaka za sajtove kojima upravlja Kontrolni čvorište.
  • Lokalne uređaje registrovane pomoću Webex Edge uređaja i uređaja registrovanih u oblaku neće moći da se pridruže sastancima ili da telefoniraju.
  • Radni prostor ili masovno brisanje ili promena radnji uređaja započeti neposredno pre nego što je migracija prekinuta i možda neće biti uspešno dovršena.
  • We'll send out email reminders to administrators of the organization, and then status updates periodically while the migration is in process.

What happens after the migration and required actions from you

  • If your organization has set up SSO, the SSO is automatically disabled during migration. 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 2 to 3 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 2 or 3 days after the completion of migration.

    Analytics data doesn't migrate over when migrating from a US or EU data center to a Canadian or United Arab Emirates data center.

  • 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.
  • Confirm that Hybrid services are functioning correctly. Some Hybrid connectors can take a few minutes to come back online after the migration is complete.
  • Sign in to Webex App and make sure it's working as configured.

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.
  • Ako su vaši korisnici konfigurisali lokalne postavke na radnoj površini i mobilne klijente Webex aplikacije, potrebno je da ponovo konfigurišu neke od ovih postavki. Nakon migracije biće vraćene na početne vrednosti sledeće postavke:
    • Pozivanje
    • Željene postavke zvuka i video zapisa
    • Pristupačnost
    • Željene postavke razmene poruka
    • Uređaji

    Druge lokalne postavke kao što su opšte postavke, željene opcije obaveštenja, izgled (npr. tamni režim) i postavke privatnosti biće očuvane (bez promene) nakon migracije.

  • Drafts created before migration begins are lost during the first stage of messaging data migration.
  • Users can't send draft messages in a space after that space has been migrated.

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.

Failure to reauthorize integrations will result in the integrations no longer working.

  • 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.
  • Ako je vaša organizacija stvorila botove, pristupni simbol za svakog bota će biti opozvan kao deo migracije. Ako pokušate da pristupite botovima, dobićete HTTP 401 grešku pošto će oznaka za pristup biti nevažeća ili istekla. Morate ponovo generisati oznaku za pristup za sve svoje botove, i ažurirati konfiguracije botova da biste koristili novi pristupni simbol. To se može uraditi tako što ćete pristupiti https://developer.webex.com/my-apps, izabrati svakog bota kojeg ste kreirali, a zatim kliknuti na dugme "Ponovo generiši oznaku pristupa".

Schedule common application data migration

Data migration may take around one hour to complete if your organization has less than 10,000 users, and up to eight hours if your organization has around 100,000 users. Make sure to schedule the migration during a date that'll have the least downtime for your organization.

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

1

Prijavite se u kontrolno čvorište.

2

Navigate to Updates & Migration in the left menu bar.

3

Choose Regional data migration and click View.

4

Kliknite na dugme Prikaži detalje u odeljku Uobičajeni podaci aplikacije.

5

Kliknite na dugme Zakaži migraciju.

6

Select a date and time to start the migration, and then click Schedule.

If you decide that you want to reschedule the data migration or cancel the migration, we suggest that you make any changes one day before the scheduled date.

Preraspoređen datum migracije

If you decide to reschedule your migration, we suggest that you make any changes one day before the scheduled date.

You cannot reschedule scheduled migrations within 24 hours of the scheduled start time. The reschedule button won't be available in Control Hub at that time.

1

Sign in to Control Hub and go to Services > Updates & Migration.

2

Select View in the Migrate to the regional data center card.

3

Kliknite na dugme Prikaži detalje u odeljku Uobičajeni podaci aplikacije.

4

Izaberite stavku Prerasporedi.

5

Select a date and time, and then click Reschedule.

Otkazivanje planiranog datuma migracije

If you decide to cancel your migration, we suggest that you make any changes one day before the scheduled date.

You cannot cancel scheduled migrations within 24 hours of the scheduled start time. The cancel button won't be available in Control Hub at that time.

1

Sign in to Control Hub and go to Services > Updates & Migration.

2

Select View in the Migrate to the regional data center card.

3

Kliknite na dugme Prikaži detalje u odeljku Uobičajeni podaci aplikacije.

4

Izaberite Otkaži migraciju.

New Webex data center in Saudi Arabia and migration plan for your Webex Meetings site

Cisco je posvećen zaštiti i privatnosti podataka naših klijenata, imajući u vidu nepokolebljivu potrebu za dodatnom fleksibilnošću i mogućnošću hostovanja podataka u vašem regionu.

As of February 2025, the new Saudi Arabia data center is fully operational and offer the complete Webex Meetings and Webinars stack. This means that you can store all of your Webex Meetings and Webinars data—including recordings and transcripts—within Saudi Arabia. To support our commitment to transparency, we’re also launching a new user interface in Control Hub that clearly displays your organization’s data location.

Eligibility for Saudi Arabia migration

All current customers in Saudi Arabia and the Middle East who use the Webex Suite Meetings platform are eligible to migrate their Webex Meetings sites to the Saudi Arabia data center during the announced migration plan.

If you became a new customer after the end of February 2025 and set up your Webex site in one of the following time zones, your Webex Meetings data will be automatically provisioned in the Saudi Arabia data center:

  • (GMT +02:00) Tripoli

  • (GMT +02:00) Cairo

  • (GMT +02:00) Juba

  • (GMT +02:00) Khartoum

  • (GMT +03:00) Riyadh

  • (GMT +03:00) Istanbul

  • (GMT +03:00) Baghdad

  • (GMT +03:00) Amman

  • (GMT +03:00) Beirut

  • (GMT +03:00) Hebron

  • (GMT +04:00) Abu Dhabi

  • (GMT +04:30) Kabul

Our plan on scheduling the migration

We'll send you an email inviting you to opt in through Control Hub. Once we receive your opt-in request, we'll schedule the migration of your Webex Meetings site to the Saudi Arabia data center and communicate your migration dates. Migrations are planned for Friday and Saturday during non-business (weekend) hours to minimize disruption and ensure no extra effort is needed from you.

Migrate Meetings site to Saudi Arabia data center

1

Prijavite se u kontrolno čvorište.

2

Navigate to Updates & Migrations in the left menu bar.

3

Select Regional data migration and click View.

4

Select View Details in the Meetings section.

5

Toggle the switch to on next to the Webex Meetings site that you want to migrate in the Opt in column.

Uticaji na Webex usluge tokom migracije

Webex sites that have opted in for migration are scheduled during the normal Webex site maintenance windows. Although migration won't cause any major disruptions, here are the impacts to Webex services that your organization might run into.

Webex Meetings

  • Hosts and participants may experience intermittent service unavailability when attempting to host or join meetings during the migration window. If this occurs, affected users should rejoin the meeting.

  • Podaci za jednostruke i ponovne sastanke koji su trebali da se odrze pre 13 meseci, ali nikada nisu imali aktivnosti na sastanku nece biti dostupni posle migracije. To neće uticati na postojeće zakazane sastanke.

  • Učesnici mogu prekinuti vezu sa sastancima koji se održavaju tokom prozora za održavanje lokacije i neće moći ponovo da se pridruže ukoliko domaćin ponovo ne pokrene sastanak.

  • Podaci za nedavne lične sobe će se uspostaviti nakon migracije lokacije na Webex lokaciji i u Webex Meetings aplikaciji za radnu površinu. Korisnici mogu da vide samo nedavne lične sobe kojima su se pridružili tek nakon migracije lokacije.

  • To neće uticati na postojeće zakazane sastanke.

  • Meeting summary and Transcript in Meeting recap will be gradually available in the next 24 hours after the migration cutover.

  • The meeting report will be gradually available in the next 24 hours after migration cutover.

Webex Edge Audio

Ako vaša organizacija koristi Webex Edge Audio, konfiguracije će i dalje biti iste kada se migracija završi. Međutim, da bi se uverili da je odabran najpriotimalniji medijski put, skripta Lua mora da se ažurira u CUCM-u nakon završetka migracije. Da biste to uradili:

  1. Sign in to Control Hub and go toMeeting > Selected the migated site > Configure Site > Audio Settings..

  2. Under Edge Audio Customer Global Call-in Numbers, click Generate Lua Script.

  3. Export the script in a .lua format.

  4. Go to the Edge Audio help article and follow the steps in the Create SIP Normalization Script from the Webex LUA Script section.

  5. U Cisco Objedinjenoj CM administraciji idite na Uređaj > Trunk i izaberite SIP prtljažnik kreiran za Webex Edge Audio.

  6. Update the existing SIP Normalization Script to the new one that you created in step 3.

  7. Sačuvajte i uspostavite početne vrednosti SIP trunke.

Webex Audio

Call-in numbers may be changed. The call-in number of the email that has been sent won't changed. Please advise your users to resend invitations if they need those numbers updated.

Webex Training Center, Support Center, Event Center

Training Center, Support Center, and Event Center aren’t supported by the Saudi Arabia data center and won't be available after migration.

Često postavljana pitanja

Q. Can I opt out of the Webex Meetings site migration schedule?

Odgovor: By default, you are opted out of Webex Meetings site migration to the Saudi Arabia data center. If you want to opt in to migrate a Webex Meetings site, follow the steps in the Migrate Meetings Site to Saudi Arabia Data Center section.

Q. What is the deadline to opt in or opt out of the Webex Meetings site migration to the Saudi Arabia data center?

Odgovor: You have until August 31, 2025 to either opt in or opt out of the Webex Meetings site migration to the Saudi Arabia data center.

Q. If I don’t opt-in during the open windows, can I migrate my meeting sites later?

Odgovor: To ensure a smooth migration experience, we encourage you to opt-in during the current migration window. If you're unable to opt-in by August 31, 2025, please reach out to Cisco Technical Support or your Customer Success Manager (CSM) to discuss a possible exception for migrating you at a future time.

Q. Will my Webex Meetings recordings and transcripts be migrated?

A. Da. All Webex Meetings recordings and transcripts will be migrated to the Saudi Arabia data center.

Q. Are there any limitations of Webex Meetings functionality not available in Saudi Arabia once migrated?

Odgovor: The following limitations apply once you've migrated to the Saudi Arabia data center:

  • Webex Webinars support up to 1,000 participants. For events with more than 1,000 participants, use Webinars in webcast view.

  • Training Center, Support Center, and Event Center aren’t supported by the Saudi Arabia data center and won't be available after migration.

Q. Who can I contact if I need additional information?

Odgovor: Please contact Cisco Technical Support or your Customer Success Manager for any further information.