UniFi - Backups and Migration

This is used when all devices are on the same Layer 2 network (i.e., all devices are on the same network/VLAN as the management application’s console device). 

Note: If you are a home user managing devices in a single location and have not used the set-inform command or other advanced Layer 3 adoption methods, this is most likely the method for you.

1. Download the desired backup file (*.unf) from your original Network application’s System Settings. 
2. Ensure that your new Network application is up to date. Backups cannot be used to restore older application versions.
3. Replace your old UniFi Console with the new one. All other network connections should remain unchanged.
4. Restore the backup file in the Network application’s System Settings.
5. Ensure that all devices appear as online in the new application. If they do not, you can try Layer 3 adoption, or factory-reset and readopt your device(s) to the new Network application.

If a device appears as Managed by Other, click on it to open its properties panel, then use its Device Authentication Credentials (from the original Network application’s console device) to perform an Advanced Adoption.

This method is for users that have performed Layer 3 device adoption (e.g., devices are on a different network/VLAN than the application’s console device). This may also be useful when migrating to a Network application console that is not also a gateway.

1. Download the desired backup file (*.unf) from your original Network application’s System Settings. 
2. Enable the Override Inform Host field on the original Network application’s console device, then enter the IP address of the new console device. This will tell your devices where they should establish a connection in order to be managed. Once entered, all devices in the old application should appear as Managed by Other.
   • When migrating to a Cloud Console, you can copy the Inform URL from the Cloud Console’s dashboard. You will need to remove the initial http:// and the ending :8080/inform. 
3. Ensure that your new Network application is up to date. Backups cannot be used to restore older application versions.
4. Restore the backup file in the Network application’s System Settings.
5. Ensure that all devices appear as online in the new application. If they do not, you can try Layer 3 adoption, or factory reset and readopt your device(s) to the new application.

If a device appears as Managed by Other, click on it to open its properties panel, then use its Device Authentication Credentials (from the original Network application’s console) to perform an Advanced Adoption.

Certain Network application consoles (e.g., Cloud Key, Cloud Console, self-hosted Network Server) can manage multiple sites. Site exportation allows you to migrate specific sites from one multi-site console to another. To do so:

1. Click Export Site in your Network application’s System Settings to begin the guided walkthrough.
2. Select the device(s) you wish to migrate to your new Network application.
3. Enter the Inform URL of your new console. This will tell your devices where they should establish a connection in order to be managed. Once entered, all devices in the old application should appear as Managed by Other in the new one.
   • When migrating to a Cloud Console, you can copy the Inform URL from the Cloud Console’s dashboard. You will need to remove the initial http:// and the ending :8080/inform.
4. Go to your new Network application and select Import Site from the site switcher located in the upper-left corner of your dashboard.
   • Note: You may need to enable Multi-Site Management in your System Settings.
5. Ensure that all devices appear as online in the new application. If they do not, you try Layer 3 adoption, or factory reset and readopt your device(s) to the new application.

If a device appears as Managed by Other, click on it to open its properties panel, then use its Device Authentication Credentials (from the original Network application’s console) to perform an Advanced Adoption.

1. Download the desired backup file (*.zip) from the original Protect application’s settings. 
2. Ensure that your new Protect application is up to date. Backups cannot be used to restore older application firmware.
3. Replace your old UniFi Console with the new one. All other camera connections should remain unchanged.
4. Restore the backup file in the Protect application’s settings.

Full HDD migration is not officially supported; however, some users have been able to perform successful migrations by ensuring consistent ordering when ejecting and reinstalling drives into their new console to preserve RAID arrays.

Note: This is only possible if both UniFi Consoles are the same model.

1. Remove the HDDs from the old console. Record which bay each one was installed in, but do not install them in the new console yet.
2. Turn on the new console and complete the initial setup wizard. Do not restore a Protect application or Cloud backup during initial setup.
3. Upgrade the new console and its Protect application to a version that is either the same or newer than the original console.
4. Shut down the new console, and then install the HDDs in the same bays as the original console.
5. Turn on the new console again. The Protect application should start with its current configuration intact, and all exported footage should be accessible.