Contact Center · UCCX

UCCX Upgrade Path Planner

Enter source and target UCCX versions, get the supported hop path, compatibility warnings, CUCM/Unity co-upgrade requirements, downtime estimate, and a rollback plan.

By Faz Karim · 30 yrs Cisco UCLast updated 2026-04-20
What this tool does

Skip versions = corruption

UCCX has specific inter-version upgrade rules — from 10.x you can't jump directly to 15, you must hop through 12.5. From 9.x you can't upgrade at all; you must fresh-install. This tool checks your source and target against Cisco's published upgrade matrix, emits the minimum hop path, flags CUCM/Unity/Finesse version dependencies, and estimates downtime based on database size.

Plan your UCCX upgrade

Inputs

Your upgrade plan

Enter versions, click Generate Upgrade Plan.

How to read your result

Five stages of any UCCX upgrade

1

Pre-check

Backup, compatibility, license migration readiness.

2

Hop path

Sequence of upgrades required to reach target.

3

Cutover

Maintenance window execution steps.

4

Validation

Post-upgrade test calls, report generation.

5

Rollback

If validation fails, snapshot revert path.

Deep dive

The compatibility chessboard

UCCX version must match or be within one major version of CUCM. UCCX 15 requires CUCM 14 or 15 — try to pair UCCX 15 with CUCM 11.5 and CTI integration breaks. The fix: upgrade CUCM first, then UCCX. Never the other way.

Finesse runs inside UCCX, not separately — so no Finesse version to manage independently. But custom Finesse gadgets may rely on JS/HTML APIs that change between UCCX majors. Before UCCX upgrade, test every 3rd-party gadget in the target version's developer sandbox.

DRS backup and restore works across adjacent versions only. You cannot restore a UCCX 10.5 DRS backup to UCCX 15 — that's why hop path matters. Within the hop path, each intermediate version must restore its own DRS backup. Plan storage: an 80-agent UCCX with 40GB DB backup takes ~2 hours to restore at each hop.

FK
Faz Karim30 years Cisco Network · UC · Data Center · LinkedIn
FAQ

Common questions

Can I upgrade from 9.x?

No. 9.x is unsupported for upgrade. Fresh install target version + manually recreate config or use Migration Assistant.

Must I upgrade CUCM first?

Yes if targeting CUCM-newer version. UCCX never upgrades CUCM; they're separate software.

Can I upgrade Publisher and Subscriber in parallel?

No. Publisher first, validate, then Subscriber. Never parallel — risks cluster split-brain.

What's the rollback time if upgrade fails?

~2-3 hours to VM snapshot revert + restore DRS backup.

Worked examples

Three common upgrade paths

10.5 → 15 (most common)

Mid-sized shop, 3 years behind.

2 hops: 10.5 → 12.5 → 15. Requires CUCM also on 15. 16h total.
Biggest upgrade most customers face. Plan two maintenance windows.

11.5 → 14 (near-term)

One version behind current.

2 hops: 11.5 → 12.5 → 14. CUCM must be 12.5+.
Skip 14 and go to 15 if target support is priority.

12.5 → 15 (direct)

Recent upgrade, just chasing support.

Direct hop. 8h. Easiest scenario.
No intermediate hops. Plan accordingly.
Sources verified against current Cisco guidance

Citations

Related tools

You might also need

Haven't upgraded in 3+ years?

Our UC Modernization Sprint runs the full upgrade with rehearsal, cutover, and rollback — in one weekend.

$25K–$75Kturnkey
Book a 30-min call →Or email info@famoustec.com