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?
Figure 2. Collaboration Transitions: Mapping the Move to the Latest Collaboration Applications and Services
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.
Before beginning any transition, it is important to evaluate the existing deployment and determine what needs to be done before the migration can begin. Understanding migration readiness and leveraging tools like readiness assessments to determine whether the existing environment is ready to be migrated is critical for successful transitions.
Table 1. Migration Readiness Information
Migration Readiness Documentation
Jabber to Webex App Migrations
Jabber to Webex App Migration - Customer Journeys & Readiness_v2.0
As customers prepare to transition to the Webex App 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 the Migration Journey to the Webex App for Messaging, Meetings and Calling (Unified CM) 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 the Jabber to Webex App Migration - Customer Readiness Assessment (see below).
Jabber to Webex App Migration - Customer Readiness Assessment
As customers prepare to transition to the Webex App for Messaging, Meetings and Calling (Unified CM) 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 collaboration environment, deployment, and configurations, it will quickly assess the required, recommended, and optional requirements for transitioning to the Webex App and identify where the customer may need to take some actions before starting their migration.
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.
Table 2. Collaboration Workload Transitions: Calling
Table 3. Collaboration Transitions: Clients
Table 4. Collaboration Workload Transitions: Contact Center
Table 5. Collaboration Workload Transitions: Meetings
Table 6. Collaboration Workload Transitions: Messaging
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.