Tell us your current Unity version + target version + mailbox count — get a phased migration plan with pre-upgrade checks, cutover playbook, and rollback criteria.
Unity Connection upgrades follow Cisco's supported paths — you can't jump from 10.x to 15 in one step. This tool determines whether you need a 2-hop upgrade, recommends in-place vs fresh-install, sizes the cutover window, and emits a 4-phase plan (Prep → Upgrade → Cutover → Post) with specific commands at each step.
Fill in your versions, click Generate migration plan.
Pre-checks, backups, sandbox upgrade, rehearsal.
L2 upgrade or fresh install + data migration.
CUCM integration swap + MWI verification.
Daily checks, rollback criteria, project closeout.
The biggest time sink is mailbox data: a 1,000-mailbox cluster with 30-day retention can hold 200–400 GB of WAV files. L2 upgrades preserve data in place but take longer. Fresh installs require COBRAS (Consolidated Object Backup and Restore Application Suite) — a free Cisco tool that exports subscribers, greetings, and messages from source, imports to destination. COBRAS runs in the background during the cutover window; on large clusters it's the critical-path item.
CUCM integration survives most upgrades, but check carefully after the upgrade: the SIP trunk security profile format changed in 12.5 (stricter TLS ciphers), so a trunk that worked on 11.5 may fail on 14/15. Before the upgrade, make sure CUCM is on a version that supports the same SIP profile format as the target Unity.
MWI is where most cutovers visibly fail. After the upgrade, users press Messages on their phone and voicemail works — but the MWI lamp doesn't toggle. This almost always means Unity's MWI-out messages aren't reaching CUCM. Check the Port Group → Ports → "MWI Requests" checkbox is enabled on at least some ports, and that CUCM's SIP trunk allows inbound SIP NOTIFY. Test by leaving yourself a message from an external line.
If source ≤ 10.5 and target ≥ 14 → yes (hop via 12.5). If source ≤ 11.5 and target = 15 → yes. Otherwise no.
In-place for 11.5+ → newer, fresh + COBRAS for 10.x → 14/15, and for any case where the source OS is EoL.
Prep: 2–3 weeks. Cutover: 4–6 hours. Post: 1 week. Total elapsed: ~4 weeks.
Yes. Voicemail is unreachable during CUCM integration swap — plan 1–2 hour outage for the swap itself, longer for the upgrade.
2-hop (10.5 → 12.5 → 15), fresh install with COBRAS, single weekend.
1-hop L2 upgrade, PCD-assisted (Prime Collaboration Deployment).
1-hop L2 upgrade, HA pair, rolling upgrade (one server at a time).
Our Upgrade Sprint plans, executes, and verifies your Unity Connection upgrade — sandbox rehearsal + zero-surprise cutover weekend included.