VT Pro retention vs. CH5 migration — a candid breakdown.

Crestron made two generations of touchpanel framework that matter for principal residences. Crestron VT Pro and its graphics framework SmartGraphics shipped on the TPS-class panels — the touchpanels that built the modern luxury Crestron market through roughly 2018–2020. Crestron CH5 (HTML5, CSS, and JavaScript) shipped on the current TSW and TS panels and is where Crestron’s development effort lives today.

The two are different programming environments with different design vocabularies. They aren’t compatible at the panel level — you can’t run a CH5 surface on a TPS panel and you can’t run VT Pro on a TSW panel. So the migration question reduces to one decision: when does the household refresh the panels, and what new design ships when they do?

The retention argument.

Most VT Pro residences we visit don’t need to migrate yet. The panels are stable, the household is comfortable, and the integration logic underneath is doing its job. Refreshing in those conditions is a discretionary expense that disrupts a working residence; deferring it is the architecturally sensible choice.

Panels still in service. Crestron TPS panels were built to commercial-grade durability. The ones we see in residences ten years on are still bright, still responsive, still passing capacitive touch. There’s no quality-of-life argument for replacing them while they’re working — the same way there’s no argument for replacing a working Lutron HomeWorks processor that’s humming along on its third household.

The household has learned the interface. A residence in service for several years has a household that has internalised the panel’s scene language, the keypad behaviours, and the morning rhythm. Replacing the surface forces a new learning curve — small, but real. On a household that values calm above novelty, that learning curve is a cost.

Refresh is invasive. Replacing wall panels means removing the old panel, addressing any bezel work the new panel doesn’t cover, pulling cables if the rough-in is now under-spec, and re-finishing the wall around the new mount. On a fully-finished luxury residence, every panel replacement is a small site visit with the contractor and a painter. Doing it across twelve panels in a large house is a multi-week project that disrupts the household’s rhythm.

Where the household values the residence’s working state above the design opportunity of a refresh, retention is right. We maintain Rubicon — our hand-composed VT Pro UI — specifically to refine these residences in place. The same design discipline that produces Tahoe on a CH5 panel produces Rubicon on a TPS panel; the household gets a properly composed interface without the disruption of a panel refresh.

The migration argument.

There are residences where migration is the right answer, and being honest about which side of the line a project sits on is the difference between an engagement that serves the household and one that defers a decision the household will eventually be made to face.

CH5 unlocks design possibilities VT Pro can’t reach. CSS transitions, JavaScript-driven motion, modern typography rendering, high-density display panels. The visible difference on a side-by-side comparison is significant — not in what the system does, but in how it reads. Households on the design end of the spectrum (architects living in their own residences, principals where the firm is composing a design-led brief) tend to see the CH5 difference and want it.

Crestron’s roadmap. Crestron has shipped no major VT Pro framework updates in years; the active development effort lives in CH5. Panels are supported and parts are available, but new capabilities — voice integration improvements, new Crestron service modules, third-party SDK improvements — ship on CH5 first and rarely come back to VT Pro. Over a ten-year residence horizon, the gap widens.

The panels are aging. A TPS panel installed in 2014 has been in service for over a decade. Capacitive touch ages; backlights age; the panel housing yellows at the edges where sunlight reaches it. At some point each panel reaches a serviceability cliff where the right answer is replacement rather than repair. Across a residence with a dozen panels, those cliffs arrive at different times; migrating proactively lets the household plan the refresh as a single event rather than absorbing it as a string of small failures.

The design partner is asking. On residences where an interior designer or architect is composing a refresh of the residence anyway — new finishes, new joinery, a kitchen renovation, an addition — the right moment for a panel refresh is the moment the rest of the residence is open for design. Tying the panel refresh to the larger project reduces the disruption to a level the household is already absorbing for other reasons.

When migration is forced.

Two scenarios force migration rather than invite it. Both are worth recognising early.

Panel failure beyond repair. A TPS panel that fails — backlight gone, capacitive touch unresponsive, controller board failed — can sometimes be repaired and sometimes can’t. Crestron still services older panels but the inventory is finite and the labour cost is real. At some point on the cost curve, the right answer for the failed panel is replacement rather than repair. Once one panel has been replaced with a CH5 unit, the residence is on a mixed-generation footing — some panels CH5, some VT Pro — and the design surface is split. Most households eventually choose to bring the rest forward to match.

Major system refresh. Some kinds of system work simply don’t roll forward through VT Pro cleanly. New voice surfaces. New Apple-ecosystem integrations. New third-party services that ship CH5 modules only. A residence whose brief now includes one of these is, in practice, migrating to CH5 whether or not the formal decision has been made; we’ll often recommend the household acknowledge it explicitly and plan for a coordinated refresh rather than absorbing it as drift.

The planned-event approach.

When migration is the right answer, the operational question is how to deliver it. Two approaches; we recommend the second.

Drip migration. Replace panels as they fail or as opportunity arises — one this year, two next year, three the year after. Spreads the cost; lengthens the disruption; produces an interim period (often years long) where the residence is on a mixed-generation interface. We see this on residences that came to us mid-migration after an inherited project lapsed; the household has been living with the mixed state for years and has come to accept it as permanent.

Planned-event refresh. Schedule the panel refresh as a single coordinated event — a long weekend, two weeks at most. The new panels arrive on site pre-loaded with Tahoe in the design language that was composed for the residence. The old panels come out; the new panels go in; commissioning happens with the household present and walks through how the new surface differs. The residence comes out of the weekend with a refreshed interface and one design vocabulary across every panel in the house.

The planned-event approach demands that the design work be done up front — the new Tahoe surface composed against the residence’s existing scene library, typography, palette, and household rhythm so the new panels feel like a refinement rather than a replacement. The composition work is the slow part; the panel swap is the fast part.

How Intuitiv handles the transition.

On Rubicon residences in our care that elect to migrate, the design carries forward. The scene library that lived on the VT Pro panel becomes the scene library on the CH5 panel; the typography selections, the palette, the vocabulary the household has internalised all come across. The household doesn’t learn a new interface; they receive a refined version of the one they already use.

The technical work is mostly invisible: the underlying Crestron programme (the scene engine, the device drivers, the integration logic) doesn’t change. Only the surface changes. The household’s “Master bedroom evening” scene continues to do what it did. The new surface looks different at three inches and identical in behaviour. That’s the design goal.

Where it’s warranted, we add CH5-specific capabilities to the surface — motion that VT Pro couldn’t render, typography that wasn’t possible on the older panel, scene compositions that read better on a higher-density display. The household notices these as small refinements rather than as a wholesale change.

Closing.

VT Pro is not deprecated. It is, in many residences, the right answer for the next decade. CH5 is not mandatory. It is, in some residences, the right answer for the next decade. The decision between them is operational, not technical — what the household is ready for, what the residence is asking for, what the capital plan can absorb. Either answer can be the right one; the wrong move is deferring the conversation.

If you’re weighing this decision on a current residence, we’re glad to read the existing system and write a candid recommendation. Most engagements that start that way settle into something longer; the work this firm does is operating the surface of a residence over the life of the system, regardless of which technology generation it lives on.