Back up and migrate a UniFi gateway

Outcome and scope

Replace a UniFi Cloud Gateway while retaining its supported configuration and returning the site to verified operation. You need the original and replacement devices, administrator access with the necessary backup permissions, an offline copy of the backup, the WAN credentials and a planned outage window. Keep the original hardware and configuration available until the replacement passes acceptance testing.

The main procedure uses a System Config Backup for a Cloud Gateway migration. A self-hosted Network application uses a different Network-only backup path. A configuration backup does not copy camera recordings. Storage migration has its own model-specific procedure and should be planned separately. [1] [2]

Preparation

  1. Record the original gateway model, UniFi OS version, application versions, WAN connection type, port assignments, VLANs, reservations, VPNs and important policies. Label every cable at both ends. Photograph the connection layout for your own maintenance record if helpful.
  2. Check that the replacement supports the applications and functions you use. Identify any change in physical port capabilities, WiFi, PoE or recording storage. A successful configuration restore cannot add a hardware feature absent from the replacement. Map each old cable to its new intended port before the outage.
  3. Prepare supported software on the replacement using an isolated setup connection where practical. Review release notes and update through the documented Control Plane or application controls. Confirm that the destination UniFi OS and each selected application support the source backup version. Update the destination where necessary; do not restore a newer backup into an unsupported older application. Avoid combining this migration with unrelated network redesign or experimental software changes. [1] [3]
  4. On the original console, open Settings, Control Plane and Backups. Create a current backup and download an offline copy. Record the file date and ensure it is accessible from the administrator computer. Keep the backup protected because it contains network configuration. Cloud backup management is tied to the owning UI Account. [1]
  5. Confirm that the WAN details are available independently of the original device. Include PPPoE credentials or static addressing where used. Record the rollback cabling sequence and the point at which you will stop troubleshooting and restore service with the original hardware.

Migration procedure

  1. Begin the agreed maintenance window. Disconnect the original gateway from the production WAN and LAN paths, preserving its configuration. Connect the replacement according to the port map. Do not place both gateways with the same restored LAN address and DHCP role on the production network at once.
  2. Restore the System Config Backup during setup, or through Settings, Control Plane and Backups on the replacement. Choose the relevant applications and settings if a partial restore is appropriate. Wait for restoration and provisioning to finish before making additional changes. [1]
  3. Connect the administrator computer and check the restored LAN address, internet status, clock and application availability. Confirm the actual WAN and LAN port assignments against the replacement's hardware. If the WAN is offline, verify its physical port and provider settings before changing internal networks.
  4. Wait for switches and APs to reconnect, then inspect their adopted state and uplinks. Keep downstream connections unchanged unless the hardware map requires a move. If a device remains offline, inspect its management address, VLAN path and application connectivity. Factory reset is a later recovery option after the supported migration and connectivity checks, because it removes that device's existing settings.
  5. Test every essential service: staff and guest WiFi, DHCP, DNS, printing, private network restrictions, VPN access, failover and hosted applications. For cameras, verify new recording and playback separately from access to historical footage. Save a fresh backup from the replacement after acceptance.

When the source is a Network server

For a self-hosted or older Network-only source, download the Network application backup, commonly a .unf file, and use the supported Network restore workflow on the destination. Record device management credentials and any DNS or inform-host dependencies before moving. Confirm devices appear online on the new host, then shut down the previous Network instance so it does not compete for management. A Cloud Gateway already includes its own Network host; it is not simply adopted into an unrelated controller like an AP. [1]

Recordings and storage

Export footage that must be retained before changing recording hardware. A general configuration restore does not transfer its video archive. Ubiquiti documents separate procedures for moving from a Cloud Gateway to an NVR and for particular NVR replacement or upgrade scenarios, including orderly shutdown and disk handling. Follow the procedure for the exact source and destination; do not move or initialise disks based only on this networking chapter. [2]

Troubleshooting and rollback

If the restored network fails, work through physical port mapping, WAN configuration, LAN addresses, VLAN trunks and application state. If a specific service fails, compare its recorded address and policy before assuming the entire migration is corrupt.

For rollback, disconnect the replacement, restore the original gateway's labelled cabling and confirm its DHCP, WAN and applications work. Restore another backup only if the original configuration itself was changed. Keep a note of changes made after the migration backup so none are silently lost. Retain the original device until the new installation has passed the agreed operating checks.

Sources

Back to the series

Leave a comment

Please note, comments need to be approved before they are published.