Important: Deadline: April 30, 2026
Cisco is retiring the legacy V1 Control Hub integration on April 30, 2026. This article walks you through what’s changing, why it matters, and how to complete your migration before the deadline.
What’s new in V2
| Feature | V1 (legacy) | V2 (new) |
|---|---|---|
| Connection stability | Standard | Enhanced, more robust |
| Navigator support | Limited | Full (Paired & Standalone) |
| Admin authentication | Standard cross launch | Improved per-user cross launch |
| Deprecation status | Retiring April 30, 2026 | Active & supported |
What happens to your existing content
The migration is designed to be low-disruption. Here’s what to expect:
- Content, device settings, and licenses transfer automatically — no need to rebuild playlists from scratch.
- A quick post-migration audit is recommended — in rare cases, some content may need to be republished to ensure uninterrupted playback.
How to migrate
- Review the step-by-step migration guide (link below).
- Start with a small set of test devices to familiarize yourself with the V2 interface.
- Migrate the remainder of your device fleet.
- Audit your screens post-migration and republish any content that isn’t playing back correctly.
Pro tip: Transitioning a few test devices first is a great way to get comfortable with the V2 interface before migrating your full fleet.
Ready to migrate?
Follow the complete instructions in Migrate Your Cisco Control Hub Integration: A Guide to the Cutover from V1 to V2. With the April 30th deadline just days away, now is the time to complete your migration and address any edge cases before the cutoff.
Friendly Check-in: Cisco V1 Migration