Put UniFi into service with a clear handoff.

Review the existing system first

For a new site, we match the gateway, switching and wireless equipment to the applications and layout. For an existing deployment, we establish what is currently managed, which account has access and what must remain working.

• Hardware models and installed software versions.
• Internet settings, networks, switch ports and Wi-Fi names.
• Existing backups and the intended management platform.
• PoE, optics, cabling and installation dependencies.

Hardware and platform compatibility are checked against the intended migration method rather than assumed from the UniFi name alone.

Keep the move deliberate

The supported backup and migration path depends on the current host and destination. We plan configuration preservation, device management and a service-interruption window before moving equipment.

Configuration backups are not a copy of every kind of data. For example, Ubiquiti states that existing Protect recordings do not transfer between consoles through configuration migration. Retained video needs its own plan when that system is involved.

A customer representative or IT provider should be available for application checks and decisions at the agreed cutover time.

Make ownership explicit

The customer should retain the appropriate ownership or administrator role, recovery method and access to backups. FryAVSI access is assigned according to the support arrangement.

At closeout, confirm adopted devices, network access, representative Wi-Fi clients and the actual business applications in scope. The project record identifies remaining issues and who manages future updates.