Customers with Jabber with Unified CM IM and Presence, Jabber Phone Only mode, or our Webex apps will not experience any change.


You can click the image below to open it in full-sized view.

Create a Control Hub org if you don't currently have one and then complete the initial setup. Control Hub is the administrative interface where you manage users and services in your organization. We highly encourage you to enable single sign-on (SSO) for a consistent user sign-in experience.

Before you begin

You may already have the entitlements for Webex. If you do, then you can get ready and start to deploy.​ If you don’t, we’ll help you move to the right licensing. Work with your partner or Cisco contact for further assistance.

1

Add, verify, and claim domains.

You can add, verify, and claim your domains in Cisco Webex Control Hub to use features that require proof of domain ownership, ensure the security and integrity of your organization, and to help with your user management.

2

Enable analytics in your environment:

Cisco Webex Cloud-Connected UC is a set of services in the Cisco Webex cloud that provides enhanced business and operational insights with the aim of improving administrative workflow productivity. It allows customers to leverage the benefits of the Webex cloud, while keeping your critical calling workload on your premises. Customers log in to Webex Control Hub to get a single global view where you can manage the entire on-premises Unified CM network from a single operations control panel that supports your Cisco cloud or hybrid services.

Jabber telemetry is also recommended and is enabled by default. This data can provide insight into your Jabber deployment and usage as your users adopt Webex. No personally identifiable information is collected. Use the linked document to surface this usage data in Webex Control Hub.

3

Enable single sign-on (SSO) across all components for a consistent user experience:

If you have your own identity provider (IdP) in your organization, you can integrate the SAML IdP with your WebEx Messenger, Unified CM, and Control Hub environments for SSO. SSO lets your users use a single, common set of credentials for Webex Meetings, Webex, and other applications in your organization.

4

Set Up Automatic License Assignment Templates in Cisco Webex Control Hub

You can set up a default license template in Control Hub that automatically assigns licenses to new users.

At any point after users are created, you can also use these methods to assign services:

5

(Optional) Synchronize users from an existing supported directory:

You can synchronize users from an existing directory in to your Control Hub organization using the integration steps for Cisco Directory Connector or a SCIM API option. These integrations keep your user list in sync so you don't have to recreate user accounts. Whenever a user is created, updated, or removed in the directory that you're synchronizing, Control Hub reflects the update.

6

Deploy the Hybrid Calendar Service.

With Hybrid Calendar Service, you can connect your on-premises Microsoft Exchange, Office 365 or Google's G Suite Calendar (Google Calendar) environment to Cisco Webex. This integration makes it easier to schedule and join meetings, especially when mobile; no plugins are required.

Users can add Cisco Webex Room and Desk devices and Webex Boards to a meeting to make conferencing resources available. If the device is enabled for the Hybrid Calendar Service, the green Join button appears on the device. (The Join button is also known as One Button to Push, and is also available to devices that are registered to Cisco Unified Communications Manager, and managed by Cisco TelePresence Management Suite.)

We recommend a flash cutover to Control Hub so that all users are updated at the same time. Set policies to allow for things like XMPP federation, retention, and compliance.

If you're migrating users over time and want to use messaging interop during that period, you must submit a request for your existing org to become "CI Enabled" so that all the Jabber users are synchronized to the Webex platform. See the Messaging Interop documentation for more information about this process.

1

Set the retention policy for your organization.

Webex uses persistent messaging. If less message retention is important to your organization, set the retention period for data in Webex.

You can request a retention period of 24 hours by contacting your Customer Success Manager (CSM) or partner for assistance.

2

Configure access to Enterprise Content Management (ECM) in Control Hub.

Configure access to your enterprise content management platform in Control Hub. Provide users with permission to use your enterprise content management platform in Cisco Webex. Users can only use an approved enterprise management platform to upload and manage files and content in Webex.

3

Ensure regulatory compliance of content.

(This feature requires Pro Pack.) As a compliance officer, you can use Control Hub to search through any conversation in the Webex app. You can look for a specific person in your company, find content they've shared, or search through a specific space and then generate a report of your findings. This way, you can make sure people are complying with both outside regulatory requirements and your internal policies.

4

Deploy Hybrid Data Security.

From day one, data security has been the primary focus in designing Cisco Webex. The cornerstone of this security is end-to-end content encryption, enabled by Webex clients interacting with the Key Management Service (KMS). The KMS is responsible for creating and managing the cryptographic keys that clients use to dynamically encrypt and decrypt messages and files.

By default, all Webex customers get end-to-end encryption with dynamic keys stored in the cloud KMS, in Cisco's security realm. Hybrid Data Security moves the KMS and other security-related functions to your enterprise data center, so nobody but you holds the keys to your encrypted content.

5

Enable XMPP Federation.

You can choose if your users can communicate in Webex with people using messaging apps that support XMPP.

For migration-specific information, see the XMPP Federation slide deck.


If you are moving your users in groups over a period of time and intend to use Webex as the single collaboration client, you can enable interop so your Webex users can communicate with the groups still on Jabber or request assistance from your Customer Success Manager (CSM) or partner. We strongly recommend a full migration to Webex; only do this step if you're doing a gradual cutover to Webex.

To enable Common Identity (CI) linking which allows for a phased update process across your organization, contact your Customer Success Manager (CSM) or partner for assistance.


If you deploy interop, you must avoid directory synchronization because it introduces two sources of user management—one in your existing org, one in Control Hub.

If you deploy interop, XMPP federation is maintained in the existing org, not in Control Hub.

If you cut over to Webex and a Control Hub org, we don't have the option to add federated domains in Control Hub. Contact your Customer Success Manager (CSM) or partner for assistance.

Follow these steps if you're an existing Site Admin customer to align your meeting environment with Control Hub and the Webex experience.

1

Follow the steps in Link Webex Sites to Control Hub.

If you have existing Webex sites you can use the Cisco Webex linking process to get access to advanced analytics for those sites, and also link your Webex Meetings users to Control Hub.

2

Enable the full-featured Webex Meetings experience.

This step gives your team of users the same meetings experience that they're already used to.

Request the full meetings experience by contacting your Customer Success Manager (CSM) or partner for assistance.

Use the steps to set up Calling in Webex (Unified CM); this solution uses your existing Unified CM deployment that you already have in place. Refer to the Transitioning from Jabber Unified CM Calling to Webex Unified CM Calling and Webex UCM Calling Configuration guides for more information.

1

Validate Unified CM Calling configuration.

The Calling in Webex (Unified CM) solution lets you register Webex directly to your Cisco Unified Communications Manager call control environment (on-premises enterprise, Business Edition 6000/7000, or as delivered through an HCS partner solution).

This solution enhances the calling experience for end users, allowing them to directly make calls in Webex through your Unified CM environment, use midcall features, and control their Unified CM registered desk phone from Webex.

2

Validate Unified CM service discovery.

Service discovery enables clients to automatically detect and locate services on your enterprise (internal) and MRA (external) network. This configuration may already be in place, but check the deployment guide in this step and your environment to verify.

3

Update Unified CM configuration file.

Webex leverages the same configuration file as Jabber You can use this embedded Unified CM to configure various client functionality, such as specific calling features and the Jabber to Webex migration tool.

See the Policy Parameters documentation for a list of supported parameters for Webex.


Webex already includes most knowledge worker calling features. However, in some cases, a small subset of your users may need more advanced calling features that aren't yet in Webex, such as contact center features and multiline. You can use Webex with a cross-launch to Jabber as an interim solution. This option opens Jabber when a user makes a call from Webex; incoming calls also ring in Jabber directly. For more information, see the Webex with Jabber Cross Launch documentation at https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/APPLICATION_CALLING-WebexTeams_with_Jabber_Cross_Launch.pdf.

Deploy the Webex app and customize the deployment, including update frequency, communication to your users, and migrating user data from Jabber to Webex. Then, decommission the previous messaging organization when ready.

1

Run a trial deployment.

We recommend a trial of Webex with select users before you roll it out to the entire organization.

2

Deploy the Webex app:

As an administrator, you can install Webex using the MSI file on Windows or the DMG file on Mac. You can include command line parameters with the MSI file on Windows to improve user experience. Webex periodically checks for newer versions to automatically upgrade the app. These steps only work for the desktop versions of Webex. Users can also self-serve and install Webex themselves. They can download the desktop or mobile versions from https://www.webex.com/downloads.html.

You can control the product updates for Webex that your users are updated to and when the app is updated. You can use a deferral period to preview the app before your users are updated.

3

Help users migrate their data from Jabber to Webex:

The migration tool is built into Cisco Jabber and provides a way to migrate contacts and other common user preferences from Jabber to Webex. The data is encrypted. Now that you've deployed Webex to your users, you can set them up for this migration. You just need to configure some settings before users see this option pop up automatically in Jabber. They can use the user guide to help them walk through the migration.

4

Decommission Messenger org.

When you're all up and running with your Control Hub organization, you've notified your users of the change, and you're ready, contact your Customer Success Manager (CSM) or partner to have your old Messenger org decommissioned.

Need some help? We've got you

Reach out to your Customer Success Manager (CSM) or partner for assistance.

Get everything you need to implement the Messenger Update Program.