Bringing a cPanel account in from another host

If your sites currently live on another cPanel host, the whole account can come across as a unit rather than being rebuilt piece by piece. Files, databases, email and settings travel together, which removes the step where something gets forgotten.

What makes this different from rebuilding

Rebuilding means recreating the site here and copying content into it. That works, and it also loses everything nobody thought to mention: the mailbox that receives contact form notifications, the cron job that publishes scheduled posts, the redirect somebody added two years ago for a URL that still gets traffic.

An account transfer carries the whole shape of the account, so the question changes from "what did we forget" to "what needs adjusting".

What you need from the old host

Three things, and none of them is your password to anything of ours:

• The hostname or address of the server the account lives on.
• Credentials for that server, at the level the transfer needs.
• The account username there.

If the old host will not provide access, the fallback is a full backup file from their panel, which you restore here instead. Slower, same destination.

The two failure modes

Transfers fail differently from restores, and knowing which you are doing shortens the diagnosis.

1. A transfer fails at the far end. Connectivity, credentials, or the old server refusing the connection. Nothing on this side is wrong, so checking things here wastes time.
2. A restore fails on content. The backup is older than you assumed, or smaller. Open it before you rely on it, because an uninspected backup is a belief rather than a plan.

Adjustments the transfer cannot make for you

The account arrives intact. What it cannot know is that it is now somewhere else:

• The home directory sits under a different username now, and anything storing a full path from the old server points at nothing: scheduled commands, config entries, compiled template caches.
• Database names and users pick up the new account's prefix, which means the credentials inside the site's own config file no longer match.
• Certificates must be issued for the new location, before you switch rather than after.
• Rewrite rules arrive with layers from every host the site has lived on. Read the file rather than assuming; the cleanup is in cPanel in Practice.

The first two cause most of the failures that appear a week after a move looked successful, usually when an older backup gets restored and reintroduces the previous values.

The address is the step people skip

A transferred account is not automatically doing the thing you came here for. It arrives, it serves, and it may well be sharing an address with something else until you assign it one.

So check it explicitly once the site is up. The address assignment and the nameserver records are the reason you moved in the first place, and neither shows up in a "the site loads" test. The audit is in WHM and Accounts.

Timing

Lower the DNS record lifetime a day ahead, bring the account across while the original is still serving, test here before redirecting anything, then point the domain. Keep the source in place for several days afterwards.

Full sequencing, including how to move an entire network rather than one account, is in Moving In. Migration is free and we do the work, so if you would rather hand over the details than run it yourself, tell us.