Migration Factory - Part 3 – WxC-DI Migration “like for like” using wrangler_ clone

May 12

After successfully assessing and planning your migration in Part 1 using preyarn and gaining an overview of wrangler_’s features in Part 2 the next step is the actual migration. This part focuses on the "like for like" migration to Webex Calling Dedicated Instance (WxC-DI) using wrangler_ clone method. As the name suggests, this feature enables us to create an copy of the source cluster in the target environment, with only the minumum number of mandatory target mappings, simplifying the migration process and minimizing the risks associated with it.

Understanding "Like for Like" Migration

"Like for like" migration is the process of replicating your current setup in a new environment without making many changes to the configuration. Essentially, it's about creating a mirror image of your existing environment in a new cluster. This approach is particularly beneficial when the goal is to maintain consistency in operations of the dial plan and reduce potential disruption to users during the migration process.

The Power of wrangler_ Clone

wrangler_ clone, a key feature for some migrations, is designed specifically to handle "like for like" migrations. It takes the complexity out of migration by allowing you to create an exact replica of your existing Cisco Unified Communications Manager (CUCM) or Cisco Hosted Collaboration Solution (HCS) setup in your new WxC-DI environment.

The process achieves this by cloning the existing objects from the source system and preparing them for loading into the target system. This includes all devices, lines, users, dial plans, and other relevant configurations. Each object is cloned as-is, preserving all its characteristics and settings except for settings that are mapped using target mappings.

Executing the Migration with wrangler_ Clone

The migration process with wrangler_clone is divided into three stages: Prepare/Clone Step, Load Step, and Move Step.

Prepare/ Clone Step: During the prepare step, objects from your current setup are cloned or transformed and staged, ready for loading into the target environment. This involves selecting the sites to be migrated, viewing the number of objects allocated to each site, and bulk selecting all sites for migration.

Load Step: In the load step, all staged objects are added to the target UC servers, or existing target objects are updated. This process is performed in a number of steps, starting with loading objects that have not been attributed to a site, such as Phone Button Templates, Security Profiles, Dial Plan objects, etc., followed by loading of all site level objects.

Move Step: Currently, this step does not perform any function but is reserved for future use.

Ensuring Seamless Migration

To ensure a seamless migration, wrangler_clone performs a secondary validation step before the prepare step. This includes identifying dependent objects and sequencing checks, as well as checking for any object configuration or setting that could stop the object from loading into the target.

By performing a "like for like" migration using wrangler_clone, you can ensure a smooth and efficient transition to WxC-DI. In the next part of this series, we will delve into a more complex migration scenario using wrangler_map for transforming data during the migration process.

Stay tuned as we continue to explore the migration journey from Cisco CUCM and Cisco HCS to Webex Calling Dedicated Instance using the powerful wrangler_ tool suite.