You can set it up from your iPhone. And back up to their cloud service and restore from their cloud service. Those are the happy path. Example: https://www.eddgrant.com/blog/2025/09/10/migrating-unifi-clo... Or: https://www.reddit.com/r/Ubiquiti/comments/1h52ieh/best_way_...

You can do manual shenanigans but it's not recommended. And yes, more like Apple than like, say, Eero, since Apple lets you fiddle inside your Mac. You might be preferring the new Eero PoE Router and Gateway along with a few of the PoE WiFi 6 or 7 slim antennas.

Just need to find a network geek to give your present full time hobby a loving home. Make them pay cash and don't let them know where you live.

I set up a Unifi system in Thailand that has to be downstream (DHCP) from an ISP provided router. Both Unifi and ISP device want 192.168.1.x and want to be the DHCP server and there’s no easy way to tell Unifi that “WAN” is 1 hop away.

I agree with the poster that if you are doing anything that is not a defined happy path for Unifi, it is a freaking nightmare and will likely involve rebuilding, resetting and readopting several times.

Couple items:

- You don't need a cloud key, or any other hardware to use the Unifi APs. You can SSH in or configure with an app on your phone. But you miss out on a lot of the features that make this hardware desirable. I ran a Unifi system for a long time with no controller or cloud key at all.

- I've never needed an internet connection to set up a Unifi system, in fact I typically get the local network setup and working, and configure the WAN as a last step. This provides the convenience of being able to consistently hit the router to debug issues.

- I can see the frustration of not being able to migrate the configuration from cloud key to gateway, but a migration is different from a restore, which is what a back up is intended to provide. In practice, I'd always plan to reconfigure if I'm changing hardware or software in the stack.

Unifi is indeed very Apple like (founded by ex-apple engineer I believe?) in both good and bad ways. I think their goldilocks deployment is large home / small businesses that need remote administration.

I was honestly pretty pleased with my unifi equipment. There was an issue setting up via Bluetooth / Android, but I am 99% certain that's an android thing since I had the same problem with other branded devices.

Setting up via a laptop with an Ethernet port was smooth sailing though.

I sympathize with the poster, as deploying my own stack should've been an easier migration from their EdgeRouter kit than it turned out to be - though wisely, I had budgeted a six hour window for a process that ultimately took ~2hrs.

Ubiquiti's niche really is the "I want Enterprise features but I also don't want to be my own CCIE to run this shit," and in that sense it overachieves nicely. Does it have idiosyncrasies? You betcha, and OP found this out first hand. Would I trust this for blind/hands-off remote site deployment? Hell naw, that's what Meraki is for. Would I build a data center around these? Maybe, depending on the data center's function?

Honestly, my wishlist for the product suite is a stronger focus on self-hosting, removing the Bluetooth app requirement for initial setup of hardware, improving zero touch provisioning, and letting me use Identity without having to tie it to their servers (e.g., local LDAP or SAML/SSO integration). That'd make me a happy dinosaur.