A few minutes of preparation makes a migration go smoothly. This checklist covers what to gather and verify before you start, so the move runs without surprises. None of it is difficult — it’s mostly about having the right details to hand.
1. Gather your old host credentials
You’ll need the cPanel username and password for the account you’re moving, plus the old server’s hostname or IP address. These are in your original host’s welcome email, or visible when you log into their control panel.
2. Confirm your iWebVault account is ready
Your destination account is created automatically when you buy a hosting plan. Make sure the plan you bought is large enough to hold your site — check your current disk usage on the old host and pick an iWebVault plan that comfortably exceeds it.
3. Take a fresh backup (peace of mind)
The migration does not delete anything from your old host — your original stays put until you cancel it. Still, having your own recent backup is good practice. Most control panels offer a one-click full backup download.
4. Note anything custom
- Custom cron jobs and their schedules
- Any non-standard PHP version or settings your app needs
- Email accounts you must keep working
- Third-party services pointing at your current IP
5. Understand the flow
Every migration follows the same six stages, shown below. Knowing the sequence helps you read the progress indicator correctly.
6. Plan your cutover timing
Decide in advance when you’ll switch DNS. The migration itself can run any time without affecting your live site, but the DNS cutover is when visitors actually move to iWebVault. Many people migrate and verify during the day, then switch DNS in the evening when traffic is lowest. If your audience is global, pick the quietest window for your biggest region.
7. Lower your DNS TTL ahead of time
If you can, drop your domain’s DNS TTL to 300 seconds a day before you plan to cut over. TTL controls how long the internet caches your DNS answers; a low value means your switch to iWebVault propagates in minutes instead of hours. You set this at whoever currently controls your DNS — your registrar or current DNS host.
8. Inventory anything outside cPanel
A cPanel migration moves everything inside your cPanel account, but some things live elsewhere and need separate attention:
- External email on Google Workspace or Microsoft 365 — defined by MX records, keep them
- A CDN like Cloudflare sitting in front of your site — you’ll update its origin to iWebVault
- Remote database servers — not in cPanel, handled separately
- Third-party services that allow-list your current server IP
A printable version of the checklist
If you like working from a list, here’s the whole thing in order: gather old cPanel username, password, and server hostname; confirm your iWebVault plan is active and large enough; take your own backup for peace of mind; note custom crons, PHP settings, and email accounts; plan your cutover time; lower your DNS TTL the day before; and inventory anything that lives outside cPanel. Tick those off and your migration will be uneventful — which is exactly what you want.
Why each item earns its place
This isn’t a checklist for its own sake — each item prevents a specific, common problem. Gathering credentials in advance avoids a failed connection at the first step. Confirming plan size avoids running out of disk mid-restore. Lowering TTL avoids a slow cutover. Inventorying external services avoids the ‘my email stopped’ surprise that comes from forgetting an external MX record. A few minutes here removes nearly every avoidable migration headache.
A note on backups you control
Although the migration leaves your old host untouched, having your own downloaded backup gives you a fully independent copy that doesn’t depend on either host. It’s the belt-and-braces option for important sites. Most control panels offer a one-click full backup you can download to your computer and set aside until the move is confirmed.
Confirming your destination plan
Check your current disk usage on the old host — usually shown on the cPanel home screen — and make sure your iWebVault plan exceeds it with comfortable headroom. Account for growth too: a site that’s 4 GB today and growing shouldn’t move onto a plan capped near 4 GB. Headroom now saves an upgrade later.
If you’re not sure which plan you need
Our team can look at your current usage and recommend the right iWebVault plan before you migrate, so the destination is correctly sized from the start. Open a ticket with your current disk and bandwidth figures and we’ll advise.
Putting it into action
Work through the checklist top to bottom the day before you intend to migrate. By the time you start the actual migration, every input is ready, every external dependency is noted, and your cutover timing is planned. That preparation is what turns a migration from a nervous event into a routine, uneventful task.
Key takeaways
- Gather your old cPanel username, password, and server hostname before you start
- Confirm your iWebVault plan is active and comfortably larger than your current usage
- Take your own downloaded backup as an independent safety copy
- Note custom crons, PHP needs, email accounts, and anything living outside cPanel
- Lower your DNS TTL the day before and plan a low-traffic cutover time
Run these the day before migrating and the move itself becomes a routine, uneventful task — every input ready, every dependency noted, nothing left to discover mid-migration.
Do I have to take my own backup if the migration keeps the old site?
It’s optional, since the migration never alters your old host and you keep the old account as a fallback. But for an important site, an independent downloaded backup that depends on neither host is cheap peace of mind — most control panels make it a single click.
What’s next
- Migrating to iWebVault — How It All Works
- Migrate Your cPanel Account Yourself
- Pointing Your Domain to iWebVault
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!
