Stage 3 — Parallel operation

Goal: Run the old system and the new one simultaneously, migrating one zone at a time, while the house keeps working the entire time.

This is where most of the calendar goes, and that’s exactly right. The hard part is proven; now it’s a matter of moving the house over carefully, one zone at a time, with the old system standing behind you as a safety net the whole way. Nothing here is irreversible yet. That’s the entire point of the stage.

The mindset shift: you are not “building the new system.” You are migrating zones, one at a time, each one fully landed before the next begins. Slow is smooth, and smooth is fast.

Run both systems without a fight

The old and new systems share physical reality — the same devices, the same wiring, the same amplifiers. Left unmanaged, they’ll step on each other: both trying to control the same device, fighting over inputs, contradicting each other’s state.

Keep them out of each other’s way:

• Divide control cleanly. A given zone is owned by one system at a time — old or new, never both. The boundary is per-zone, and it’s explicit.
• Be careful with shared infrastructure. Where both systems route through the same matrix, amplifier, or splitter, changes on the new side can disturb a zone the old side still owns. Know your shared chokepoints (you mapped them in discovery) and respect them.
• Don’t let the new system issue commands to zones it doesn’t own yet. Scope it deliberately. The new system controlling a zone “just to test” while the household is using it via the old system is how you manufacture a disruption.

Migrate one zone at a time — and pick the first one well

The order matters. Your first zone is where you’ll make your beginner mistakes, so choose it for forgiveness, not importance:

• Start with a low-stakes zone. A spare room, a workshop, somewhere the household barely touches. Not the living room. Your first migration will be rough, and you want the roughness to happen where no one’s watching.
• Pick a zone that exercises your patterns without being your hardest case. You want to establish the repeatable rhythm — wake, route, control, fall back — on something representative but gentle.
• Then let difficulty climb gradually. Each zone teaches you something the next one needs. By the time you reach the high-stakes rooms, the patterns are proven and your mistakes are behind you.

Land each zone completely before starting the next. A house full of half-migrated zones is harder to reason about, harder to roll back, and far more likely to produce a disruption than a house with one zone in flight and the rest stable.

Keep a same-day rollback for every change

This is the rule that makes the whole stage safe: every change you make must be reversible the same day, ideally in minutes.

• Before you move a zone, know exactly how to move it back — and confirm that path actually works.
• Often the rollback is physical or near-physical: re-point control of the zone to the old system, which is still wired and still running.
• If you can’t articulate the rollback, you’re not ready to make the change. “I’ll figure out how to undo it if I need to” is not a plan; it’s the setup for a bad evening.

The old system staying fully live is what makes this possible. Do not be tempted to start dismantling it to “clean up” — its entire job in this stage is to be the floor you can’t fall through.

The household is your acceptance test

A zone is not done when it works for you. It’s done when it works for the people who live there, in the way they actually use it, without them thinking about it.

• Live with each zone before calling it migrated. Use it normally for a stretch — days, not minutes. The rough edges only show up in real use.
• Watch for the small stuff: the source that takes a beat too long to start, the volume that resets, the thing that works when you do it but not when they do it. Professional installs earned their reputation on exactly these details.
• Let the household be the judge. If they haven’t noticed a change — good or bad — the zone is migrated. If they’re working around something, it isn’t, no matter how clean it looks to you.

This is the zero-disruption principle in practice. Every zone that passes the household’s unconscious acceptance test is trust banked. Every zone that fails it is trust spent.

Exit criterion

Every zone runs on the new system, each has been lived with and passed the household’s test, and — the real measure — you would be genuinely comfortable if the old system vanished tomorrow. When that’s true, and only then, you’re ready to actually remove it: cutover and decommission.