Composer Pro: backing up and restoring a project safely

If you’ve been integrating Control4 for any length of time, you’ll know the feeling: you make a quick change to a customer’s project, save, and something three rooms away stops behaving. Nine times out of ten when one of our team rings the office in a panic, the first question we ask is “have you got a clean backup from before you started?” A good backup discipline is the difference between a five-minute rollback and a very long night re-programming someone’s home.

This is our standard process for backing up and restoring a Composer Pro project safely, written for fellow integrators working on OS 3.4 and newer.

Why you back up before you touch anything

A Composer Pro project (.c4z file) is the entire brain of the home — every room, every driver, every line of programming, every lighting scene and remote button. There is no undo button that survives a save. If you delete a connection or overwrite an agent, the only way back is a previous backup.

Our rule is simple and non-negotiable: take a fresh backup before every site visit and before any structural change. It costs you sixty seconds. Re-creating a complex lighting and AV programme from memory costs you a day and your reputation.

Where backups actually live

It pays to know exactly what is stored where, because the three copies do different jobs.

• On the controller — the live, running project sits on the EA or Core controller itself. This is what the home is using right now. It is not a backup.
• On your laptop — when you connect with Composer Pro and save, a copy lives in your local project directory. By default that’s under Documents\Control4\Projects. This is your working copy.
• In the cloud — with 4Sight active, the project is automatically backed up to Control4’s cloud servers (more on that below).

Treat the local laptop copy as your primary safety net during active work, and the cloud copy as your disaster-recovery net. Never rely on just one.

Taking a manual backup in Composer Pro

This is the bread-and-butter routine before any job.

1. Connect to the system in Composer Pro and let it fully load the project from the controller.
2. Go to File > Save As and save a dated copy to your local backups folder using the naming convention above. This guarantees you have an untouched “before” state.
3. Continue working in the live project. Composer Pro auto-saves to the controller as you go, but the standalone .c4z you just created is frozen in time.
4. When the job is done, do a final File > Save As with a “post-change” label so you have a clean “after” copy too.

Cloud backup with 4Sight

If the customer has an active 4Sight subscription (and we recommend every system we commission has one), Control4 automatically backs the project up to the cloud whenever changes are made and saved. This is genuinely one of the best reasons to keep 4Sight current.

What that gives you:

• Automatic versioned snapshots stored off-site, so even if the controller dies and your laptop is at the office, the project isn’t gone.
• Restore from the customer’s account via the dealer tools, which is a lifesaver when you’re standing in front of a dead controller with no recent local copy.
• Remote programming via Control4 Connect / 4Sight, which also keeps the cloud copy current as you work.

You can check and manage cloud backups through your dealer portal at control4.com under the customer’s account. We still take our own local Save As copies as well — cloud is brilliant, but we like belt and braces.

Restoring to a replacement controller

Controllers do eventually fail — power events, age, the occasional lightning strike out in the eastern suburbs. When you’re swapping an EA or Core controller, the goal is to get the home running exactly as it was. Here’s our process.

1. Get the most recent good project. Pull it from your local backups, or restore it from the 4Sight cloud backup if the controller is unrecoverable and you don’t have a current local copy.
2. Physically install and address the new controller. Rack it, cable it, power it, and identify it on the network. Make sure it’s running a firmware version compatible with the project’s OS (ideally match the OS the project was last saved under).
3. Open the backup project in Composer Pro and connect to the system with the new controller present.
4. Migrate the project to the new controller. In Composer, point the project’s primary controller to the new hardware and load the project onto it. Control4’s identify/move-controller workflow handles transferring the project brain across.
5. Refresh device connections. Re-identify any directly bound devices (IR/serial/contact connections on the controller’s own ports) and confirm Zigbee server status — you may need to re-pair the Zigbee network to the new controller if it was the ZigBee server.
6. Test methodically, room by room. Lighting scenes, AV sources, remotes (Halo/Neeo), touchscreens (T3/T4), schedules and agents. Don’t sign off until every room behaves.

Version hygiene that keeps you out of trouble

Most backup disasters aren’t really backup disasters — they’re version mismatches. A few habits we drill into our team:

• Match the OS. A project saved under OS 3.4 should be opened with a matching Composer Pro version. Opening an older project in a much newer Composer can trigger an upgrade that you can’t easily reverse, so always have your pre-upgrade backup safe first.
• One Composer version per project era. Keep your Composer Pro installs current, but be deliberate about upgrading a customer’s project to a new OS — that’s a planned job, not something you do mid-troubleshoot.
• Date and annotate everything. A folder of project (1).c4z, project (2).c4z is useless in an emergency. Dates and reasons save you.
• Keep a master “as-commissioned” backup for every site, separate from your day-to-day working copies, archived where it won’t get cleaned up.
• Don’t leave your only copy on a laptop. Laptops get stolen, dropped and reformatted. Sync your backups folder to a server or cloud storage.

For more on getting systems ready for changes, our team has written up our advanced programming workflow and a separate piece on getting the most out of 4Sight and remote access. If you’re planning a controller swap on a customer’s behalf and want a hand, get in touch with us.

Our quick checklist

• Backup before every visit and before every structural change.
• Keep three copies: controller (live), laptop (working), cloud (4Sight).
• Name files with surname, OS version, date and reason.
• Match Composer Pro and OS versions before opening old projects.
• Keep an untouched as-commissioned master for every site.

Backups are the least glamorous part of this trade and the one that saves your bacon most often. Get the habit right and a dead controller becomes a routine swap instead of a crisis. If you ever get stuck mid-restore on a Melbourne job, give us a yell — we’ve been there and we’re happy to talk it through.

— Adam and the DUKE team