Cisco Exterrnal

Cisco UCM Cloud Migration Assistant Tool

January 2021

© 2021 Cisco and/or its affiliates. All rights reserved. Page 1 of 95

Table of Contents
1. Overview ......................................................................................................................................... 5
Introduction ......................................................................................................................................... 5
Supported On-premises Cisco Unified CM Deployment Scenario .......................................................... 5
2. Preparation.................................................................................................................................... 10
Prerequisites for migrating to UCM Cloud ........................................................................................... 10
Pre-Migration Steps and Considerations ............................................................................................ 11
Migration Steps and Considerations ................................................................................................... 14
3. Migration Assistant Tool................................................................................................................ 18
Recommendations for using the Migration Tool................................................................................... 18
Install the Migration Assistant Tool ..................................................................................................... 19
Install the Migration Assistant Server.................................................................................................. 20
4. Functional flow of the Migration Assistant Tool ............................................................................ 23
Limitations in the Migration Assistant Tool............................................................................................23
5. Configuring the Migration Assistant Tool ...................................................................................... 25
Extracting configuration from the source cluster................................................................................. 25
Edit Mappings....................................................................................................................................30
Create New Migration......................................................................................................................... 33
Using Bulk Changes ...........................................................................................................................38
Viewing and Validating the Sites ..........................................................................................................40
Mapping Object Defaults ....................................................................................................................46
Mapping Tables .................................................................................................................................46
Source Type Actions ..........................................................................................................................47
Edit Settings ......................................................................................................................................48
Customers ......................................................................................................................................... 49
Clusters ............................................................................................................................................. 50
Sites .................................................................................................................................................. 53
Countries ........................................................................................................................................... 55
Transform Types................................................................................................................................55
Map Types ........................................................................................................................................57
Clone Types ......................................................................................................................................59
Skip Types ........................................................................................................................................60
Dial Plan Configuration .......................................................................................................................62
Schema Templates ............................................................................................................................63

© 2021 Cisco and/or its affiliates. All rights reserved. Page 2 of 95

 Objects .............................................................................................................................................65
Browse .............................................................................................................................................65
Configure Actions ..............................................................................................................................70
Clones ..............................................................................................................................................71
Data Validation ..................................................................................................................................72
Reports.............................................................................................................................................72
Step Changes ....................................................................................................................................72
Orphaned Objects..............................................................................................................................73
CSS Usage ........................................................................................................................................74
Reconcile Clusters .............................................................................................................................75
Bulk Changes ....................................................................................................................................77
6. Move Users/Lines/Devices ........................................................................................................... 82
Reset ITL certificate ...........................................................................................................................82
SIP Trunk Configuration......................................................................................................................83
Ignoring Rules ...................................................................................................................................84
Users Missing Email ...........................................................................................................................85
Rules ................................................................................................................................................86
Tasks................................................................................................................................................86
Number Ranges .................................................................................................................................87
DN....................................................................................................................................................87
E164 .................................................................................................................................................88
Invalid E164s .....................................................................................................................................89
Conflicts ...........................................................................................................................................90
Rollback Migration ............................................................................................................................. 91
7. Post-Migration Considerations ..................................................................................................... 94
8. Reference Documents................................................................................................................... 95
Cisco UCM Cloud Support ..................................................................................................................95
Cisco UCM Cloud ...............................................................................................................................95
UCM Cloud Service Description...........................................................................................................95
UCM Cloud Help Portal .......................................................................................................................95
Cisco Unified Communication Tools.....................................................................................................95
IM&P: Export Contact Lists..................................................................................................................95
Calling Transitioning from Unified CM to UCM Cloud Deployment Guide ..................................................95

© 2021 Cisco and/or its affiliates. All rights reserved. Page 3 of 95

 Table of Figures
Figure 1. On-Premises Collaboration Architecture................................................................................................ 6
Figure 2. Transition from On-Premises to UCM Cloud in a Typical Environment....................................................... 7
Figure 3. Migration to UCM Cloud from On-Premises ........................................................................................... 7
Figure 4. Firmware Load Information for Existing Devices.................................................................................... 11
Figure 5. Non-Default Firmware Load Information ............................................................................................. 12

© 2021 Cisco and/or its affiliates. All rights reserved. Page 4 of 95

1. Overview
Introduction
Cisco Unified Communications Manager Cloud (Cisco UCM Cloud) is part of the Cisco Cloud Calling portfolio,
powered by the Cisco Unified Communications Manager (Cisco Unified CM) collaboration technology. Cisco UCM
Cloud offers voice, video, messaging, meeting, and mobility solutions with the features and benefits of Cisco IP
phones, mobile devices, and desktop clients that connect securely to Cisco UCM Cloud.

Cisco UCM Cloud is part of the Cisco Collaboration Flex Plan set of offers, which includes key Cisco commercial and
administrative tools to facilitate the go-to-market and common subscription plans, including Webex Teams™ and
Webex® Meetings.

Cisco UCM Cloud is hosted and operated by Cisco in North America, Europe, the Asia Pacific region, and Japan. The
service offers the same Cisco Unified CM features and user experience providing an ideal migration path to the cloud
f or enterprise customers. This document discusses transitioning from on-premises Unified CM to Cisco UCM Cloud.

This guide provides information about migrating an on-premises deployment to the UCM Cloud using the Migration
Assistant Tool. The migration from on-premises to cloud is seamless for the customer's end users. During a migration,
Cisco deploys the Unified CM cluster, then an administrator at the partner configures it, taking care to replicate the on-
premises Unified source cluster. The end-user devices will now register to the UCM cloud post migration.

Supported On-premises Cisco Unified CM Deployment Scenario

Single Cluster Migration
Multi Cluster Migration

© 2021 Cisco and/or its affiliates. All rights reserved. Page 5 of 95

 Figure 1. On-Premises Collaboration Architecture

A typical deployment includes different collaboration infrastructure components on the network, a call control platform,
an edge platform, hardware, and software endpoints, and in some cases additional applications. The above
deployment includes Cisco Unified CM for call control, Cisco Unified CM IM&P for instant messaging and presence,
Cisco Expressway for remote access and business-to-business (B2B) edge services, Cisco Unity

© 2021 Cisco and/or its affiliates. All rights reserved. Page 6 of 95

 Figure 2. Transition from On-Premises to UCM Cloud in a Typical Environment

Connection for voice messaging, Cisco Emergency Responder for emergency service call routing, and user-facing
hardware (Cisco IP Phones, Cisco Webex DX and Room) and software (Cisco Jabber) IP-based endpoints. These
components may vary depending on the deployment.

Once the Unif ied CM environment is migrated to UCM Cloud, there are no Unified CM servers on the customer’s
premises. The end user’s experience, dialing, and feature set will not change in UCM Cloud as compared to the on-
premises Unified CM.

Figure 3. Migration to UCM Cloud from On-Premises

© 2021 Cisco and/or its affiliates. All rights reserved. Page 7 of 95

 Table 1. Migration to UCM Cloud

Service Post-transition Changes

Unified CM publisher and subscribers The on-premises Unified CM publisher and

subscribers are removed

Unified CM TFTP server(s) The Unified CM TFTP server(s) are removed.

DHCP server(s) The on-premises DHCP server will remain in service

and OPTIONS such as 150 are modified to point to
the appropriate TFTP server(s).

DNS server(s) The on-premises DNS server(s) will remain in service

and SRV records such as _cisco-uds must are
modified to point to the new UCM Cloud server.

Active Directory or LDAP server(s) The existing AD/LDAP server does not require
modification.

Table 2. Role of UCM Cloud Infrastructure Components

Product Description

Cisco UCM Cloud UCM Cloud call control provides device registration and
call routing services.

Cisco Expressway-C/E Edge infrastructure providing Mobile and Remote

Access (MRA) (business-to-business (B2B))
f unctionality enabling remote endpoints to connect
securely from outside the organization. Expressway is
deployed in pairs to provide firewall traversal for external
endpoints. Expressway cluster nodes may be deployed
on-premises or they can be deployed in the cloud by the
partner provider or Cisco. [Optional]

Cisco Unity Connection Cloud UCM Cloud voice messaging platform provides
voicemail and unified messaging capabilities. [Optional]

© 2021 Cisco and/or its affiliates. All rights reserved. Page 8 of 95

 Product Description

Cisco Instant Messaging and Presence Cloud UCM Cloud provides messaging, presence, and
contacts services. [Optional]

Cisco Emergency Responder Cloud UCM Cloud provides on-premises emergency

enhancement services. [Optional]

Cisco IP Phones and Cisco Jabber IP-based devices registered to UCM Cloud provides
voice and video calling capabilities

© 2021 Cisco and/or its affiliates. All rights reserved. Page 9 of 95

2. Preparation
Prerequisites for migrating to UCM Cloud
To deploy this solution, the following is required. Readers of this document should have:
● Expert experience in configuring and administering Cisco Unified Communications Manager (Unified
CM) and Cisco endpoints including IP desk phones, video devices, and Jabber soft clients.
● Read this document in its entirety before taking any action. Do not proceed if you are unclear about any
task or possible repercussions.
● Notify users that these settings will be lost post migration:
o Call history for both phones and Jabber
o Speed dials for both phones and Jabber
o Voicemail messages for both phones and Jabber
o Jabber chat history
o Jabber contact lists
● Considerations for User Experience:
o User experience does not change. Calling features and functions, dialing habits, and other
collaboration operations can all remain the same for end users.
o The following historical user-facing data from the previous on-premises system will be lost
during the transition:
 Call history for both phones and Jabber.
 Speed dials for both phones and Jabber.
 Voicemail messages for both phones and Jabber.
 Jabber chat history
 Jabber contact lists
● Create a new Application user in the Cisco Unified CM with these roles dedicated to the Migration
Assistant rather than using an existing Application User account.
o Standard AXL API Access
o Standard CCM End Users
o Standard CTI Enabled
o Standard CCM Super Users
o Standard CCM Server Monitoring
o Standard CTI Allow Control of Phones supporting Rollover Mode

© 2021 Cisco and/or its affiliates. All rights reserved. Page 10 of 95

 o Standard CTI Allow Control of Phones supporting Connected Xfer and conf
Pre-Migration Steps and Considerations
Follow these steps for migrating Unified CM configuration to UCM Cloud.
Develop a Back-Out Option
Make a backup of all collaboration and infrastructure systems to revert in the event of failure during the
migration.
Back up the existing Unified CM configuration at the cluster-level using the Disaster Recovery System
(DRS). For information on DRS refer to the Back Up the System chapter of the Administration Guide for
Cisco Unified Communications Manager and IM and Presence Service available at Unified Communications
CM Maintenance Guides.
Once the UCM Cloud environment is fully deployed and operational, the DRS archive is no longer needed
and can be discarded.
Inventory Existing Endpoints and Jabber Clients
Make a note of the inventory of your customer’s hardware and software endpoints. You will use the
inventory of phone models to identify endpoints not supported by UCM Cloud. Unsupported models must be
replaced prior to the transition. Refer to the Unified CM Deprecated Phone Models documentation.
Document the deployment mode(s) implemented for Jabber (IM-only, phone-only, and/or full UC modes)
and document any other on-premises services (Unified CM IM&P, Unity Connection, Cisco Meeting Server,
and so on) consumed by Jabber.

Upgrade All Endpoints to the Latest Enterprise Phone Firmware

You should upgrade all phones before moving them to UCM Cloud so that they do not immediately upgrade
on initial registration to UCM Cloud. See Certificate Management for details.

Upgrading before moving to Unified CM Cloud will result in a more efficient migration.
Verify that all phones are running the default firmware load by navigating to Device> Device Settings >
Firmware Load Information as shown.

Figure 4. Firmware Load Information for Existing Devices

© 2021 Cisco and/or its affiliates. All rights reserved. Page 11 of 95

 Selecting one of the hyperlinks on the Firmware Load Information page will show you which phones may not
be running the current default load. Examples of phones not using the default firmware will have a name in
the ‘Load Information’ field as shown.

Figure 5. Non-Default Firmware Load Information

Clicking the linked device name provides direct access to change to the default firmware version.

Audit the Existing Unified CM deployment

Select a representative sample of 5 or a range user types and carefully document their phone-related and
Jabber client workflows. You will use this sampling during and after migration to verify that their dialing
habits and workflows remain identical after migration.
Before performing any configuration, you must perform a comprehensive audit of the existing Unified CM
deployment that includes at least the following:
a. Certificates
b. Unified CM devices and related configuration
c. Users and their associated devices
d. Network
e. Firewall
i. Ingress Ports
ii. Egress Ports
f. DNS SRV records: _cisco_uds._tcp.<domain>
g. DHCP scope and advertised DHCP OPTIONS
h. AD / LDAP
i. Dial Plan
i. Hunt Groups
ii. Hunt Pilots
iii. Hunt Lists

© 2021 Cisco and/or its affiliates. All rights reserved. Page 12 of 95

 j. PSTN
k. SRST
l. User Provisioning methods
m. TFTP files

NOTE: Jabber 11.8 and later versions does not support SRST.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 13 of 95

Migration Steps and Considerations
This section assumes you have performed all previous pre-migration steps relevant to your customer’s current Unified
CM deployment.

Users can continue to use their phones and Jabber clients on their existing Unified CM environment while you
conf igure UCM Cloud to replicate their existing Unified CM configuration.

Once you have completed configuring UCM Cloud, you must perform testing on a representative set of phones and
Jabber clients. When test results confirm that the full Unified CM configuration is properly replicated in the UCM Cloud
cluster, initiate a maintenance window where DNS and DHCP services will be modified. This maintenance window is
required because changes to DNS and DHCP will directly impact users trying to work when their phones and Jabber
clients attempt to register to UCM Cloud.

There are multiple ways to transition an existing Unified CM cluster’s configuration to another cluster. This section
provides an overview of this transition task using the Unified CM administration web interface. Advanced
administrators may choose to use AXL, Bulk Administration Tool (BAT), 3rd-party migration tools, or some
combination of these options.

The f ollowing steps include basic Unified CM administration web interface navigation information for the primary
Unif ied CM configuration parameters:
Certificate Management
The partner is responsible for generating Certificate Signing Requests (CSR) and submitting them to the
appropriate Certificate Authority (CA). You are also responsible for installing the signed certificates as
described in Cisco documentation.
To manage Unified CM system certificates, navigate to System > Security > Certificates.

Cluster Security Mode Configuration

You must configure UCM Cloud to run in the security mode specified by your customer’s security policy.
This will already be correctly configured by Cisco’s build team based on the response to the “Secure
Calls Required” question in the Customer Questionnaire.
To determine the cluster security mode, navigate to System > Enterprise Parameters and scroll to
Security Parameters section to find the Cluster Security Mode setting. A setting of ‘0’ indicates the
cluster is in non-secure mode. A setting of ‘1’ indicates the cluster is in mixed mode (secure). To change
the Unified CM security mode, you must use the utils ctl set-cluster command at the system command
line interface (CLI) through an SSH session.
If moving from a secure mode cluster, you must perform additional steps when transitioning Cisco IP
phones from Unified CM to UCM Cloud to avoid loss of trust which would require having to physically
touch every phone to manually clear the trust list.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 14 of 95

TFTP Files
You should copy any needed TFTP files from your customer’s Unified CM environment to the temporary
SFTP server . Use the UCM Migration Assistant tool to copy the TFTP files.
Replicate the Unified CM Configuration in UCM Cloud Deployment
The following configuration parameters on the source Unified CM deployment must be replicated on the
UCM Cloud deployment. Use these reference documents to configure these parameters.

Configuration Reference Document

Parameter

UC Service https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste
Configuration mConfig/cucm_b_system-configuration-guide-1251su3/cucm_m_configure-
provisioning-
profiles.html?bookSearch=true#task_199BE83DBD58E9E7D54DFFF8B53B7A9A

Service Profile https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste

Configuration mConfig/cucm_b_system-configuration-guide-1251su3/cucm_m_configure-
provisioning-profiles.html?bookSearch=true#CUCM_TK_CADA64B7_00

Feature Group https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste

Template mConfig/cucm_b_system-configuration-guide-1251su3/cucm_m_configure-
Configuration provisioning-profiles.html?bookSearch=true#CUCM_TK_C01A92CB_00

Authentication SAML SSO-

and Authorization https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste
Configuration mConfig/cucm_b_system-configuration-guide-1251su3/cucm_m_configure-single-
sign-on.html?bookSearch=true#task_78A9B340DF6DF56D27E1CCBB1C6C32DC
SIP OAuth-
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste
mConfig/cucm_b_system-configuration-guide-1251su3/cucm_m_configure-enterprise-
parameters-and-services.html?bookSearch=true
LDAP Authendication-
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste
mConfig/cucm_b_system-configuration-guide-1251su3/cucm_m_configure-import-
ldap-users.html?bookSearch=true#CUCM_TK_C55B77FD_00

LDAP https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste
Synchronization mConfig/cucm_b_system-configuration-guide-1251su3/cucm_m_configure-import-
Agreement ldap-users.html?bookSearch=true#CUCM_TK_C302A5DA_00
Configuration

Unified CM Group https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste

Configuration mConfig/cucm_b_system-configuration-guide-1251su3/cucm_m_configure-device-
pools-1251.html?bookSearch=true#task_4084CCBBACAF1F0A18D6E291A61885AD

© 2021 Cisco and/or its affiliates. All rights reserved. Page 15 of 95

 Partition https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste
Configuration mConfig/cucm_b_system-configuration-guide-
1251su3/cucm_mp_c945f7d2_00_configuring-partitions12-
0.html?bookSearch=true#CUCM_TK_C6B3C95C_00

Calling Search https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste

Space mConfig/cucm_b_system-configuration-guide-
Configuration 1251su3/cucm_mp_c945f7d2_00_configuring-partitions12-
0.html?bookSearch=true#CUCM_TK_CF99B17F_00

Route Pattern https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste

Configuration mConfig/cucm_b_system-configuration-guide-1251su3/cucm_m_configure-call-
routing.html?bookSearch=true#CUCM_TK_CCF661C3_00

Directory Number https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CALLIN

Configuration G_Unified_CM_to_Unified_CM_Cloud.pdf

Translation https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste
Pattern mConfig/cucm_b_system-configuration-guide-1251su3/cucm_m_configure-call-
Configuration routing.html?bookSearch=true#CUCM_TK_C8E9EC3C_00

Call Park and Call https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/cuc

Pickup m_b_feature-configuration-guide-for-cisco1251su3/cucm_b_feature-configuration-
Configuration guide-for-cisco1251su3_chapter_011101.html?bookSearch=true

Transformation https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste
Pattern mConfig/cucm_b_system-configuration-guide-1251su3/cucm_m_configure-call-
Configuration routing.html?bookSearch=true%23CUCM_TK_C8E9EC3C_00

Global Dial Plan https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste

Replication mConfig/cucm_b_system-configuration-guide-1251su3/cucm_m_global-dial-plan-
Configuration replication.html?bookSearch=true

SIP Route Pattern https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste

Configuration mConfig/cucm_b_system-configuration-guide-1251su3/cucm_m_global-dial-plan-
replication.html?bookSearch=true#task_6E35813CB1F8BBFEDA7C3CC1838F081E

Route Group and https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste

Route List mConfig/cucm_b_system-configuration-guide-1251su3/cucm_m_configure-call-
Configuration routing.html?bookSearch=true#CUCM_TK_CB9925D3_00

Media Resource https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste

Configuration mConfig/cucm_b_system-configuration-guide-1251su3/cucm_m_media-resources-
overview.html?bookSearch=true

© 2021 Cisco and/or its affiliates. All rights reserved. Page 16 of 95

 Device Pool https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste
Configuration mConfig/cucm_b_system-configuration-guide-1251su3/cucm_m_configure-device-
pools-1251.html?bookSearch=true#task_5762E6A5B4CCCE76F553ED0D15BCAC69

CTI Route Point https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste

Configuration mConfig/cucm_b_system-configuration-guide-
1251su3/cucm_mp_c968bd67_00_configure-cti-applications12-
0.html?bookSearch=true#CUCM_TK_A3DF0715_00

Phone and Client https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CALLIN

Configuration G_Unified_CM_to_Unified_CM_Cloud.pdf

Trunk https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste
Configuration mConfig/cucm_b_system-configuration-guide-1251su3/cucm_m_trunk-
configuration.html?bookSearch=true#CUCM_TK_C94F7CC7_00

Device Settings https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste

Configuration mConfig/cucm_b_system-configuration-guide-1251su3/cucm_m_configure-
endpoints.html#concept_9053CA9398C8D28BC8DD3D0EC9FDF5EE

Remote https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CALLIN
Destination G_Unified_CM_to_Unified_CM_Cloud.pdf
Configuration

Headset https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1SU3/syste
Configuration mConfig/cucm_b_system-configuration-guide-1251su3/cucm_m_configure-
provisioning-
profiles.html?bookSearch=true#task_D7D576C61279FA3E882C4C693842F827

Emergency https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CALLIN
Calling G_Unified_CM_to_Unified_CM_Cloud.pdf
Configuration

© 2021 Cisco and/or its affiliates. All rights reserved. Page 17 of 95

3. Migration Assistant Tool
The UCM Cloud Migration Assistant (UCMC MA) tool assists in migrating the enterprise on-premises Cisco Unified
CM deployments to Cisco UCM Cloud.
Recommendations for using the Migration Tool
These are the hardware requirements to use the Migration Assistant Tool:

Hardware Specification

Virtual Machines 4 vCPU

8 GB vRAM

1 x 100 GB vDisk

Virtualization software VMware vSphere ESXi 6 or higher

VMware Workstation support 12 or higher

Important: Configure these steps manually in the target before you start the migration:
● CMG (Call Manager Groups)
● MRGL (Media Resource Group Lists)
● Unity connection Voice Port Group
● Referenced Phone Services (for example: Extension Mobility)
● If LDAP is used for deploying users, configure manually and complete the synchronization to import users
(MA tool will update users if they exist but will not setup LDAP synchronization). When Jabber users are
synced with LDAP, first configure the UC Service Profiles, User Profile, and Feature Group Templates.
This configuration ensures that the users are appropriately synced.

These are the recommended additional configurations:

● SIP Proxy Deployments
● Voice Gateways
● VPN based Enterprise Access
● SIP Trunks

© 2021 Cisco and/or its affiliates. All rights reserved. Page 18 of 95

 ● SRST/CME/E-SRST
● VCS/Expressway(B2B/collaboration Edge)
● ISR Gateways
● 3rd party applications
Special Considerations:
● Post Migration, Extension Mobility users are logged out from their end devices and you must log in.
● Passwords (if not using LDAP) and PIN-recommend using BAT or such to set password and PIN post
migration

Install the Migration Assistant Tool

The overview of the steps to deploy the UCM Cloud Migration Assistant is as follows:

1. Deploy VM OVA

2. Set IP address of VM

3. Install UCMC MA on VM

4. Patch UCMC MA from 2.5.4 to 2.5.5

Use this detailed procedure to execute each step.

Deploy OVA via vMware vSphere
Deploy the base verison using: ucmc-ma-2.5.4-ucmcma-552c9a7-signed.ova
If using the ovftool to deploy
ovftool --name="<VMNAME>” --powerOn --datastore="<datastore>" --net:"nat"="<network name>"
<Yarnman OVA name> "<Vi path >"
where Vi Path can take these values:
Direct ESXI "vi://<vmware username>@<ESXI IP>"
Direct ESXI with resource pool "vi://<vmware username>@<ESXI IP>/<resource Pool>"
vSphere Host "vi://<vmware username>@<vSphere>/<datacenter name/host/<Host IP or name>"
vSphere Cluster "vi://<vmware username>@<vSphere>/<datacenter name/host/<cluster name>/<Host IP
or name>"
if you use a “@” in your password, it must be escaped with %40 as in vi://foo:b%40r@hostname

Log into the UCM Migration Assistant Tool using the VMware Console with the default credentials.
Username: yarnman Password: yarnman

© 2021 Cisco and/or its affiliates. All rights reserved. Page 19 of 95

Set the IP address using the VMware console
cd /opt/yarnlab/yarnman
sudo ./scripts/bootstrap.sh

1) Do you want to set a static IP?

Enter Y
2) Select the ens XXX from the list of available interface
3) Set the IP Address for the selected interface
4) Do you want to change Hostname?
Enter Y and continue with new Hostname.
5) Do you want to change Password?
Enter Y and continue with new Password.
6) Do you want to change yarnman-protected Password?
Enter Y and continue with new Password.
7) Reboot the system for the changes to take effect.

NOTE: To change the password at any time SSH and run the passwd command.

Install Migration Assistant on the Virtual Machine

Follow these steps to install the Migration Assistant on the virtual machine you have just deployed. This configuration
automatically sets up the server and all required services.
Log in to the Migration Assistant server as user yarnman using ssh.
Change the directory to /opt/yarnlab/yarnman/
Run the install script using node and sudo:
sudo node ./scripts/install-as-core-standalone.js -p <password> --couchport <couchport> --redisport
<redisport> and substitute the <value>

© 2021 Cisco and/or its affiliates. All rights reserved. Page 20 of 95

 sudo node ./scripts/install-as-core-standalone.js -p <password> --couchport 5984 --redisport 6379
Wait for the installation is complete message to appear in the CLI. Ignore the INFO messages
displayed in the install script’s output. Do not go to Admin-App and do not attempt to add other
services.

Apply the UCMC MA 2.5.5 patch

Copy the patch file: yarnman-app-2.5.5-ucmcma-3ee909e.tar.gz.sig to /opt/yarnlab/install with SFTP

ssh into the server

Run the command : cd /opt/yarnlab/yarnman
Run the upgrade script: ./scripts/install-yarnman-app.sh yarman-app-2.5.5-ucmcma-
3ee909e.tar.gz.sig
NOTE: You can ignore these warnings during upgrade

WARNING: unsafe ownership on configuration file `/home/yarnman/.gnupg/gpg.conf'

WARNING: Using untrusted key!
WARNING: unsafe ownership on configuration file `/home/yarnman/.gnupg/gpg.conf'
chown: cannot access '/opt/yarnlab/yarnman/config/private-encryption-key.pem'

Now proceed to access the GUI.

Browse to Migration Assistant’s IP address and set the administrator account password.
Accept the End User License Agreement by selecting the check box.
Under the Set Administrator Password option, enter the password that is used later to log in to the GUI &
click “Save Acceptance and Update Administrator”.
Login with the username of the administrator and password that you created.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 21 of 95

This completes the installation of the Migration Assistant tool and you can now use the Migration Assistant tool for
migration.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 22 of 95

4. Functional flow of the Migration Assistant Tool

The dif ferent phases of the Migration Assistant tool consist of:

Extraction-Extracts data from existing on-premises systems and automatically fixes imported data errors and migrates
this inf ormation into a a common migration model database.

Validation-Validates user data using in built business rules, identifies any configuration issues in migration database
and f ixes the issues and provides reporting and bulk review capabilities.

Prepare-Establish connection between on-premises and UCM Cloud and deploys the dial plan.

Load-Automatically pushes validated data into the UCM Cloud processor.

Migrate-Moves the dial plan, trunking and phones configuration to the target systems.

Limitations in the Migration Assistant Tool

When using the load sites option, some objects with cross site dependencies will fail to add. See Viewing and
Validating the Sites in Configuring the Migration Assistant Tool for details.

Workaround: Restart the load sites task and then use the bulk change, migration point change, during site load tasks
to add objects that were not correctly added.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 23 of 95

Rename these device models when migrating between Cisco Unified CM versions

Automated migration of these devices is not supported by the Migration Assistant tool. You must manually add these
models:

CUCM 11.5 Model Name CUCM 12.5 Model Name

Standard Cisco Spark Room 55 Cisco Webex Room 55

Standard Cisco Spark Room 70 Dual G2 Cisco Webex Room 70 Dual G2

Standard Cisco Spark Room 70 Single G2 Cisco Webex Room 70 Single G2
Standard Cisco Spark Room Kit Cisco Webex Room Kit

Standard Cisco Tele Presence DX80 Cisco Webex DX80

To solve this issue, add the new model of the phone name in Source and old model name in the Target of the UC
applications and move these devices to the added models. If you upgrade to UC applications 11.5 SU9 or later
release, this issue will be solved .

Template Dial Plan

Conf igure these features manually when using the Template dial plan on the target cluster:

◦ Hunt pilot
◦ Route groups
◦ Calling search spaces

Bulk Change

When perf orming Bulk change for CUCM-PHONE objects, the Migration Assistant tool may display an incorrect count
f or f ields that are changed under events. However, the tool updates the field correctly.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 24 of 95

5. Configuring the Migration Assistant Tool
The MA tool is defined with the source and destination interfaces and the AXL user credentials. The configurations
including all lines, devices, users, and dial plan is extracted from the source Cisco Unified CM cluster and imported
into the target clusters. These configurations can be periodically rediscovered, if required for a phased migration.
Extracting configuration from the source cluster
Complete these steps to define the source and target systems.
Navigate to Cisco UCM Cloud Migration Assistant > Administration > Interfaces. Click Add
Interfaces
Select the CUCM or Unity Connection interface type as required. Specify a name and description and
Submit.

After Submit, an alert is displayed. To solve, continue with Arm Binding Settings

© 2021 Cisco and/or its affiliates. All rights reserved. Page 25 of 95

After Submit, we will get an alert like below:

To solve the alert, continue with Arm Binding Settings.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 26 of 95

Select Arm Bindings. Choose the Standalone from the dropdown and select Bind To Arm. Click
Update / Set Credentials.

For Cisco Unified CM

© 2021 Cisco and/or its affiliates. All rights reserved. Page 27 of 95

 For Cisco Unity connection:

The alert for validation is displayed.

Click Test Connection
Check the CUCM Test Connection results. If the AXL Test Connection is Green, then you can start the
migration. For Unity Connection, UCXN Test Results API should show Green.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 28 of 95

© 2021 Cisco and/or its affiliates. All rights reserved. Page 29 of 95
Repeat the earlier steps in order to add the Target UCM cloud’s (CUCM & CUC) Interface.

Use these steps to change the default migration settings based on your requirements. These are the general
migration settings, including Mappings, Schemas, and global settings for the migration. You can use the default values
or change to suit the naming conventions and mappings based on your deployment.

To open the Migration Assistant Application, navigate to the Migration Assistant from the top-right menu.

Edit Mappings

Maps f rom one value to another value with a base level of modification. Mapping tables can be global, or customer
level Can map f rom various source naming conventions to many targets.

Navigate to Cisco UCM Cloud Migration Assistant > Migrations > Mappings.
Enter default Settings for Schema.
Select the required Dial plan for the Dialplan Configuration field. Follow these guidelines:

© 2021 Cisco and/or its affiliates. All rights reserved. Page 30 of 95

 1) Clone Dial Plan-The dial plan is cloned from the source to the target system “like for like”
although some objects require mapping due to the changes in the cluster layout. Copy these
configurations:
I. Essential items that is mapped due to change in cluster layout (process nodes and
CUCM media services)
II. Create CMG/MRGL on the target system
2) Templated dial plan-This dial plan type uses the standardised dial plan but allows adding
additional fields between Cisco Unified CM versions and accommodating AXL schema
changes. Custom transform template can be added to transform configuration during
migration for the base types.
I. HCS T4 Dial plan is included by default but you can define the required dial plan
template.
II. Map the dial plan items to PT/CSS/CMG/DP/LOC/REG/MRGL
3) Map to a new dial plan- Partners can define their own dial plan template for pushing a new
dial plan. Tt can be used for partially pushing a dial plan such as only a site while country
and customer level objects are configured manually

© 2021 Cisco and/or its affiliates. All rights reserved. Page 31 of 95

 I. Manually add the dial plan to the target cluster
II. Map the dial plan items to PT/CSS/CMG/DP/LOC/REG/MRGL
Select Countries.
Select the Customer and Site Prefix.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 32 of 95

Create New Migration
Follow these steps to use the Migration Assistant Tool to extract data from the existing on-premise Unified CM and
optionally Unity Connection, validate the data with the rules, and then migrate the data

Navigate to Cisco UCMC Migration Assistant > Migrations.

Select New Customer Migration from the top right menu.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 33 of 95

NOTE: Select the Cisco Unified CM Source and Target Cluster as they are mandatory but for Unity Connection
application, the Source and cluster entries are optional.

Select the appropriate Dial plan. There are three options for the dial plan migration

The Migration Assistant Tool uses the Discovery and Allocation process to import all dial plan objects and allocates
the configurations.
● Clone Dial Plan-The Discovery and Allocation process imports all dial plan objects and allocates the
configurations to the Customer, Country, and Site. The Migration Assistant moves the cloned dial plan
elements into Cloud UCM Instance.
● Templated Dial Plan-The Discovery and Allocation process identifies key inputs for the target dial plan
including Countries, Area codes, Number ranges. User selects the dial plan template and the sites for
batch migration. The Migration Assistant pushes the appropriate dial plan elements into Cloud UCM
Instance during the load phase.
● Map to a new Dial Plan-The Discovery and Allocation imports all objects. The dial plan objects must be
mapped to the dial plan existing on the target cluster. It maps Partition, Calling search space, Device Pool,
Region, and Location. The User maps all dial plan objects from Source to the Target. The Migration
Assistant pushes all user, line, device, and feature configuration mapped to the target dial plan

Click Save Migration and Start Discovery for the session to start the discovery and associate the
settings. The events are allocated, and the validation starts. Allocation Events and Validation.
Resolve the issues that are flagged on completion of Discovery.

Select Issues & Resolution to resolve the flagged issues. You can select Disable Rule and Clear
Issue to skip an issue.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 34 of 95

Select Resolve Invalid Users to view details on resolving the highlighted issue.

Select each item and resolve the issue. In the below sample, mail ID is missing and can be rectified by
entering the email ID under Override Value > Save.

Select Re-Validate Migration, after all issues are resolved.

Navigate to Ready from the menu and select Site Suggestions.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 35 of 95

 Here Clone Dialplan is used as an example.
Complete this step if you use Clone Dialplan. If you use Templated Dial Plan Migration option, complete
the Dialplan Sites step prior to Prepare Sites step, to use the standard Dialplan.
View the suggestions for Sites, which are based on the mapping table rules created during discovery. If the
def ault mappings do not work for any sites, the Site Suggestion tab is not displayed.
Alternately you can create Sites from the Sites menu and add mapping rules using the Mappings-
>Mapping Tables option, to match the individual customer’s requirements. Then do a rediscovery .

Select Create Site, to create the sites as per the requirement. When all sites are created, select
Re-Allocate Migration to allocate these as sites, and perform a new validation. If the validation identifies
new issues, resolve them.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 36 of 95

Select Issues & Resolutions, to resolve any issues.

In this example, the flagged issues are similar. So use the Bulk change to rectify rather than
fixing each item individually.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 37 of 95

Using Bulk Changes

Bulk change provides a way to

● Allocate objects to sites

● Update configuration settings
● Ignore configuration
● Set default configuration
Navigate to Bulk Changes from the menu and select Create Bulk Change.

Select Source Object and Search Objects from the Bulk Changes Filter. This displays all objects of
the selected type.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 38 of 95

Remove any object that must be excluded, click Next. In Set Values, update items as per the
requirement and click Review Bulk Changes.

Review the changes and if the changes look good, select Apply Bulk Changes.

Navigate to Issues from the menu and click Revalidate Migration for the changed objects.
Select Issue & Resolutions, if there are any unresolved issues rectify using Re-Validate Migration.
Once all issues are resolved, the next step is Migration.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 39 of 95

 This screen displays if Clone Dialplan is used else select the existing target Dialplan. If Template Dialplan
option was selected, Dialplan Sites step displays prior to Prepare Sites.

Viewing and Validating the Sites

Navigate to Sites from the UCM Cloud MA menu.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 40 of 95

 Review the sites to be migrated by selecting them individually from the Select Column or click Bulk Select-
>Sites Shown to select all sites or alternatively select sites individually from Name column to open site
details. “P/L/U” (Phones/Lines/Users) column shows the number of the phones/lines/users at each site

Select the toggle To Migrate/ Rollback and Save the changes.

Select the Sites using:

◦ The select column on the sites view

◦ Use bulk changes search with ucmc-site as the keyword applied with the appropriate filters and set to
Apply to true

© 2021 Cisco and/or its affiliates. All rights reserved. Page 41 of 95

Navigate to Ready from the UCM MA menu.

This displays the Site Migration details.

Select Preview Prepare, to proceed with the preparation for migration.

Select Start Migration.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 42 of 95

Resolve any issues that are flagged during Prepare.
Select Continue Migration.
Select Re-Validate Migration.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 43 of 95

Resolve any issues, then select Re-Validate Migration again.

Select Preview Load which will take you to Start Migration screen.
Select Start Migration.

NOTE: It may be required to run migration point changes for “during site load” and “before any sites
loaded” to resolve circular dependencies. Perform Run migration point changes from Bulk Changes
Menu item->Create Migration Point Change.

Select Continue Migration.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 44 of 95

Select Re-Validate Migration, when completed, Select Preview Move, to continue with the final step of
migration.
Select Start Migration. The migration will be completed.

Verify if all objects are moved. Click Rollback, to backout from migration. See RollBack Migration for
details.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 45 of 95

Mapping Object Defaults

These conf igurations are used for mapping the source data to the target data objects. These configurations can be:

Overridden on the object

Specified as a hardcoded value, template, number, or state true/false.
Edited the source value and the target path.
The default Source and Target Path Mappings can be overridden

Mapping Tables

Allows to do mapping from one value to another value with some modification. The Mapping Tables allow
to map the following:

◦ Mapping Regexes
◦ Device Pools
◦ Regions
◦ Locations
◦ Call Manager Groups
◦ Route Partitions
◦ Route Lists

© 2021 Cisco and/or its affiliates. All rights reserved. Page 46 of 95

 ◦ CSS
◦ Unity Partitions
◦ Unity Search Spaces

There are some default mappings that can be matched to items such as site suggestions using the discovery option.
Also, allows to map manual entries such as naming conventions used by the individual customer.

Source Type Actions

The Source Type Actions allows you to:

◦ Transform Objects-are transformed using a template and then added to the target cluster.
◦ Map Objects-are matched to a target either in the target cluster or clusters that are added as part of a
dial plan.
◦ Clone Objects-and their associated fields are moved into the target cluster.
◦ Skip/Ignore Objects-are not added to the target cluster

This table has default values but can be changed for specific requirements

© 2021 Cisco and/or its affiliates. All rights reserved. Page 47 of 95

Edit Settings
You can view/modify the global settings. These configurations are usually set with the default values.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 48 of 95

Customers
Navigate to Customer from the UCM Migration Assistant menu, to add or modify the customer details.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 49 of 95

Select any item in the Override Value Column, click Save. This option allows to override the selected item.
Clusters
Navigate to Cluster from the UCM Migration Assistant menu, to view the Target UCM Cluster and the optional
UCXN Cluster.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 50 of 95

Use the Toggle to enable or disable the changes applied for Cluster, Call Manager, Unity/ VoiceMail, IMP/ Presence
Tabs> Click Save Changes.

You can view the modified Target and Source Servers.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 51 of 95

Source Cisco Unified CM Server Details

© 2021 Cisco and/or its affiliates. All rights reserved. Page 52 of 95

Target Cisco Unified CM Server Details

Sites
Navigate to Sites from the UCM Main menu, to view and modify the Site details:

Select Site to view from the link under the Name Column.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 53 of 95

Modify items from the Override Value Column.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 54 of 95

Countries
Navigate to Countries from the UCM Main menu, to view, add or modify the country details.

Target Mappings

Select Target Mappings to view the status of all objects. The Target Mappings are divided into four types:

● Transform types
● Map Types
● Clone Types
● Skip Types

You can view the details of each object for each type.

Transform Types

Transf orm Types object shows objects that are in Waiting, Transformed, Skipped and Moved state.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 55 of 95

Select the item from the Type column, to view details of the object type. In the screenshot, the Call Park object is
shown.

When the Source is highlighted, the Object details appear.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 56 of 95

Perf orm the following task:
● Change the details using the Override Value column or mark the item as Ignored.
● Select View Target, you can view the corresponding target.
● Select View Template to view the Template details for this object.

NOTE: Select the Sync with Cisco Unified CM option, if you changed a single object in Cisco Unified CM and want
these ref lected in the Migration Assistant.

Map Types

The Map Types show objects in Unmapped, Mapped, Skipped, Loaded state.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 57 of 95

Select the highlighted item from the Type column, to view the details of the object type. In the screenshot the CUCM-
DIALPLAN-TAG object is shown.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 58 of 95

You can change the details from the Override Value column or mark the item as Ignored. Select View Target to view
the corresponding target details.

Clone Types
Clone Types show objects in Waiting, Cloned, Skipped, Loaded state.

Select the highlighted item in the Type column, to view the items of the object type. In the screenshot the CUCM-
AUDIO-CODEC-PREFERENCE-LIST is displayed.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 59 of 95

View or modify the details from the Override Value column or mark the item as Ignored. Select View Target, to see
the corresponding target .

Skip Types

The Skip Type shows a summary of the Unmapped, Mapped, Skipped, Completed objects

© 2021 Cisco and/or its affiliates. All rights reserved. Page 60 of 95

Select the highlighted item in the Type column, to view items of the object type. In the screenshot the CUCM-
ANNUNCIATOR is shown.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 61 of 95

You can view or modify details from the Override Value column or mark the item as Ignored. Select View Target, to
view the corresponding target.

Dial Plan Configuration

Navigate to Dial plan >Configuration, to view the Global UCM Cloud Dial plan page. This page allows to change the
Dial plan including:

◦ Schema Configuration
◦ Transform Templates Settings
◦ Prefix Templates

Select the required settings to modify and Click Save.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 62 of 95

Schema Templates

Navigate to Schema->Templates, to pre-check the object to be migrated and ensure that all configurations look good.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 63 of 95

The page displays a list of templates. Search and find the required template. In the example, the Default Line template
is shown.

Select the highlighted item and view the default template. Select Preview Template. The Preview object selection
screen appears.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 64 of 95

Select the target Cluster and Object to check. In this example, the Line 2205000 instance is considered. If there are
any issue, it is displayed on the screen. You can see that the relevant Route Partition in source cluster is not mapped
which must be resolved before migration.

Once verif ication is complete, select Generate Report.

Objects

Navigate to Objects f rom the Migration Assistant menu, to view the sub menus to view, add or modify all existing
imported objects.

Browse

Navigate to Browse sub menu, to view or modify any source and target object. This View can be filtered on a few
f ields as required.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 65 of 95

Click Edit, to view the item detail.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 66 of 95

Select the item to modify, or mark the item as ignored.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 67 of 95

Additions

Navigate to Additions from the submenu, to add objects.

Select Create New Object, to create an object and you can see a list of all the object types.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 68 of 95

Select the required object from the list. Specify the cluster to create the object and complete all the required fields.
Click Save Object.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 69 of 95

Configure Actions

Navigate to Source Type Actions from the submenu, to view a list of all source items where the default action can be
customized.

◦ Transform Objects-are transformed using a template, then added to the target cluster.

◦ Map Objects -are matched to a target either in the target cluster or added as part of a dial plan.
◦ Clone Objects and all fields are asserted like-for-like into the target cluster.
◦ Skip/Ignore Objects is not added to the target cluster.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 70 of 95

 Select the required object from the Custom Value column, to modify the details and when all changes are complete,
click Save.

Clones

The Clones menu item will display summary of current Tracked Cloned Objects, the status of the objects and at the
step it is added to the target. Selecting the object from the Source Object column will display a detailed view of the
same.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 71 of 95

Data Validation

An automated report is generated, which is based on the import validation rules and compliance. Analyze the report
and manually resolve the identified issues.

Here is a list of issues that the report identifies:

● Users without Lines or Devices
● Devices with no Lines
● Devices with missing E164
● Lines without a Device

Reports

Navigate to Reports from the UCM Migration Assistant menu.

Step Changes

Navigate to Reports>Step Changes to create a report for every action taken for each step of the migration.

Select Generate Step Changes Report.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 72 of 95

Download the report after it is generated by selecting the link and view the report in an Excel format.

Orphaned Objects

This report f inds the orphaned extension mobility profiles (device profiles).

© 2021 Cisco and/or its affiliates. All rights reserved. Page 73 of 95

Select Generate Orphaned Objects to create a report for the orphaned objects.

Download the report by selecting the link on completion of report generation, and view in an Excel.

CSS Usage
Navigate to CSS Usage to generate a report on all the CSS that are in use.

Select Generate Orphaned Object, to create a report

© 2021 Cisco and/or its affiliates. All rights reserved. Page 74 of 95

Download the report by selecting the link on completion of the report generation and view in an Excel.

Reconcile Clusters

Navigate to Reconcile Clusters from the menu to reconcile Source and Target items.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 75 of 95

Select sites required for report and Migration Point or leave at default – select Generate

Select the Report Tab to view the results

The table shows three columns to display the Source objects, Target objects and the third column showing
dif ferences.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 76 of 95

Bulk Changes

Navigate to Bulk Changes from the menu to update multiple items simultaneously rather than individually.
Additionally, use Bulk Changes to run migration point changes.

The Existing Bulk Changes that are applied are displayed.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 77 of 95

Select +Create Bulk Change to create a new Bulk Change.

From the drop down, select the migration point to execute

From the Filter, select the required item to update.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 78 of 95

Select the item + fields to update

Click Review Bulk Changes to review the updates.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 79 of 95

Select Apply Bulk Changes to apply the changes .

Create Migration Point Changes

The migration change point provides a way to run in isolation any specific work flow task base on the migration
change point and optional Site(s). It can be used to roll back configuration.

Navigate to Bulk Changes from the menu.

Select +Create Migration Point Change. From the drop down, select the migration point to run.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 80 of 95

Select Execute or Rollback, then Click Start Migration Point Bulk Change.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 81 of 95

6. Move Users/Lines/Devices
Migration Assistant tool supports moving users between the old and new clusters by controlling the PSTN routing and
move devices.

◦ Allows to migrate large number of users using the trunk.

◦ Ability to move selective groups of users within large sites.
◦ Provides an option to perform roll back in case of migration failure.
◦ Provides option for dual phone deployment
◦ Can utilize user driven migration processes
◦ Clone configuration for users/lines/devices/features (and remove from on premise)

To migrate devices, use one of the following options:

◦ Consolidate Certificates. This requires DHCP changes

◦ Consolidate Certificates and TFTP proxy settings. This is an automated process.
◦ Migration Assistant performs ITL/CTL Reset

Reset ITL certificate

◦ Register handsets with the newly deployed UCM Cloud cluster.
◦ Reset ITL certif icate in handsets registered to UCM Cloud cluster to allow devices to re-register with the old
cluster, if a Rollback is required.

Select Reset, then from drop down menu select cluster that the handsets are registered. Click Run ITL Reset.

NOTE: It is recommended to consolidate the old and the new UCM Cloud cluster certificates rather than using the ITL
Reset option.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 82 of 95

SIP Trunk Configuration

Navigate to SIP Trunks from the submenu, to view all the SIP trunks discovered.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 83 of 95

Select Edit link adjacent to each trunk, to view details of the Trunk. You can choose to modify the details or mark as
Ignored.

Ignoring Rules

Navigate to Ignoring Rules from the submenu, to view all items where the rules are set to Ignore.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 84 of 95

Users Missing Email

Navigate to Users Missing Email from the submenu, to view the list of users whose email information must be added
bef ore migration.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 85 of 95

Rules

The f ollowing is a list of all the validation rules that are available, you can disable the rules if required.

Tasks

The Tasks menu lists all tasks that are accomplished. Expand each task and view by selecting the link in the Status
column.

These steps help you validate the data imported to the Migration Assistant tool

© 2021 Cisco and/or its affiliates. All rights reserved. Page 86 of 95

Number Ranges

Select Number Ranges from the UCM Migration Assistant menu, to view and modify DNs, E164 ranges, and any
Number Conflicts.

DN
Select DN, to view all the DN ranges.

Select Edit Range to view or modify each range detail.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 87 of 95

E164

Navigate to E164, to view all the E164 ranges.

Select Edit Range, to view or modify the E164 and DN range. You can use the Edit Range to disable the details.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 88 of 95

Invalid E164s

Navigate to Invalid E164s from the menu. If any invalid E164s are detected during the discovery and validation steps,
they will be displayed here.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 89 of 95

Conflicts

Navigate to Conflicts from the menu, to view any DN or E164 number range conflicts that must be resolved prior to
migration.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 90 of 95

Rollback Migration
To back out the migration, you must re-register the end devices and other services to the original cluster. To reregister
the handsets back to original cluster, use the ITL Reset f unction that will reset/ delete the ITL certificate.

To rollback migrated services in UCM Migration Assistant, there are different rollback options. It is possible to rollback
individual services or the sites that is migrated.

1. Navigate to Ready from the UCM Migration Assistant menu, select Rollback.

Select Preview Rollback Loaded, to view the Rollback screen > select Start Rollback. This option will
rollback the devices that was previously loaded into the new Cisco Unified CM.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 91 of 95

Navigate to Objects from the MA menu, to rollback individual items.

Click Browse and select the item that requires rollback. For example: If a specific phone requires rollback,
then under Object Type enter CUCM-PHONE.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 92 of 95

View the list of phones and select the phone to be rolled back, click Edit.

Select Rollback Changes, to roll back the change from the new cluster.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 93 of 95

7. Post-Migration Considerations

Once the transition from Unified CM to UCM Cloud is complete, there are a f ew additional steps that should be
considered:
Handover Document for End Users. Provide the customer an end-user document explaining that:
● The system has undergone maintenance.
● There should be no changes in phone behavior.
● Their call history will have been cleared.
● They should reset Jabber.
Provide support information so that users can receive the required assistance.

Re-configure the migrated services in Source cluster for staged migrations

In a staged migration, you must remove configuration for the migrated services from source cluster after
migrating each migration batch.
Decommission the On-Premises Unified CM Cluster
Delete or remove all on-premises Unified CM cluster node virtual machines and/or servers. Repurpose
compute resources and hardware as needed. These resources are no longer needed for call control. You
may also remove any other on-premises collaboration application nodes and or servers which have been
replicated in the Cisco cloud.

© 2021 Cisco and/or its affiliates. All rights reserved. Page 94 of 95

8. Reference Documents
Cisco UCM Cloud Support

To open support tickets use: https://yarnlab.atlassian.net/servicedesk/ or email [email protected].

Cisco UCM Cloud

https://www.cisco.com/c/en/us/solutions/collaboration/unified-communications-manager-cloud/index.html

UCM Cloud Service Description

https://www.cisco.com/c/en/us/solutions/collateral/collaboration/unified-communications-manager-
cloud/salestool-c96-742547.html

UCM Cloud Help Portal

https://ucmcloudhelp.cisco.com/

Cisco Unified Communication Tools

http://ciscounitytools.com/

IM&P: Export Contact Lists

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/configAdminGuide/12_5_1/cup0_b
_config-and-admin-guide-1251/cup0_b_config-and-admin-guide-
1251_chapter_0100011.html?dtid=osscdc000283#task_0F2C26E2BC3929146D9AF931141F1691

Calling Transitioning from Unified CM to UCM Cloud Deployment Guide

https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CALLING_Unified_CM_to_Unified
_CM_Cloud.pdf

© 2021 Cisco and/or its affiliates. All rights reserved. Page 95 of 95