Cisco UCM Migration - Fresh Install with Data Import


In this lab, you will learn how to migrate Cisco Unified Communications Manager to a new CUCM 15 deployment using the Direct Refresh Install with Data Import method.

The migration uses an SFTP server to transfer the exported CUCM data to the newly installed CUCM system. This approach is useful when you want to perform a fresh installation while preserving important configuration data from the existing environment.

Table of Contents

Migration Overview

A CUCM migration can be required when moving to a newer software release, replacing an older virtual machine, changing the deployment platform, or rebuilding the system using a fresh installation.

In this demonstration, the target system is CUCM 15 and the migration is performed by creating a fresh CUCM installation and importing the existing configuration data.

The main objective is to preserve the required Unified Communications configuration while moving to a clean target deployment.

What Is Direct Refresh Install with Data Import?

Direct Refresh Install with Data Import allows a new CUCM system to be installed and then populated with data exported from the existing environment.

Instead of performing only an in-place upgrade, the administrator prepares a fresh target system and transfers the required data through the supported migration workflow.

This method can be useful when:

  • A fresh CUCM virtual machine is preferred.
  • The target release requires a new deployment.
  • The administrator wants to migrate configuration data rather than preserve the original VM.
  • The existing CUCM environment needs to be replaced as part of the upgrade project.

Migration Prerequisites

Before starting the migration, verify the source and target environments carefully.

  • Confirm the current CUCM version and target CUCM version.
  • Review the supported migration and upgrade path.
  • Verify the target virtual-machine requirements.
  • Confirm CPU, memory, disk, and VMware compatibility.
  • Prepare a reliable SFTP server.
  • Verify network connectivity between CUCM and the SFTP server.
  • Record IP addressing, DNS, NTP, hostname, and domain information.
  • Take the required backups before making any production changes.
  • Document the current cluster and node roles.

Using SFTP for Data Import

The SFTP server is used as the transfer point between the existing CUCM system and the new CUCM deployment.

Before starting the export or import process, verify:

  • SFTP server IP address or hostname
  • Username and password
  • Destination directory
  • Available disk space
  • TCP connectivity from CUCM to the SFTP server
  • Read and write permissions

A failed SFTP connection can interrupt the migration workflow, so connectivity should be tested before the maintenance window begins.

Migration Workflow

The general migration workflow demonstrated in this lab is:

  1. Review the existing CUCM deployment.
  2. Prepare the SFTP server for migration data.
  3. Export the required data from the source CUCM system.
  4. Deploy the new CUCM 15 virtual machine.
  5. Complete the initial installation of the target CUCM server.
  6. Select the Data Import migration method.
  7. Provide the SFTP server information.
  8. Import the migration data into the new system.
  9. Allow CUCM to complete the installation and database processing.
  10. Verify services, configuration, and application functionality.

Post-Migration Verification

After the migration completes, verify the new CUCM system before returning the environment to normal operation.

Recommended checks include:

  • Verify all expected CUCM nodes are present.
  • Confirm database replication status.
  • Check Cisco CallManager and related services.
  • Verify phones register successfully.
  • Test internal calls.
  • Test inbound and outbound PSTN calls.
  • Verify trunks and gateways.
  • Check route patterns and calling search spaces.
  • Verify device pools, regions, locations, and media resources.
  • Confirm user and directory integration.

Important Considerations

A CUCM migration should always be treated as a planned change with a defined maintenance window and rollback procedure.

  • Validate the supported source-to-target migration path before starting.
  • Confirm that the target CUCM version supports the existing phone models and integrations.
  • Review licensing requirements for the target release.
  • Verify certificates and trust relationships.
  • Check integrations such as Unity Connection, IM and Presence, UCCX, gateways, and SIP trunks.
  • Plan for service interruption during the migration window.
  • Keep the original system available until the new deployment has been fully validated.

Video Demonstration

The following video demonstrates the Cisco UCM migration process using a fresh installation and SFTP-based data import.

Conclusion

The Direct Refresh Install with Data Import method provides a practical way to move an existing CUCM environment to a newly installed CUCM 15 system while preserving the required configuration data.

The success of the migration depends on proper preparation, a reliable SFTP server, a supported upgrade path, correct target-system sizing, and thorough post-migration verification.

Before using this process in production, validate the exact migration path and compatibility requirements for your current CUCM release and target version.

About the Author

Ehsan Emad is a networking and cybersecurity expert with four CCIE certifications, a CCDE, CISSP, and extensive industry experience. He creates practical tutorials that turn complex networking technologies into clear, real-world solutions.