Collaboration Transitions
Available Languages
Contents
Collaboration Transitions
Collaboration Transitions is focused on moving collaboration workloads from existing on-premises, hybrid, and cloud products and solutions to the latest on-premises, hybrid, and cloud-delivered collaboration services (see Figure 1).
Figure 1. Collaboration Applications & Services Delivery: On-Premises, Hybrid, and Cloud Transitions
As customers transition existing collaboration workloads to the newest collaboration applications and services, they must understand the implications of this transition and the steps required to make the transition.
To guide our customers during these transitions, Cisco is defining and testing specific paths for transitioning primary collaboration services to the latest Cisco collaboration applications and services.
This program defines a new type of prescriptive, validated deployment model building on the existing Collaboration Preferred Architectures (PA) available at https://www.cisco.com/go/pa. This new model addresses the transitions to the latest collaboration experiences for on-premises, hybrid, and cloud collaboration application and services.
This deployment model is applied to specific collaboration workload transition scenarios. For each transition scenario, iterative validation of the transition is undertaken to identify issues and barriers hindering the transition. Identified issues and barriers are driven back to the product teams to address and improve the overall solution. As gaps are closed and issues are resolved, the transition validation is repeated, and transition maps and other collateral are updated to reflect these improvements.
As shown in Figure 2, in order to transition collaboration workload deployments to the latest Cisco application and service, customers need to answer the question: How do I get from where I am to where I want to be?
The answer rests with Collaboration Transitions which maps the transition to the latest and most sophisticated collaboration services showing customers how to implement the transition and the changes and benefits along the way.
Migration Readiness
Before beginning any transition, it is important to evaluate the existing deployment and determine what needs to be completed before the migration can begin. Understanding migration readiness and leveraging tools like readiness assessments help to determine whether the existing environment is ready to be migrated and is critical for a successful transition.
Table 1. Migration Readiness Information
| Migration |
Migration Readiness Documentation |
| Webex Migrations (Includes Jabber to Webex App & UCM to Webex Calling) |
Webex Migrations - Customer Journeys & Readiness As customers prepare to transition to Webex there are some pre-migration activities that may need to be completed and others that should be strongly considered to provide the best experience for administrators and end users. This document covers all the migration journeys from on-premises Unified CM to Webex for Messaging, Meetings and Calling (Unified CM or Webex Calling) and identifies the readiness activities for each workload. Use this document to understand all the workload journeys, the phases of each journey and the pre-migration activities within each phase. In addition, it provides links to additional resources for the pre-migration activities. Information in this document will help the customer complete Information in this document will help the customer complete the Webex Migrations - Customer Readiness Assessment (see below). |
| Webex Migrations - Customer Readiness Assessment As customers prepare to transition to Webex for Messaging, Meetings and Calling (Unified CM or Webex Calling) this assessment document will help to determine how ready they are for the migration. By answering some questions about the customer's current Webex and on-prem UC environment, deployment, and configurations, it will quickly assess the required, recommended, and optional requirements for transitioning to Webex and identify where the customer may need to take some actions before starting their migration. |
Transition Scenarios
Along with product and support documentation, the following documentation is available to illustrate and explain the transitions:
■ Transition Maps — Illustrates the recommended steps for transitioning from an existing collaboration deployment to the latest on-premises, hybrid, or cloud solutions accounting for the changes required during and after the transition.
■ Transition Deployment Guides – Provides technical background, deployment steps, and the key differences and considerations for transitions of collaboration workloads to the latest on-premises, hybrid, and cloud deployments.
Links to this documentation Is provided in the scenario workload transition tables in the sections below.
Transitions scenarios are divided into the following categories:
■ Calling - Covering on-premises, hybrid, and cloud calling transitions.
■ Clients – Covering on-premises, hybrid, and cloud client transitions.
■ Contact Center – Covering on-premises, hybrid, and cloud contact center transitions.
■ Meetings – Covering on-premises, hybrid, and cloud meeting transitions.
■ Messaging – Covering on-premises, hybrid, and cloud messaging transitions.
Calling
Table 2. Collaboration Workload Transitions: Calling
| Workload |
START |
TARGET |
Key Considerations & Benefits |
Transition Documentation |
Product / Solution Documentation |
||
| Type |
Product(s) |
Type |
Product(s) |
||||
| Calling |
On-Premises |
Unified CM |
Cloud |
Webex Calling |
§ Delivers an advanced set of enterprise-grade PBX features § Provides a rich user experience across both Webex Calling devices and Webex apps § Part of an integrated user experience with Webex Meetings and Webex devices, including IP Phones and Webex Room series |
||
| On-Premises |
Unified CM |
Cloud |
UCM Cloud |
§ Enterprise-grade cloud calling and team collaboration offered through a flexible subscription model. § Shorter deployment time with no requirement for upgrade and maintenance staff. § Licensing is managed by Cisco. |
|||
Clients
Table 3. Collaboration Transitions: Clients
| Workload |
START |
TARGET |
Key Considerations & Benefits |
Transition Documentation |
Product / Solution Documentation |
||
| Type |
Product(s) |
Type |
Product(s) |
||||
| Clients |
On-Premises |
Jabber |
Hybrid |
Webex |
§ Make calls in Webex through on-premises Unified CM and control Unified CM registered desk phones directly from Webex . § Use the configuration that’s in place for your Unified CM deployment (such as location, bandwidth settings, point-to-point media, and so on) § Reduce on-premises infrastructure by moving messaging to Webex. |
Jabber Data Sheet (Desktop) Jabber Data Sheet (Mobile) |
|
Contact Center
Table 4. Collaboration Workload Transitions: Contact Center
| Workload |
START |
TARGET |
Key Considerations & Benefits |
Transition Documentation |
Product / Solution Documentation |
||
| Type |
Product(s) |
Type |
Product(s) |
||||
| Contact Center |
On-Premises |
Unified Contact Center Express (CCX) |
Cloud |
Webex Contact Center (CC) |
§ Quickly transform your contact center from a cost center to a strategic business asset. § Webex Contact Center in the cloud provides flexibility and scalability. § Webex Contact Center provides high levels of security and data privacy. |
||
Meetings
Table 5. Collaboration Workload Transitions: Meetings
| Workload |
START |
TARGET |
Key Considerations & Benefits |
Transition Documentation |
Product / Solution Documentation |
||
| Type |
Product(s) |
Type |
Product(s) |
||||
| Meetings |
On-Premises
OR
Hybrid |
TelePresence Server / Conductor
OR
CMR-Hybrid |
Cloud |
Webex |
§ TelePresence Server EoL § Lower admin overhead (reduced TCO) § Adhoc and scheduled meetings (Personal Rooms, @meet, @webex, OBTP) § Global meeting service with increased scale and monthly feature updates. § Modern video first Webex platform with better in-meeting user experience |
||
| Meetings |
On-Premises |
Cisco Meeting Server |
Cloud |
Webex |
§ Lower admin overhead (reduced TCO) § Global meeting service with increased scale and monthly feature updates. |
||
| Meetings |
On-Premises
|
TelePresence Server / Conductor
|
On-Premises |
Cisco Meeting Server |
§ TelePresence Server EoL § Improved features and increased scale. § Simplified management § Web-based conferencing for all (WebRTC) |
||
| Meetings |
On-Premises |
Cisco Webex Meeting Server |
On-Premises |
Cisco Meeting Server |
§ Webex Meeting Server EoL § Video conferencing as well as audio and web-based conferencing § Simplified management |
||
| Meetings – Video Endpoints |
On-Premises |
Unified CM / VCS (Expressway) |
Cloud |
Webex |
§ Access to Webex features: o Cloud whiteboarding o Webex Assistant – Voice Control § Endpoint administration including automatic firmware management |
||
| Meetings – Clients |
Cloud |
Webex Meetings App |
Cloud |
Webex |
§ Schedule, join, and manage your meetings with a single unified application. § Simplify app management for IT admin. § Access to Webex platform services such as calendar and compliance services. |
||
Messaging
Table 6. Collaboration Workload Transitions: Messaging
| Workload |
START |
TARGET |
Key Considerations & Benefits |
Transition Documentation |
Product / Solution Documentation |
||
| Type |
Product(s) |
Type |
Product(s) |
||||
| Messaging |
On-Premises |
Unified CM IM&P –Distributed |
On-Premises |
Unified CM IM&P –Centralized |
§ Provides appropriate scale for IM&P outside of calling scale. § Eliminates version dependency between Unified CM call control and IM&P. § Reduces IM&P upgrade times |
||
| Messaging |
On-Premises / Hybrid
|
Jabber with Unified CM IM&P / Webex Messenger
|
Cloud |
Jabber with Webex Messaging |
§ Persistent Messaging (1:1, Spaces, File Sharing) § Reduced TCO (no IM&P required, no external DB/fileservers for persistent chat) § Integration with rich Webex messaging APIs |
Because Jabber Team Messaging Mode is retired, this transition is no longer recommended. For more details refer to Making the Move to Modern Messaging |
Jabber Data Sheet (Desktop) Jabber Data Sheet (Mobile) |
Related Information
The Collaboration Transition architecture is based on the Enterprise (on-premises) Preferred Architecture (PA) and is included under the Collaboration PA documentation framework. For more details on deploying both on-premises and hybrid collaboration solutions, refer to the Preferred Architecture documentation available at https://www.cisco.com/go/pa.
Feedback