# Moving to UniFi OS Server With Us

> Existing customers on the classic Network Application can move to UniFi OS Server from the customer portal. We build the new console, restore your data into it, keep your existing address working, and watch the devices reconnect. This page walks through the portal steps and what to expect.

If you are new to UniFi OS Server, read [How to migrate a UniFi Network Application to UniFi OS Server](../Unifi/migrate-unifi-network-application-to-unifi-os-server.md) first. It explains why devices need to be told about the new address, which is the part we handle for you.

## Before you start

- **Choose the owner.** The console owner must be one of your existing super admins. If that admin is linked to a Ubiquiti account, you keep single sign-on, Remote Access and the mobile app. If it is a local-only admin, the new console will be local-only until it is linked, and the portal warns you about this.
- **Note your custom domains.** If devices or people use your own domain name, the portal tells you a DNS change is needed after the move. See [Using your own domain](../Unifi/custom-domain.md).
- **Update device firmware first.** Very old firmware can misbehave when a controller changes address. Update devices before the move, not after something breaks.

## The portal steps

1. Sign in to the [customer portal](https://portal.cloudunifi.com), open your service and click **Upgrade to UniFi OS Platform**.
2. The portal shows **your new hostname**, ending in `.netconsole.cloud`. Copy it; you will use it in the console address and, if you have one, in your custom domain's CNAME record.
3. The portal **verifies your current controller**. This takes up to five minutes.
4. **Choose the owner** from your super admins. If the admin you pick is not linked to a Ubiquiti account, you can choose a different admin or continue with a local-only owner.
5. **Review** what happens: your configuration and devices are migrated, your new console is hosted at the new address, devices reconnect automatically, and user accounts are carried across with their passwords.
6. **Accept the terms**: our terms of service, and an acknowledgement that you are the end user of Ubiquiti's software.
7. Start the migration.

## What happens next

- We provision the console and restore your controller into it. Your existing `.cloudunifi.com` address is pointed at the new console, so devices reconnect without any change on your side.
- For a short period the old controller and the new console both exist while devices re-home. Once the new console is confirmed, the old one is retired.
- Typical elapsed time is under an hour for a normal site. Devices reconnect on their own schedule, usually within minutes.

!!!warning Do not run the setup wizard yourself
If you open the new address before we tell you the console is ready, you may see the UniFi OS setup wizard. Do not complete it. Completing the wizard creates an empty console and can strand the restore. Wait for our confirmation, then sign in with your existing credentials.
!!!

## Afterwards

- **Sign in** at the new address with the same username and password as before. See [Signing in](signing-in.md).
- **Check the device count** in the Network application against what you had before. Devices that were already offline before the move stay offline. If anything that was online is missing after an hour, see [Devices offline after moving](troubleshooting-devices.md).
- **Custom domain:** the portal guides you through updating your CNAME record to the new hostname once the console is ready.
- **Remote Access** and captive-portal sign-in providers need to be enabled again if you used them. See [Remote Access](remote-access.md).
- **Updates** now arrive on Ubiquiti's schedule rather than ours. See [Updates on UniFi OS Server](updates.md).