How to Migrate Phones Between CUCM Clusters

CUCM has no native way to move phones between clusters, so a consolidation or a migrate-to-15 usually becomes a multi-day manual slog with no undo. Here is the manual reality and a safer way.

The manual way

• Export the phone and line detail from the source cluster.
• Recreate device pools, CSSs, partitions, and templates on the target so the imports land.
• Rebuild each phone, re-associate users, re-add speed dials and BLFs.
• Repoint and hope nothing was missed, with no clean rollback if it was.

The safer way

Cluster Buster migrates phones between clusters with lines, DN settings, forwards, ILS, user associations, speed dials, and BLFs intact. It runs as a four-phase atomic migration with a per-step journal and automatic rollback on failure, and if a run is interrupted it resumes where it stopped.

Runs on your server, talks directly to both clusters. No middleware.

Frequently Asked Questions

Can you move phones between CUCM clusters?

Not natively in one step. You export and rebuild, or use a migration tool that carries lines, forwards, BLFs, and user associations across with automatic rollback.

How do you migrate phones to a new CUCM cluster?

Recreate the dependencies on the target, then move each phone’s configuration. A tool like Cluster Buster automates this as a four-phase migration that resumes if interrupted.