UniFi Adoption, Migration and Closeout Runbook
UniFi equipment may be reachable on the network yet remain tied to another console, wait for adoption, or receive configuration that does not match the site. TechRunz verifies console ownership, backup and migration method, Layer 2 or Layer 3 adoption requirements and the final operational handoff before devices are reset or moved.
Make each dispatch repeatable and recoverable
Define prerequisites, remote ownership, method of procedure, acceptance evidence and rollback before technicians arrive onsite.
Ownership, backup and adoption planning
Identify the existing console, destination console, owner account, site, Network application version and installed device models. Verify that the client has authorized access before resetting, removing or transferring equipment. A reset without source ownership or a current backup can turn a routine migration into a rebuild.
Create and protect the appropriate backup or use the current supported migration process. Record VLANs, networks, SSIDs, authentication, switch profiles, static addresses, VPNs, port forwards, identity dependencies and third-party services. Confirm version compatibility before restoring data to a different console.
The remote team should supply the site identifier, approved design, equipment list, configuration status, contacts, access window and success criteria. The field technician verifies serials, labels, damage, accessories and prerequisites before changing production service.
- Authorized source and destination
- Current protected backup
- Version and migration compatibility
- Adoption network prerequisites
Device installation, adoption and migration
Map each gateway, switch and access point serial to its location, uplink, switch port and power source. Confirm Layer 2 discovery or the approved Layer 3 adoption path, required DNS/DHCP behavior and firewall reachability before dispatch.
Install and adopt devices in a controlled sequence that preserves management. Wait for provisioning and reboots to finish, and watch for adoption loops, duplicate IP addresses, isolated devices or unexpected factory defaults. Do not repeatedly reset a device before the remote owner reviews its actual state.
Use a written method of procedure with hold points for configuration-sensitive actions. Photograph and label the before state, preserve known-good cabling or configuration, and keep a practical rollback path. Record deviations as they occur instead of reconstructing them after the visit.
- Serial and physical mapping
- Controlled adoption sequence
- Provisioning and reboot hold points
- Remote escalation before reset
| Area | Acceptance check | Evidence |
|---|---|---|
| Ownership | Correct console, site and administrators | Console inventory |
| Adoption | Connected, provisioned and correctly named | Device status record |
| Service | Gateway, switching, Wi-Fi and applications | Representative tests |
| Recovery | Backup, update policy and rollback ownership | Protected handoff record |
Network, wireless and recovery validation
Validate gateway addressing, internet, routes, VLANs, DHCP, DNS, NAT, VPN and required inbound services. Check switch trunks, native VLANs, profiles, spanning tree, negotiated links and PoE. Test every required SSID with representative clients for authentication, addressing and applications.
Exercise the approved gateway, uplink or power recovery scenario when redundancy is part of the design. Confirm that all devices return to connected state and that alerts, topology and client history are useful. Apply updates only under the approved policy after release-note and backup review.
Validation must cover physical status, management visibility, addressing, uplinks, power, policies and representative user traffic. When redundancy is expected, test the approved failure and restoration scenarios. Escalations should include timestamps, identifiers and reproducible evidence.
- Gateway, VLAN and DNS tests
- Trunk, profile and PoE checks
- SSID and representative clients
- Approved recovery scenarios
Closeout, access and lifecycle ownership
Reconcile console inventory, names, sites, firmware, switch ports, AP positions and client networks with the field worksheet. Record offline or pending devices, temporary profiles, failed updates and any hardware that remains owned by a prior console.
Transfer ownership to named client administrators, enable strong account protection and document backup, update and alert responsibilities. Store recovery material and credentials in the client repository. The public project record should contain official help links, not exported backups or controller secrets.
Closeout combines annotated photographs, serials, port and cable records, software versions, test output, exceptions and ownership. Credentials and private configurations belong in the client-controlled repository, while public pages should point only to official manufacturer support resources.
- Console and field reconciliation
- Offline and temporary conditions
- Protected access and backups
- Named update and alert ownership
How we plan and deliver the work
The final design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Prepare
Confirm access, equipment, remote readiness and rollback.
Execute
Install through the approved method and document deviations.
Test
Validate management, service, resilience and user workflows.
Close
Deliver evidence, inventory, exceptions and support ownership.
Information to gather before design
Good decisions are easier when the project team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.
- Site access and remote contacts
- Staging, inventory and prerequisites
- Method, maintenance window and rollback
- Acceptance tests and escalation
- Evidence and operational ownership
Frequently asked questions
These are common planning questions. A site-specific answer should be confirmed during discovery and design.
Should a UniFi device be factory-reset when adoption fails?
Only after verifying ownership, network reachability, inform state and recovery. An unnecessary reset can erase useful configuration or complicate migration.
Can a backup from any Network application version be restored?
Compatibility varies. Review the current Ubiquiti migration guidance and test the supported path before the maintenance window.
What causes Layer 3 adoption problems?
Routing, DNS or DHCP options, inform settings, firewalls, NAT, prior ownership and version compatibility are common factors.
What is required at closeout?
Correct ownership, complete inventory, network and client tests, backup and update policy, exceptions, recovery information and named administrators.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Build a repeatable field-deployment plan
Provide the site list, target schedule, equipment responsibility, change-window constraints and acceptance criteria. We will help turn them into a practical rollout and closeout workflow.