...
The Initial migration as Clone Migration or Template/ Simplified Dial Plan migration with this used as master dialplan for consecutive (mapped) migrations
A new dialplan could be deployed manually (or by engineer developed tools). The initial and consecutive migrations could then be performed as separate Mapped migrations.
Separate Clone Migrations but to the same target. This would not be a recommended option as the target cluster would end up with a separate dialplan for each source cluster migrated.
| Info |
|---|
Important Note regarding these options is that duplicate objects that may exist between the second and any consecutive migrations and the target will not be flagged in the discovery. These duplicate object configurations will be updated in the target from the last migrated cluster of the same. Thus it is important that any potential duplicates are reviewed in CUCM and be known beforehand. If the duplicate in consecutive migrating clusters have a different configuration than the target object, and the target configuration is not to be changed, then the source cluster configuration of this object will need to be skipped, or if required, reconfigured in the source CUCM cluster. |
...