As cloud registration becomes more common, organizations may want to migrate endpoints that are currently registered with on-premise systems such as CUCM/TMS/VCS to a cloud-based registration model such as Control Hub. Performing this migration without proper planning can result in endpoints not being visible or, in some cases, the loss of historical endpoint data.
WXP Collaboration supports migration of endpoint data during on-premise to cloud transitions by tracking the existing CUCM/TMS/VCS registered endpoint to the cloud registered Control Hub endpoints with as little manual intervention as possible.
Some guidelines to minimise risk and data loss on WXP collaboration during the migration process.
What to avoid:
Manually duplicate endpoints in the Admin portal.
Deleting existing endpoints in the Admin portal.
Automatic Endpoint Migration in WXP collaboration
When Control hub is integrated, the new endpoint data is automatically pulled from Control Hub into WXP collaboration and endpoint data records are automatically updated within 24-48 hours of integration as follows :
The managed endpoints from Control Hub are added to the Managed Endpoint List in the WXP Collaboration Admin Portal.
The endpoint data is check to see if the endpoint has already existed by using the serial number to determine if the endpoint was previously registered with CUCM/TMS/VCS.
If the endpoint has already existed and is active, the existing endpoint record is updated with the new Control Hub registration data, which overwrites the old CUCM/TMS/VCS registration.
If endpoint has already existed and is not active, the entry with the new Control Hub registration is updated, the endpoint is re-enabled so it will now be added into the endpoint list.
Recommended Migration Approach
Note : Ensure that the WXP Collaboration support is notified when you plan to start a migration so your UC environment can be reviewed and environment-specific guidance can be provided.
Create a list of all endpoints that are currently listed in Endpoints dataset on WXP Collaboration. You may request this by opening a support case.
Create a new monitoring group for cloud-registered endpoints and move the existing CUCM/TMS/VCS endpoints into this group.
Perform the Control hub in the Admin Portal as described in Cisco Control Hub for Devices Integration.
Wait for 24-48 hours for the automatic endpoint migration to complete. After 24-48 hours, all the endpoint record would be updated with Control Hub data.
Ensure that the endpoints have the new admin-local credentials. This can be achieved by the Control hub integration from the new monitoring group.
Validate the new endpoint dataset with the old endpoint dataset saved in step 1, to ensure all the endpoints are listed.
Once the data is validated, the old endpoints registered in CUCM/TMS/VCS can be deleted.
IMPORTANT Note : If the CUCM/TMS/VCS is going to be decommissioned, it is important to ensure the endpoints are first deleted from it. Once endpoints are deleted, please allow 24-48 hours for the endpoint record in WXP Collaboration to update BEFORE disabling or deleting the infrastructure from the WXP Collaboration Infrastructure list.
Contact Us
For any assistance, create a support case or email support@wxp.hp.com.