The migration form asks for your old host’s hostname or server address. This tells iWebVault where to fetch your backup from. Here’s how to find the right value and what format to use.
What the field expects
Enter the server’s hostname (something like server123.oldhost.com) or its IP address (like 192.0.2.10). Either works. Don’t enter your website domain here — that often points somewhere different from the actual cPanel server.
Where to find it
- Welcome email — your old host’s signup email usually lists the server hostname for cPanel access
- cPanel URL — when you log into cPanel, the address bar shows the hostname, e.g.
https://server123.oldhost.com:2083 - Billing panel — the service details page often shows ‘Server Name’ or ‘Hostname’
Hostname or IP — which is better?
Both work. A hostname is easier to read; an IP is more direct. If the hostname doesn’t connect, try the IP, and vice versa. If you only know your domain, you can look up the server IP, but the cPanel hostname from your welcome email is the most reliable.
Ports
You don’t normally need to specify a port — the tool uses the standard cPanel ports automatically. If your old host uses non-standard ports, our support team can help you set them.
Why the domain often isn’t the server
It’s tempting to type your website domain into the hostname field, but that frequently points somewhere other than your actual cPanel server — especially if you use a CDN, a proxy like Cloudflare, or if your domain’s A record was customised. The migration needs to reach the real cPanel/WHM server, which is why the server’s own hostname (from your welcome email) is the reliable choice.
Reading your cPanel URL for the hostname
The easiest place to find the true server hostname is your browser’s address bar when you’re logged into cPanel. A cPanel session URL looks like this:
https://server123.oldhost.com:2083/cpsess1234567890/frontend/...
The part right after https:// and before the :2083 port — here server123.oldhost.com — is your server hostname. That’s exactly what to enter.
When to use the IP instead
If the hostname doesn’t resolve or connect (some hosts use internal names), use the server’s IP address instead. You can find it in your welcome email, your billing panel’s server details, or by asking your old host ‘what is the IP of the server my account is on?’. Either the hostname or the IP works equally well.
Non-standard ports
The vast majority of cPanel servers use the standard ports, and you don’t need to enter anything special. If your old host runs cPanel on custom ports, that’s unusual — open a ticket and we’ll set the migration up for it.
Double-checking before you submit
Before submitting, sanity-check three things together: the hostname is the server (not your domain), the username is your cPanel username (lowercase, no spaces), and the password is current. The tool validates on submit, but checking these first saves a round trip.
A simple rule to remember
When in doubt, remember this: the hostname field wants the address of the computer your account lives on, not the address of your website. Your website domain is for visitors; the server hostname is for administration. They’re frequently different, and using the server hostname is what reliably connects the migration to the right place.
Three reliable sources, ranked
- Your cPanel address bar — the most reliable; it literally shows the server hostname when you’re logged in
- Your welcome email — lists the server hostname for cPanel access
- Your billing panel’s server details — often labelled ‘Server Name’ or ‘Hostname’
If all three disagree or you can’t find them, the server’s IP address is a dependable fallback — ask your old host ‘what IP is my account’s server on?’ and use that.
Why CDNs and proxies break this field
If you use Cloudflare or another CDN, your website domain resolves to the CDN, not your real server — that’s the whole point of a CDN. Entering your domain (which points at the CDN) into the hostname field would aim the migration at the CDN, which holds no backup. Always use the origin server’s true hostname or IP, bypassing any CDN, so the migration reaches the actual cPanel server holding your data.
Confirming before submit
Before you submit the migration form, sanity-check the three inputs as a set: the hostname is the server (not your domain), the username is your cPanel username in lowercase, and the password is current. The tool validates on submit and will tell you immediately if the host is unreachable — but verifying the hostname is a true server address first saves that round trip and gets your migration moving on the first try.
Key takeaways
Enter the address of the server your account lives on — not your website domain. The most reliable source is your cPanel address bar (the part before :2083); your welcome email and billing panel also list it, and the server IP is a dependable fallback. Avoid CDN or proxy addresses, which sit in front of your real server and hold no backup.
What if my domain and server hostname look the same?
On some setups they can appear similar, but use whatever your cPanel address bar shows when you’re logged in — that’s always the true server hostname. If a connection attempt fails using the hostname, switch to the server’s IP address, which removes any ambiguity about where the migration should connect.
What’s next
- Finding Your Old cPanel Username and Password
- “Access Denied” Connecting to Your Old Host
- Migrate Your cPanel Account Yourself
Still stuck? Our team can run or finish the migration for you — open a support ticket and we’ll take it from there.
Was this helpful?
Thanks for your feedback!
