Move customers to another UHost server
Two UHost servers can hand customers over between them. The server being left issues a pairing code; the new one pastes it in and shows you what would come across before anything moves.
What this is for
Between two UHost servers, not from another panel.
This is how you move customers to another UHost server — a bigger machine, a different region, a second server as you grow. Leaving a different control panel is a separate job with its own guide: moving a website over SSH. Here both ends are UHost, which is what makes the handover safe to automate.
On the server being left
Issue a pairing code.
Use Issue a pairing code, tick the customers it covers, and confirm with your password — the panel asks again, because this grants another machine the right to read those accounts. Then copy the pairing code now: like any other secret here, it is shown once.
The code is narrow by design. It lets another UHost server read the customers you name, and nobody else. It works once. And it only works for a server that finds this one presenting its own certificate, so a code intercepted on its way somewhere else reaches nothing.
On the new server
Paste it, and read the preview.
Paste the code on the new server and it fetches a manifest describing what would come across. The preview changes nothing, and it says what would stop the move — a domain already in use, something the new server cannot accommodate — before you have committed to anything.
The manifest describes and carries nothing that signs in anywhere: no passwords, no keys, no session. It is a description of work to be done, not the work itself.
The move
A website at a time, and then compared.
Starting the move records a migration per website and copies each one: the website is made, its files arrive and are swapped into place the way a restored backup is, each database is made and loaded, and the settings that live on the machine are applied. Both servers then take an inventory and compare them, so "it finished" means the two ends agree rather than that no error was printed.
Switching the traffic
A fresh code, because the authority is granted as it is used.
Where UHost holds the domain's DNS, the switch-over is a separate step and it asks for a fresh pairing code from the old server. That is not an oversight: the authority to repoint a customer's records is granted at the moment it is used, not borrowed from a code issued earlier in the day.
Lower the record lifetimes first and the switch is a short read-only window, measured and shown to you beforehand rather than discovered afterwards. It can also be undone, which is the other reason the traffic moves separately from the data.