Some large houses in northern Bergen County run a Savant or Control4 system that was installed by a dealer who has since closed, moved on, or simply stopped answering the phone. The house still turns its lights on. The keypads still work, mostly. But nobody can get into the programming, nobody knows the administrator login, and the last person who touched the rack does not return calls. That is a different problem from choosing a platform for a new build, and it deserves its own plan.
What actually happens during the walkthrough
Before anyone talks about staying on the existing platform or moving to something else, the system has to be documented. An integrator taking over a house they did not build needs to understand the layout of the home and the system: catalog every piece of hardware in place, photograph the front and back of every rack connection, trace the wiring infrastructure room by room, and map how control is actually being exercised — IR, IP, relay, or serial. According to 5 System Design Criteria for a Successful Takeover, this initial walkthrough is also described as the one chance to be in the home, and it should include using the system with the homeowner present, watching how they actually turn on the TV or call up a lighting scene, because the way a family uses a system and the way it was designed to be used often drift apart over the years. Any existing documentation — user manuals, programming code, CAD drawings, wiring diagrams, and hardware model numbers — should be pulled together at the same time, since it can fill in gaps the walkthrough alone will not catch.
That inventory step matters more in an orphaned-dealer scenario than in a normal service call, because there is no one left to ask. Whatever gets missed on the one site visit either gets guessed at later or turns into a change order once demolition starts.
Which layers are actually reusable
Not everything in the walls needs to be replaced, and figuring out what survives is a large part of what makes a phased takeover affordable rather than a full gut. On the Crestron side specifically, migrating from an older wired topology does not automatically mean pulling cable. Crestron's own Home OS documentation describes moving existing Cresnet-wired devices onto an Ethernet-to-Cresnet bridge as a supported migration path: the physical Cresnet connection is moved to the bridge, the Crestron Home Setup app scans and reidentifies the devices, and a Deploy Code transfers the system data over. The documentation is specific about sequencing here — see Migrate Cresnet Wired Devices to an Ethernet-to-Cresnet Bridge — the physical connection has to move before the data migration runs, because if a device does not support the Replace Device function it has to be re-added from scratch and whatever programming was attached to it is lost.
That kind of documented migration path is what makes a "reuse the wiring" conversation credible rather than aspirational. It is also why the stay-or-switch decision should not be answered in the first site visit: whether the existing low-voltage wiring, speaker runs, keypad locations, and network drops in a given house are worth keeping depends on what is actually behind the wall plates, not just what platform badge is on the rack. If you are inheriting a system like this, ask your integrator to separate the conversation into two questions — what wiring and infrastructure survive regardless of platform, and what control-layer decisions (processor, programming, user interface) depend on staying with Savant or Control4 versus moving to Crestron or Lutron. If staying with the existing platform is on the table, put the dealer-support question to the manufacturer directly rather than assuming an answer either way: can a new dealer be assigned to service this account and its software licenses, and what does that process actually involve? That answer should drive the stay decision more than a general impression of the brand.
Why the swap has to be phased, not flipped
A large occupied house does not tolerate losing lighting, shades, music, and video all at once while a new system gets commissioned. Crestron's documentation on transferring system data between processors — see Migrate System Data to a Different Processor — notes that data can be transferred as a means of moving system data from a test system to a live system or to replace a processor. That points to the practical sequence a takeover project should follow: build and validate the new configuration on a bench or in a non-critical zone first, then cut over room by room or subsystem by subsystem, rather than pulling the existing processor and hoping the new one comes up clean the same night.
For a homeowner, that translates into a few concrete questions worth putting to whichever integrator does the survey:
- Which rooms or subsystems can move first without leaving the rest of the house dark, and in what order?
- What existing wiring and keypad locations does the proposal actually reuse, versus assume will be repulled?
- If staying on the current platform, what does the manufacturer say about assigning a new dealer of record for this account, and is there a documented support path for the specific processor generation installed?
- What does the transition plan look like for the week between old system decommission and new system full commissioning?
A decision, not a default
There is no single right answer for whether an orphaned Savant or Control4 install should be revived under a new dealer or replaced outright with Crestron or Lutron. The right call depends on the age and condition of the processor, how much of the wiring plan survives inspection, and how much the household depends on features that only the current platform provides. What is consistent across takeovers of this size is that the process starts with a full survey and a design review before any hardware decision gets made, and that the swap itself gets staged so the house keeps functioning while it happens.
Cave Group works on estate-scale technology takeovers throughout northern Bergen County, and surveys existing Crestron, Lutron, and Savant systems as a first step before recommending a path forward. If you're facing this in Alpine, Saddle River, Franklin Lakes, or a neighboring town, the Bergen County estate page covers how new construction, renovations, and takeovers of existing systems get handled locally, and the residential page has more on whole-home control and lighting design generally.