Use Migration Insights to make an informed decision about migrating to Webex Calling. Based on that information, you can confidently migrate to Webex Calling.
Migration Insights
| 1 |
From the customer view in https://admin.webex.com, go to Services > Updates & Migrations. In the Unified CM upgrade utilities section, go to Migration Insights card and click View. Collect Unified CM details, such as the list of users and devices that you plan to import to the Webex Cloud Calling service. Use the Unified CM Bulk Admin Tool to get the tar files, see Import Users Using the Bulk Administration Tool (BAT) for detailed information and then import the files. | ||||
| 2 |
In the Import data from UCM to generate a migration insight report window, drag and drop the .tar file.
The .tar file takes some time to upload. Once uploaded, the successful window appears. | ||||
| 3 |
Refer to CDR Respository Manager on collection of CDR files. The maximum size of upload for CDR file is 2GB. Refer to CDR Preprocessing and follow the readMe to know more about the suitable configuration to run the script for Pre-processing the CDR file before uploading.
For CDR Reports, drag and drop the .gzip file in the Drag and Drop a .gzip file here or browse for files pane. 
| ||||
| 4 |
To delete the uploaded generated reports , click three dots on the top right and select Delete. | ||||
| 5 |
To download the CSV files (.zip file), click three dots on the top right and select Export CSV. After successful download, you can view the detailed information on the CSV files. |
Export ZIP File
Once you export and download the .zip file, here are the list of output CSV files included in this zip file:
-
ImportedDataBulk.csv - This file contains the extracted data from enduser.csv and phone.csv of the imported CUCM tar files. This CSV contains all the devices from the phone.csv
- DeviceEligibility(firmwareMigration).csv - This file contains the records of IP phone devices and this report provides information about the migration eligibility of the devices in firmware.
- MTSuppportedDevice.csv - This file contains the records of Room OS devices, ATA devices, Third Part devices, etc., and provides the information if the device is supported on WxMT or not.
- DevicePoolNumbers.txt - This is a text file. This file contains the records of all the numbers in a particular device pool.
-
GroupMigrationReport.csv - This file contains reports about devices and users that can be migrated together. The report is generated based on shared lines, huntpilot, callqueue, callpark, callpickup group configuration.
-
FeatureUsageBasedDeviceEligibilityReport.csv - This report is generated using UCM .tar and CDR file. The report contains information about the migration eligibility of the devices based on the feature usage inspected from CDR records.
-
FeatureUsageWithLastUsageDateReport.csv – This report is generated using UCM .tar and CDR file. The report contains the count of number of times huntpilot and callqueue number is used along with their last usage date.
-
UserWorksapceLastUsage.csv – This report is generated using UCM .tar and CDR file. The report contains the records of users/workspace and their last usage date. It also contains reports of softclients and hardphones.
-
DidUsageReport.csv - This report is generated using UCM .tar and CDR file. The report contains the records of DID usage for both assigned and unassigned DIDs.
- Read Me- Contains detailed information on the CSV files.
View your Report
ImportedDataBulk.csv
| Column | Description | Example |
|---|---|---|
| User ID | The unique identifier of the UCM user. | username |
| The email address of the UCM user. | username@email.com | |
| Name | The full name of the UCM user. | firstName + lastName |
| Device Description | A description of the UCM device. | Main Lobby Device |
| Device Pool | The UCM device pool to which the device belongs. | AshwiniOPUS-UP |
| Device Name | The name of the UCM device. | CUCTRDXVE |
| Location | The physical location of the UCM device. | Hub_None |
| Directory Number | The UCM directory number of the device. | +12225553333 |
| E164 | The E.164 number of the device. | +12225553333 |
| Route Partition | The route partition to which the UCM device belongs. | CORE 8digit |
DeviceEligibility.csv
| Column | Description | Example |
|---|---|---|
| User ID | The unique identifier of the UCM user. | username |
| The email address of the UCM user. | username@email.com | |
| Name | The full name of the UCM user. | firstName + lastName |
| Device Description | A description of the UCM device. | Main Lobby Device |
| Device Pool | The UCM device pool to which the device belongs. | AshwiniOPUS-UP |
| Device Name | The name of the UCM device. | CUCTRDXVE |
| Model | The model of the device | Cisco 8865 |
| Eligibility | The firmware migration eligibility. Checks for 78, 88 series devices. The Possible values are Eligible, Ineligible, and Unknown. Unknown is reflected when the service is not able to determine the eligibility status. | Eligible |
MTSupportedDevices.csv
| Column | Description | Example |
|---|---|---|
| User ID | The unique identifier of the UCM user | username |
| Name | The full name of the UCM user. | firstName+lastName |
| Device Description | A description of the UCM device. | Main Lobby Device |
| Device Pool | The UCM device pool to which the device belongs. | AshwiniOPUS-UP |
| Device Name | The name of the UCM device. | SEP007E452DDEG7 |
| Model | The model of the device | Cisco 7961G-GE |
| Directory Number | The UCM directory number of the device. | +12225553333 |
| E164 | The E.164 number of the device. | +12225553333 |
| Supported in WxC MT | Checks if supported or not in WxCMT for ATA, Room OS, Third Party etc | No |
DevicePoolNumbers.txt
| Column | Description | Example |
|---|---|---|
| Device Pool | The UCM device pool to which the device belongs. | AshwiniOPUS-UP |
| E164 Numbers | The comma separated number list, each row contains 1000 numbers. | +12225553344,+12225553345 |
GroupMigrationReport.csv
| Column | Description | Example |
|---|---|---|
| Feature Type | The feature type of the device. | HUNT PILOT, CALL QUEUE, CALL PARK GROUP, CALL PICKUP GROUP, SHARED LINE |
| Config Name | The line of the feature. | +12225556666 |
| User | The user of the device. | username |
| Email ID | The email address of the user. | username@email.com |
| Device Name | The name of the device. | CISCO8875 |
| Device Pool | The device pool to which the device belongs. | AshwiniOPUS-UP |
| Line | The line of the device. | +12225554444 |
| Route Partition | The route partition to which the device belongs. | CORE 8digit |
FeatureUsageBasedDeviceEligibilityReport.csv
| Column | Description | Example |
|---|---|---|
| User ID | The unique identifier of the UCM user. | username |
| Email ID | The email address of the user. | username@email.com |
| Device Name | The name of the device. | CISCO8875 |
| Device Pool | The device pool to which the device belongs. |
AshwiniOPUS-UP |
| Line | The line of the device. | +12225556666 |
| Migration Elligibility |
The migration eligibility of the device. The values are: Eligible - The device is eligible for migration. Unknown - The exact eligibility of the device cannot be determined. It means, from the CDR records, we found usage of features which are not supported by Webex. You should contact CISCO TAC for further assistance. | unknown |
| Details |
The values are: Empty: If MigrationElibility is eligible, NotSupportedFeatureList: if MigrationEligibility is unknown |
Not Available feature List: RandomFeatureABC(12), Please contact CISCO for more info on the device.
|
FeatureUsageWithLastUsageDateReport.csv
| Column | Description | Example |
| Feature Type | The feature type of the device. |
Hunt Pilot ,Call Queue |
| Config Name | The line of the feature. | +12225557777 |
| Usage Count | The usage count of the line. | 23 |
| Last Usage Date | The last usage date of the feature on particular line. | 15/01/2024 |
UserWorksapceLastUsage.csv
| Column | Description | Example |
|---|---|---|
| User ID | The unique identifier of the UCM user. | username |
| The email address of the UCM user. | username@email.com | |
| isAnonymous | This contains if it is workspace or not. | yes |
| deviceName | The name of the device. | SEP22555d409 |
|
isIpPhone
|
This contains if it is softclient or not.
| yes |
|
Model
|
UCM Device Model.
|
Cisco 8851
|
|
Last Usage Date
|
The last usage date of the device.
| 23/01/2024 |
|
DaysSinceLastUseAtReportDate
|
The number of days since the last usage date of the device on the day of report generation.
|
8 It means this device was last used 8 days back from report genration date.
|
DidUsageReport.csv
| Column | Description | Example |
| User ID | The unique identifier of the UCM user. | username |
| Email ID | The email address of the user. | username@email.com |
| DID | The DID Number | +12225553409 ( It can be and cannot be same as directoryNumber) |
| Device Name | The name of the device. | CISCO 8875 |
| Device Pool | The device pool to which the device belongs. | AshwiniOPUS-UP |
| Directory Number | The UCM Directory Number of the device | AshwiniOPUS-UP |
| CallingPartyNumberCount | The number of times the DID was used as the calling party number. | 20 |
| OriginalCalledPartyNumberCount | The number of times the DID was used as the original called party number. | 30 |
| FinalCalledPartyNumberCount | The number of times the DID was used as the final called party number. | 40 |
| sumAllCalledPartyNumbers | The total number of times the DID was used as the calling party number. | 90 |
| Last Usage Date | The last usage date of the DID. | 16/11/2023 |
| DirectoryNumberType | The type of the DID. It can be unassigned or assigned. | For Unassigned type , the details about userID and device name coming from cdr records. |
 | we follow a strict data privacy policy. Once reports are generated, we have implemented measures to ensure that user data is handled securely. We do not store any user data beyond the report generation process. This includes deleting the tar file and any other data used to create the reports. Furthermore, the reports themselves are securely uploaded to our protected file storage. To provide users with full control over their data, we also offer the option to manually delete the reports when they are no longer needed. |
