# Jabber to Webex App migration

Canonical: https://warmtransfer.net/knowledge/jabber-to-webex-app-migration

Last verified: 2026-09-24

Cisco Jabber to Webex App migration transitions users from Cisco Jabber software endpoints to the Webex App client[^33][^52]. Webex App is the only soft client supported by Webex Calling, whereas Cisco Unified Communications Manager (Unified CM) supports both Webex App and Cisco Jabber[^51][^50][^47].

## Soft client migration strategies

Cisco names Jabber to Webex App migration among its native migration utilities, alongside Migration Insights, devices and features migration from Unified CM, a user and contact synchronisation utility, Unified CM data conversion, and Enterprise-to-MPP phone firmware conversion[^52]. Before users are moved to Webex Calling, their Jabber clients must be transitioned to the Webex App[^45]. Cisco recommends moving users onto the Webex App while they are still registered to Unified CM calling, and only then cutting them over to Webex Calling[^53][^42].

Cisco outlines two distinct migration sequences:
- **Single-step migration**: Users change from Jabber to the Webex App at the same time as they move from Unified CM to Webex Calling, an approach Cisco describes as suited to customers with few users to migrate[^44].
- **Dual-step migration**: Recommended by Cisco for larger customers wishing to separate the soft-client change from the calling-service change[^23]. In the first step, the soft client changes from Jabber to the Webex App, registering directly to Unified CM call control, with users cut over to Webex Calling in a later step[^24][^4].

In the target Webex Calling architecture, the Webex App on Windows, Mac, Android, or iOS registers directly to the Webex Calling platform[^49]. However, Webex Calling Dedicated Instance supports both Jabber and the Webex App with the same user experience as on-premises Unified CM[^22].

## Workloads and client configuration

Depending on whether Jabber is deployed in IM-only, phone-only, or full UC mode, migrating to Webex Calling may require moving Messaging or Meetings workloads to the Webex App alongside calling[^34]. The Webex App can be deployed either in phone-only mode as a calling-only client or as the full Webex Suite[^41]. Webex App messaging is persistent, and organizations requiring shorter message retention should configure a retention period for Webex App data[^40].

When using Calling in Webex App (Unified CM), the client registers as a SIP device using the same softphone device types as Jabber: Cisco Unified Client Services Framework (CSF) on desktop, TCT or BOT on mobile, and TAB on tablets[^43]. The Webex web app (web.webex.com) does not permit users to call phone numbers under Calling in Webex App (Unified CM)[^48].

Control Hub calling-behavior settings include Calling in Webex (Unified CM), Open Cisco Jabber from Webex App, and calling through a third-party app[^3]. Users licensed for Webex Calling receive Webex App as their default calling client without requiring a calling-behavior setting[^3]. When configuring Calling in Webex (Unified CM), the organization's domain applies from the user's email domain by default, though administrators can instead assign a UC Manager profile[^1].

## Migration tools and administration

With Cloud-Connected UC, the Control Hub migration wizard can migrate Jabber users with Unified CM calling or Jabber messenger users to the Webex App[^15]. The migration wizard operates in batches; administrators may configure multiple tasks, but only 1 task can run at a time[^12]. The wizard's Choose Settings step provides two calling options: Calling in Webex (Unified CM)—configured by email domain or a UC Manager Profile—or Open Cisco Jabber from Webex app[^5]. If Cloud-Connected UC is not enabled, administrators must upload.csv files in bulk via the Manage Unified Communications User Data dialog[^6].

To use the Cloud-Connected UC migration wizard, administrators must satisfy several requirements:
- Full administrator privileges in Control Hub are required[^8].
- Unified CM must run version 11.5 or later[^14].
- Organizations with hybrid Calling must remove it for affected users prior to initiating migration[^13].
- Every directory user across the organization must be synchronized to the identity service[^9].

After enabling Deployment Insights, updated data may take about 8 to 9 hours to populate in migration tasks[^10]. Following migration, users on the Webex App cannot communicate with Jabber users who are not present in Common Identity[^11].

To transfer user data, a migration utility built directly into Cisco Jabber moves contacts and common preferences to the Webex App[^19]. The Jabber migration screen appears between 5 minutes and 3 hours after a user signs in to Jabber, or when the user starts it from the Help menu, and users can continue or skip[^18].

## Infrastructure and licensing requirements

Calling in Webex App (Unified CM) requires a minimum Unified CM version of 11.5(1) SU3 for desktop, with Cisco recommending version 12.5(1) SU3 or later[^46]. For off-premises connectivity using Mobile and Remote Access (MRA), Expressway X8.11.4 or later is required; push notifications require Expressway X12.6 or later, and MRA failover requires X14.0 or later[^28].

For server performance reasons, Cisco states that Visual Voicemail must not be used concurrently in both Jabber and the Webex App[^37]. Licensing requires that users with 3 or more apps or devices hold Cisco Unified Workspace Licensing (CUWL) perpetual licenses, or the organization must maintain an active Flex Calling subscription[^35].

## Product lifecycle and documentation

On January 15, 2026, Cisco announced the end of sale and end of life for Cisco Jabber for Windows, Mac, and VDI versions 12.8.x and 12.9.x[^25]. The migration path documented in that end-of-life notice instructs customers to upgrade to the latest Cisco Jabber release rather than moving to the Webex App[^27]. Additionally, Cisco Jabber documentation has been relocated from the Webex Help Center to cisco.com within the Cisco Jabber User Guide and Cisco Jabber Administration Guide[^32].

## See also

- See also [CUCM to Webex Calling migration](https://warmtransfer.net/knowledge/cucm-to-webex-calling).
- See also [Expressway and Mobile and Remote Access](https://warmtransfer.net/knowledge/cucm-expressway-mra).

## Applicability

Applies to: Cisco Webex Calling, Cisco Unified Communications Manager, Cisco Jabber, Cisco Webex App, Cisco Webex Calling Dedicated Instance, Cisco Webex Control Hub, Cisco Cloud-Connected UC, Cisco Webex App with Unified CM calling, Cisco Expressway, Cisco Webex App (web), and Cisco Jabber for Windows. Deployments: on-premises, hybrid, multi-tenant, and dedicated instance. Sources checked 2026-09-24. Calling in Webex App (Unified CM) requires at least Unified CM 11.5(1) SU3 for desktop clients, with Cisco recommending 12.5(1) SU3 or later[^46]. Cloud-Connected UC Jabber migration requires Unified CM 11.5 or later[^14]. Calling over MRA requires Expressway X8.11.4 or later, push notifications require X12.6 or later, and MRA failover requires X14.0 or later[^28]. The end-of-sale and end-of-life announcement applies specifically to Jabber for Windows, Mac, and VDI versions 12.8.x and 12.9.x[^25][^27].

## What remains uncertain

Specific migration timelines or automated data conversion tools for Jabber custom contact groups or local chat history are not covered by the sources below.

## Sources

[^1]: For Calling in Webex (Unified CM), the default is to apply the organization's domain from the user's email domain. Admins can instead choose a UC Manager profile. Source: [Set up calling behavior](https://help.webex.com/en-us/article/1lvb42/Set-up-calling-behavior), Set up calling behavior > Calling in Webex (Unified CM). Checked 2026-09-24.
[^2]: Calling behavior can be set for the whole organization, for a group through calling templates, or for an individual user. Source: [Set up calling behavior](https://help.webex.com/en-us/article/1lvb42/Set-up-calling-behavior), Set up calling behavior (organization, group and user level procedures). Checked 2026-09-24.
[^3]: Control Hub calling-behavior options include Calling in Webex (Unified CM), Open Cisco Jabber from Webex App, and calling through a third-party app. Users licensed for Webex Calling get the Webex App as their default calling app without any calling-behavior setting. Source: [Set up calling behavior](https://help.webex.com/en-us/article/1lvb42/Set-up-calling-behavior), Set up calling behavior (calling behavior options). Checked 2026-09-24.
[^4]: Calling in Webex App (Unified CM) registers the Webex App directly to the customer's Unified CM call control. Source: [Upgrade Jabber with IM and Presence to Webex App](https://help.webex.com/en-us/article/980p3k/Upgrade-Jabber-with-IM-and-Presence-to-Webex-App), Align Calling. Checked 2026-09-24.
[^5]: The wizard's Choose Settings step offers two calling options: Calling in Webex (Unified CM), set by email domain or a UC Manager Profile, or Open Cisco Jabber from Webex app. Source: [Migrate Jabber users with Cloud-Connected UC to Webex App](https://help.webex.com/en-US/article/nejw7ue/Migrate-Jabber-Users-with-Cloud-Connected-UC-to-Webex-app), Task flow > Choose Settings. Checked 2026-09-24.
[^6]: If Cloud-Connected UC is not enabled, the Get Started tile opens the Manage Unified Communications User Data dialog, where admins upload .csv files in bulk. Source: [Migrate Jabber users with Cloud-Connected UC to Webex App](https://help.webex.com/en-US/article/nejw7ue/Migrate-Jabber-Users-with-Cloud-Connected-UC-to-Webex-app), Prerequisite. Checked 2026-09-24.
[^7]: The Cloud-Connected UC Jabber migration requires onboarding to Cloud-Connected UC and turning on Deployment Insights for the Unified CM and IM and Presence clusters. Source: [Migrate Jabber users with Cloud-Connected UC to Webex App](https://help.webex.com/en-US/article/nejw7ue/Migrate-Jabber-Users-with-Cloud-Connected-UC-to-Webex-app), Prerequisite. Checked 2026-09-24.
[^8]: The Cloud-Connected UC Jabber migration requires full administrator privileges in Control Hub. Source: [Migrate Jabber users with Cloud-Connected UC to Webex App](https://help.webex.com/en-US/article/nejw7ue/Migrate-Jabber-Users-with-Cloud-Connected-UC-to-Webex-app), Prerequisite. Checked 2026-09-24.
[^9]: The Cloud-Connected UC Jabber migration requires every directory user in the organization to be synchronized to the identity service. Source: [Migrate Jabber users with Cloud-Connected UC to Webex App](https://help.webex.com/en-US/article/nejw7ue/Migrate-Jabber-Users-with-Cloud-Connected-UC-to-Webex-app), Prerequisite. Checked 2026-09-24.
[^10]: After Deployment Insights is turned on, updated data may take about 8 to 9 hours to appear in the migration tasks. Source: [Migrate Jabber users with Cloud-Connected UC to Webex App](https://help.webex.com/en-US/article/nejw7ue/Migrate-Jabber-Users-with-Cloud-Connected-UC-to-Webex-app), Troubleshooting Migration Issues > Bulk Updates on Control Hub or On-Premises. Checked 2026-09-24.
[^11]: After migration, users on the Webex App cannot contact Jabber users who are not in Common Identity. Source: [Migrate Jabber users with Cloud-Connected UC to Webex App](https://help.webex.com/en-US/article/nejw7ue/Migrate-Jabber-Users-with-Cloud-Connected-UC-to-Webex-app), Task flow > Select Cluster. Checked 2026-09-24.
[^12]: The migration wizard moves Unified CM users in batches. Admins can create several migration tasks but can run only one at a time. Source: [Migrate Jabber users with Cloud-Connected UC to Webex App](https://help.webex.com/en-US/article/nejw7ue/Migrate-Jabber-Users-with-Cloud-Connected-UC-to-Webex-app), Migrate Jabber users with Cloud-Connected UC to Webex App > Task flow. Checked 2026-09-24.
[^13]: Organizations using hybrid Calling must remove it for the affected users before starting the Cloud-Connected UC Jabber migration. Source: [Migrate Jabber users with Cloud-Connected UC to Webex App](https://help.webex.com/en-US/article/nejw7ue/Migrate-Jabber-Users-with-Cloud-Connected-UC-to-Webex-app), Prerequisite. Checked 2026-09-24.
[^14]: The Cloud-Connected UC Jabber migration requires Cisco Unified Communications Manager 11.5 or later. Source: [Migrate Jabber users with Cloud-Connected UC to Webex App](https://help.webex.com/en-US/article/nejw7ue/Migrate-Jabber-Users-with-Cloud-Connected-UC-to-Webex-app), Prerequisite. Checked 2026-09-24.
[^15]: With Cloud-Connected UC, the Control Hub migration wizard can move Jabber users with UCM calling, or Jabber messenger users, to the Webex App. Source: [Migrate Jabber users with Cloud-Connected UC to Webex App](https://help.webex.com/en-US/article/nejw7ue/Migrate-Jabber-Users-with-Cloud-Connected-UC-to-Webex-app), Migrate Jabber users with Cloud-Connected UC to Webex App (intro paragraph). Checked 2026-09-24.
[^16]: The contacts migration is controlled by two jabber-config.xml parameters. EnableJabber2TeamsMigration turns it on or off, and WebexTeamsDownloadURL gives the Webex App download location. Source: [Configure Users to Move Jabber Contacts and Common Settings to Webex App](https://help.webex.com/article/nyxlcde/Configure-Users-to-Move-Jabber-Contacts-and-Common-Settings-to-Webex), Jabber client configuration parameters. Checked 2026-09-24.
[^17]: The Jabber contacts and settings migration requires Jabber for Windows 12.7.3 or later, Jabber for Mac 12.8.5 or later, and the Webex App September 2020 release or later. Source: [Configure Users to Move Jabber Contacts and Common Settings to Webex App](https://help.webex.com/article/nyxlcde/Configure-Users-to-Move-Jabber-Contacts-and-Common-Settings-to-Webex), Requirements table. Checked 2026-09-24.
[^18]: The Jabber migration screen appears between 5 minutes and 3 hours after a user signs in to Jabber, or when the user starts it from the Help menu. Users can continue or skip. Source: [Configure Users to Move Jabber Contacts and Common Settings to Webex App](https://help.webex.com/article/nyxlcde/Configure-Users-to-Move-Jabber-Contacts-and-Common-Settings-to-Webex), User experience. Checked 2026-09-24.
[^19]: A migration tool built into Cisco Jabber moves contacts and common user preferences from Jabber to the Webex App. Source: [Upgrade Jabber with IM and Presence to Webex App](https://help.webex.com/en-us/article/980p3k/Upgrade-Jabber-with-IM-and-Presence-to-Webex-App), Deploy Webex App. Checked 2026-09-24.
[^20]: The Jabber migration tool moves directory contacts whose emails match the cloud identity service, custom contacts and photos, and XMPP federated contacts. It also moves chat and call notification settings and audio/video device selections, except on VDI. Source: [Configure Users to Move Jabber Contacts and Common Settings to Webex App](https://help.webex.com/article/nyxlcde/Configure-Users-to-Move-Jabber-Contacts-and-Common-Settings-to-Webex), What gets migrated (contacts and user preferences lists). Checked 2026-09-24.
[^21]: Cisco's Design and Implement guides for the UCM-to-Webex-Calling migration do not cover the Jabber-to-Webex-App transition. That guidance is in the Prepare and Plan guides (inferred). Source: [Design to migrate from Unified CM to Webex Calling](https://help.webex.com/en-us/article/nqojzwt/Design-to-migrate-from-Unified-CM-to-Webex-Calling), whole article (no Jabber mention found); compare q0pgpb Initial setup. Checked 2026-09-24.
[^22]: Webex Calling Dedicated Instance supports both Jabber and the Webex App, with the same user experience as on-premises Unified CM. Source: [Introduction to Dedicated Instance](https://help.webex.com/en-us/article/dk3o5r/Introduction-to-Dedicated-Instance), Introduction to Dedicated Instance > Simple migration path. Checked 2026-09-24.
[^23]: The Plan guide recommends dual-step user migration for larger customers who want to separate the user's soft-client change from the calling-service change. Source: [Plan to migrate from Unified CM to Webex Calling](https://help.webex.com/nw9po3o), Plan to migrate from Unified CM to Webex Calling > Migration journey - one or two steps? > Option 2: Dual step user migration. Checked 2026-09-24.
[^24]: In the first step of a dual-step migration, the soft client changes from Jabber to the Webex App and the Webex App registers to Unified CM. Users move to Webex Calling in a later step. Source: [Plan to migrate from Unified CM to Webex Calling](https://help.webex.com/nw9po3o), Plan to migrate from Unified CM to Webex Calling > Migration journey - one or two steps? > Option 2: Dual step user migration, Step 1. Checked 2026-09-24.
[^25]: Cisco announced end of sale and end of life for Jabber for Windows, Mac and VDI 12.8.x and 12.9.x on January 15, 2026. Source: [End-of-Sale and End-of-Life Announcement for the Cisco Jabber for Windows, Mac and VDI version 12.8.x and 12.9.x](https://www.cisco.com/c/en/us/products/collateral/unified-communications/jabber-windows/jabber-12-8-x-12-9-x-eol.html), Table 1 > End-of-Life Announcement Date. Checked 2026-09-24.
[^26]: For Cisco Jabber for Windows, Mac and VDI 12.8.x and 12.9.x, the end-of-sale date, end of software maintenance, end of vulnerability/security support and last date of support are all July 31, 2026. Source: [End-of-Sale and End-of-Life Announcement for the Cisco Jabber for Windows, Mac and VDI version 12.8.x and 12.9.x](https://www.cisco.com/c/en/us/products/collateral/unified-communications/jabber-windows/jabber-12-8-x-12-9-x-eol.html), Table 1. End-of-Life Milestones and Dates. Checked 2026-09-24.
[^27]: The 12.8.x/12.9.x end-of-life notice's migration path is to upgrade to the latest Cisco Jabber version, not to move to the Webex App. Source: [End-of-Sale and End-of-Life Announcement for the Cisco Jabber for Windows, Mac and VDI version 12.8.x and 12.9.x](https://www.cisco.com/c/en/us/products/collateral/unified-communications/jabber-windows/jabber-12-8-x-12-9-x-eol.html), Product Migration Options. Checked 2026-09-24.
[^28]: Calling in Webex App over MRA needs Expressway X8.11.4 or later. Push notifications need X12.6 or later, and MRA failover needs X14.0 or later. Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Call control environment requirements (Expressway). Checked 2026-09-24.
[^29]: The stated reason for moving to the Webex App first is to give users time to get used to the new app while they are still on on-premises Unified CM calling. Source: [Prepare to migrate from Unified CM to Webex Calling](https://help.webex.com/en-us/article/4yz2zd/Prepare-to-migrate-from-Unified-CM-to-Webex-Calling), Prepare to migrate from Unified CM to Webex Calling > Inventory existing devices/clients > Soft clients. Checked 2026-09-24.
[^30]: Before decommissioning IM and Presence, Cisco says to archive persistent chat messages and contact lists. Source: [Upgrade Jabber with IM and Presence to Webex App](https://help.webex.com/en-us/article/980p3k/Upgrade-Jabber-with-IM-and-Presence-to-Webex-App), Deploy Webex App (decommission IM and Presence guidance). Checked 2026-09-24.
[^31]: For iOS, Calling in Webex App (Unified CM) needs at least Unified CM 11.5(1) SU8 or 12.5(1) SU3. MRA failover needs Unified CM 14.0 or later. Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Call control environment requirements. Checked 2026-09-24.
[^32]: Cisco Jabber documentation has moved from the Webex Help Center to cisco.com, into the Cisco Jabber User Guide and the Cisco Jabber Administration Guide. Source: [Cisco Jabber](https://help.webex.com/en-US/landing/ld-n1uv5wq-CiscoJabber/Jabber), page body. Checked 2026-09-24.
[^33]: Cisco's UCM-to-Webex-Calling introduction lists Cisco Jabber as a software endpoint of the on-premises (before) architecture, not the cloud (after) architecture. Source: [Introduction (Migrate Unified CM to Webex Calling)](https://help.webex.com/en-us/article/nbedetf/Introduction), Introduction > Before: On-premises calling infrastructure components. Checked 2026-09-24.
[^34]: Depending on the Jabber deployment modes in use (IM-only, phone-only or full UC), a Webex Calling migration may also need to move Messaging and/or Meetings workloads from Jabber to the Webex App. Source: [Prepare to migrate from Unified CM to Webex Calling](https://help.webex.com/en-us/article/4yz2zd/Prepare-to-migrate-from-Unified-CM-to-Webex-Calling), Prepare to migrate from Unified CM to Webex Calling > Inventory existing devices/clients > Soft clients. Checked 2026-09-24.
[^35]: For Calling in Webex App (Unified CM), users with three or more apps and/or devices need CUWL perpetual licensing, or the organization must be on a Flex Calling subscription. Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), License requirements. Checked 2026-09-24.
[^36]: When moving from Jabber with Messenger to the Webex App, admins can do a flash cutover that updates all users at once, or a phased transition that relies on interoperability. Source: [Upgrade Jabber with Messenger to Webex App](https://help.webex.com/en-us/article/09t04o/Upgrade-Jabber-with-Messenger-to-Webex), Set Up Control Hub / Deploy Webex App. Checked 2026-09-24.
[^37]: For server performance reasons, Cisco says not to use Visual Voicemail in both Jabber and the Webex App at the same time. Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Unified CM feature requirements. Checked 2026-09-24.
[^38]: The Cisco sources in this packet show only version-specific Jabber end-of-life notices, not an end of life for the Jabber product line as a whole. On this evidence, Jabber is still a supported Unified CM client as of 2026-09-24 (inferred). Source: [Cisco Jabber for Windows - End-of-Life and End-of-Sale Notices](https://www.cisco.com/c/en/us/products/unified-communications/jabber-windows/eos-eol-notice-listing.html), notice list (nine entries; newest 14/Jan/2026). Checked 2026-09-24.
[^39]: The label 'option 1' means opposite paths in Cisco's two UCM-to-Webex-Calling guides: two-step (Webex App on Unified CM first) in the Prepare guide, and single-step in the Plan guide. Answers should name the path, not the option number (inferred). Source: [Plan to migrate from Unified CM to Webex Calling](https://help.webex.com/nw9po3o), Migration journey - one or two steps? compared with 4yz2zd Soft clients subsection. Checked 2026-09-24.
[^40]: Webex App messaging is persistent. Organizations that want less message retention should set a retention period for Webex App data. Source: [Upgrade Jabber with IM and Presence to Webex App](https://help.webex.com/en-us/article/980p3k/Upgrade-Jabber-with-IM-and-Presence-to-Webex-App), Align Messaging. Checked 2026-09-24.
[^41]: The Webex App can be deployed in phone-only mode as a calling-only client, or as the full Webex Suite when messaging and/or meetings move to the app along with calling. Source: [Prepare to migrate from Unified CM to Webex Calling](https://help.webex.com/en-us/article/4yz2zd/Prepare-to-migrate-from-Unified-CM-to-Webex-Calling), Prepare to migrate from Unified CM to Webex Calling > Inventory existing devices/clients > Soft clients. Checked 2026-09-24.
[^42]: The Prepare guide recommends that users first move to the Webex App with Unified CM calling, then move to Webex Calling. It calls this option 1. Source: [Prepare to migrate from Unified CM to Webex Calling](https://help.webex.com/en-us/article/4yz2zd/Prepare-to-migrate-from-Unified-CM-to-Webex-Calling), Prepare to migrate from Unified CM to Webex Calling > Inventory existing devices/clients > Soft clients (option 1 'Before you transition them to Webex Calling'). Checked 2026-09-24.
[^43]: With Unified CM calling, the Webex App registers as a SIP device of product type Cisco Unified Client Services Framework (CSF) on desktop, TCT or BOT on mobile, and TAB on tablets. These are the same softphone device types Jabber uses. Source: [Deployment guide for Calling in Webex App (Unified CM)](https://help.webex.com/article/nj8v6wg/Deployment-guide-for-Calling-in-Webex-App-(Unified-CM)), Overview. Checked 2026-09-24.
[^44]: Cisco's Plan guide describes single-step user migration, where users change from Jabber to the Webex App at the same time as they move from Unified CM to Webex Calling, as suited to customers with few users to migrate. Source: [Plan to migrate from Unified CM to Webex Calling](https://help.webex.com/nw9po3o), Plan to migrate from Unified CM to Webex Calling > Migration journey - one or two steps? > Option 1: Single step user migration. Checked 2026-09-24.
[^45]: Before users are moved to Webex Calling, their Jabber clients must be transitioned to the Webex App. Source: [Prepare to migrate from Unified CM to Webex Calling](https://help.webex.com/en-us/article/4yz2zd/Prepare-to-migrate-from-Unified-CM-to-Webex-Calling), Prepare to migrate from Unified CM to Webex Calling > Inventory existing devices/clients > Soft clients. Checked 2026-09-24.
[^46]: Calling in Webex App (Unified CM) needs at least Unified CM 11.5(1) SU3 for desktop. Cisco recommends 12.5(1) SU3 or later. Source: [Deployment guide for Calling in Webex App (Unified CM)](https://help.webex.com/article/nj8v6wg/Deployment-guide-for-Calling-in-Webex-App-(Unified-CM)), Prepare your Environment > Call control environment requirements. Checked 2026-09-24.
[^47]: Unified CM supports both the Webex App and Cisco Jabber as soft clients. Source: [Prepare to migrate from Unified CM to Webex Calling](https://help.webex.com/en-us/article/4yz2zd/Prepare-to-migrate-from-Unified-CM-to-Webex-Calling), Prepare to migrate from Unified CM to Webex Calling > Inventory existing devices/clients > Soft clients. Checked 2026-09-24.
[^48]: The Webex web app (web.webex.com) does not let users call phone numbers under Calling in Webex App (Unified CM). Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Webex App requirements. Checked 2026-09-24.
[^49]: In the Webex Calling target architecture, the Webex App on Windows, Mac, Android or iOS registers directly to the Webex Calling platform for calling. Source: [Introduction (Migrate Unified CM to Webex Calling)](https://help.webex.com/en-us/article/nbedetf/Introduction), Introduction > After: Cloud calling infrastructure components. Checked 2026-09-24.
[^50]: The Webex App is the only soft client supported by Webex Calling. Source: [Prepare to migrate from Unified CM to Webex Calling](https://help.webex.com/en-us/article/4yz2zd/Prepare-to-migrate-from-Unified-CM-to-Webex-Calling), Prepare to migrate from Unified CM to Webex Calling > Inventory existing devices/clients > Soft clients. Checked 2026-09-24.
[^51]: Webex App is the only soft client supported by Webex Calling, whereas Unified CM supports both Webex App and Jabber. Source: [Transitioning from Unified CM to Webex Calling — Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CALLING_Unified_CM_to_Webex_Calling.pdf), Soft Clients. Checked 2026-09-04.
[^52]: Cisco's named native migration utilities for this transition are Migration Insights, devices and features migration from Unified CM, a user and contact synchronisation utility, Unified CM data conversion, Enterprise-to-MPP phone firmware conversion, and Jabber to Webex App migration. Source: [Migrate from Unified CM to Webex Calling](https://help.webex.com/migrate-unified-cm-to-webex-calling), Named migration tools. Checked 2026-09-04.
[^53]: Cisco recommends moving users onto Webex App while they are still registered to Unified CM calling, and only then cutting them over to Webex Calling. Source: [Transitioning from Unified CM to Webex Calling — Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CALLING_Unified_CM_to_Webex_Calling.pdf), Soft Clients. Checked 2026-09-04.