Migration Factory - Part 4 - WxC-DI Migration Transformation Using wrangler_ Map
Having established a solid understanding of the "like for like" migration process using wrangler_clone, we now venture into more complex migration scenarios. In this fourth installment of our series, we explore the use of wrangler_map for data transformation during migration to a Webex Calling Dedicated Instance (WxC-DI). This feature is ideal for scenarios where the target environment is significantly different from the source, requiring a higher degree of customization and transformation.
Transformation Migration: An Overview
Unlike "like for like" migrations, transformation migrations involve significant changes to the configurations as you move from the source to the target environment. These changes might include altering dial plans, modifying device configurations, consolidating clusters, or even completely revamping the system architecture. Transformation migration is ideal for instances where you wish to make improvements or changes to your system during the migration process.
The Power of wrangler_ Map
wrangler_map is another feature for migrations, specifically designed to handle complex transformations during migration. It provides powerful mapping capabilities that allow for granular control over how each object is transformed and loaded into the new environment.
One of the key capabilities of wrangler_map is its ability to replace dial plans during the migration process. Dial plans, which define how telephone numbers are dialed within a network, are a critical aspect of any unified communications system. With wrangler_map, you can redesign and replace your existing dial plan with a new one that better fits the needs of your organization in the WxC-DI environment.
Executing Transformation Migration with wrangler_ Map
Much like the process with wrangler_clone, migration with wrangler_map also follows the three-stage process: Prepare/Map Step, Load Step, and Move Step.
Prepare/ Map Step: In this step, wrangler_map takes the existing objects from your source system and transforms them based on your specified mappings. This includes modifying attributes, changing configurations, and replacing dial plans. The transformed objects are then staged and ready for loading into the target environment.
Load Step: The load step in wrangler_map works similarly to wrangler_clone, with all staged objects added to the target UC servers. However, the key difference here is that the objects loaded are transformed versions of the original, adapted to suit the new environment.
Move Step: While currently non-functional, this stage is reserved for future enhancements to further streamline and optimize the migration process.
wrangler_ Map for HCS Migration and Cluster Consolidation
Beyond dial plan transformation, wrangler_map is also an excellent tool for migrating from a Cisco Hosted Collaboration Solution (HCS) to a new dial plan or transforming the existing environment. Furthermore, it is the preferred method for cluster consolidation, allowing you to merge multiple clusters into a single, unified system in the target environment.
Transformation migration with wrangler_map opens the door to significant system enhancements during the migration process. By leveraging its powerful mapping and transformation capabilities, you can create a WxC-DI environment that not only replicates but also improves upon your existing setup.
In the next part of this series, we will explore advanced migration features such as cluster consolidation and phased migration. Stay tuned as we continue our deep dive into the journey of migrating from Cisco CUCM and Cisco HCS to Webex Calling Dedicated Instance using the wrangler_ suite.
Try out wrangler_ using Cisco dCloud labs on demand
Note: that the wrangler_ lab is availible in multiple geographies other than US(RTP)
