collabcowboy.net
Inter-cluster phone migration with rollback for Cisco CUCM
📦 Cluster Bustera Collab Cowboy tool
Move phones between clusters with their lines, forwards, and users intact, and a rollback.
CUCM has no native way to move phones between clusters, so a consolidation or a migrate-to-15 becomes a multi-day manual slog with no undo. Cluster Buster migrates phones between CUCM clusters and brings everything with them: lines, DN settings, forwards, ILS, user associations, speed dials, and BLFs. It runs as a four-phase atomic migration with a per-step journal and automatic rollback on failure.
Select phones on the source, pick the destination, and Cluster Buster migrates in four journaled phases with auto-rollback if anything fails and crash recovery if the run is interrupted. It groups shared lines transitively, watches registration live, preps encrypted-phone ITL, and offers a finalize or inverse-migration path.
Inter-cluster migration · journaled● migrating
Cluster-A → Cluster-B · 68 phones · config preserved
| Device | DN | Carried over | State |
|---|
| SEP0011A4 | 4021 | lines · fwd · user · BLF | migrated |
| SEP0022B7 | 4022 | lines · fwd · user · BLF | migrated |
| SEP0033C1 | 4023 | lines · fwd · user · BLF | phase 3/4 |
| SEP0044D9 | 4024 | lines · fwd · user · BLF | queued |
Phase 1 Prepare ✓ · 2 Copy ✓ · 3 Register ● · 4 FinalizeConflicts: 0 · rollback armed
The Migration
Everything moves, atomically
Pick the phones and the destination cluster and Cluster Buster moves them with their full configuration intact. It runs in four atomic phases with a per-step journal, so the migration either completes cleanly or rolls itself back.
- Full config: lines, DN settings, forwards, ILS, users, speed dials, BLFs
- Four-phase atomic: journaled steps, not a fire-and-forget script
- Auto-rollback: a failure reverses the run instead of leaving a mess
- Conflict detection: collisions surfaced and resolved before commit
Safety & Recovery
Built for the run that goes wrong
Migrations get interrupted: a link drops, a box reboots. Cluster Buster survives it: a run recovers mid-flight, shared lines move as a group, encrypted phones get their ITL prepped, and registration is watched live so you see phones land on the new cluster.
- Crash recovery: resume a run interrupted mid-migration
- Transitive shared lines: grouped so they move together, intact
- Encrypted-phone prep: ITL handling for secure phones
- Finalize / inverse: commit the move, or migrate back
Why teams reach for it
The one job CUCM gives you no tool for.
There is no native tool for this. Inter-cluster migration is normally a manual, error-prone, no-rollback slog. Cluster Buster makes it a selection and a run.
Config comes along. Lines, forwards, users, speed dials, and BLFs migrate with the phone, so you’re not rebuilding devices on the far side.
Rollback is the default. A four-phase journaled migration reverses itself on failure instead of stranding you half-moved.
Interruptions aren’t fatal. Crash recovery resumes a run that got cut off, re-checking each phone rather than starting over.
Shared lines stay whole. Transitive grouping moves a shared-line set together, so you don’t split a line across clusters.
Secure phones handled. ITL prep means encrypted phones migrate too, not just the easy ones.
Consolidations, M&A, and migrate-to-15
Merging environments, collapsing datacenters, or standing up a new 15 cluster and moving onto it: all of it comes down to relocating phones without losing their config or your weekend. Cluster Buster does the operational half of that with rollback, so a cluster move can happen over lunch instead of over a change-freeze.
Setup & Fit
Works with
Two or more on-prem Cisco CUCM clusters you’ve connected.
Turn it on
Connect source and destination; select phones and pick the target.
Sized for
Cluster consolidation, M&A, datacenter moves, migrate-to-new-cluster projects.