Backup and ETS project handover that actually survives

A KNX project's most valuable asset is not the wires or the actuators. It is the .knxproj file in ETS6 that holds the configuration of every device. Lose it and even a small change becomes a re-engineering job.

A backup discipline that has worked across hundreds of projects: at the end of every commissioning session, export the project to a versioned filename (like building-name-2026-05-09-evening.knxproj). Save it to three places: the engineer's laptop, the company shared drive, and an offline copy held by the customer. If any one of those three storage places fails, the others still have the project.

Version every export. Avoid overwriting. Disk space is cheap and history is priceless. When something goes wrong six months from now, the ability to roll back to a known-working snapshot saves hours.

The handover pack to the customer should include four documents in a single folder: the .knxproj file (encrypted with a password the customer holds), a printed group address sheet (PDF), a one-page network diagram, and a one-page user guide for the visualization. Hand this folder to the customer in person and confirm they have stored it somewhere they will remember.

Passwords belong in a separate place. Many engineers tape the visualization admin password to the back of the cabinet door. Stop. Use a password manager entry shared with the customer's IT contact. The cabinet door is the worst possible place for any credential.

Finally, ask the customer to send you a copy of any change they make to the project after handover. Most customers do not change KNX after handover, but the few who do (typically by hiring a different engineer for an extension) need to give you the updated file so the next service call has the right starting point.