The most common questions we get about migrating to iWebVault, answered briefly. For detail on any of them, follow the linked articles.
Will my site go down during migration?
No, if you follow the right order. Your old site stays live until you point DNS to iWebVault as the final step. Done this way, visitors never see downtime.
Does iWebVault do the migration for me?
Single-account migrations you can run yourself in minutes, but our team is happy to run or finish any migration for you. Bulk reseller migrations are typically handled by our team. Just open a ticket.
Is migration free?
iWebVault provides migration tools and support as part of getting you onboard. There’s no separate charge to use the migration system for your accounts.
What do I need to migrate a single site?
Your old cPanel username, password, and the old host’s hostname. That’s it — no root access required.
Do I need root on my old server?
No. Single accounts need only a cPanel login; reseller bulk migrations need only standard reseller access.
Will my email and databases come across?
Yes — mailboxes, messages, databases (with names preserved), users, and grants all transfer.
Will my WordPress site need reconfiguring?
No. Because database names are preserved, wp-config.php keeps working with no edits.
How long does it take?
Minutes for small sites; longer for large accounts. See the timing article for estimates by size.
What if something fails?
You retry — for bulk jobs, only the failed account re-runs. The error reason tells you the cause, and we can help.
Can I keep my old host as a backup?
Yes, and you should — keep it running for a few days after cutover before cancelling, as a fallback.
Is the migration private?
Your backup is pulled directly from your old host to iWebVault — it doesn’t pass through a third party. iWebVault is offshore, anonymous, and DMCA-ignored by default.
More questions, answered
Can I migrate from any control panel, or only cPanel?
The self-service single-account and bulk reseller flows are built around cPanel/WHM sources. If you’re coming from a different panel (DirectAdmin, Plesk, or a custom panel), open a ticket — we handle those migrations too, just with a method suited to that source.
Will my site’s speed change after migrating?
Most customers see their sites get faster on iWebVault thanks to modern NVMe SSD storage and LiteSpeed. The migration itself doesn’t change your site’s code; the performance gain comes from the infrastructure it now runs on.
Do I have to migrate everything at once?
No. You can migrate one site now and others later, or move a reseller fleet in scoped batches. The flows are independent and don’t interfere with each other.
What happens to my old IP-based allow-lists?
Your site gets a new IP on iWebVault, so any third-party service that allow-listed your old server IP needs its allow-list updated to the new one. This is rare but worth checking if you integrate with external APIs that restrict by IP.
Is my data exposed during the migration?
Your backup is pulled directly from your old host to your iWebVault server — it isn’t staged on a third-party machine or routed through an intermediary. Combined with iWebVault’s offshore, anonymous, DMCA-ignored stance, your migration is as private as your hosting.
Can I test before committing my domain?
Yes. You can preview your migrated site on iWebVault before changing DNS, using a hosts-file entry so only your computer sees the new server. This lets you confirm everything works while your live site is untouched.
What if I start a migration and change my mind?
The migration only reads from your old host and restores into your iWebVault account — it changes nothing on the old side. If you decide not to proceed, you simply don’t switch DNS; your old site keeps serving visitors as if nothing happened.
How do I cancel my old host after migrating?
Wait until DNS has fully propagated and you’ve confirmed your site and email run cleanly on iWebVault for a few days. Then cancel the old account through that host’s billing. Keeping it briefly is your rollback safety net.
Where to go next
If your question wasn’t covered here, the other articles in this Migrations section go deep on each topic — planning, the self-service walkthrough, reseller bulk moves, DNS and email cutover, SSL, and troubleshooting. And if you’d rather not handle any of it yourself, our team will run your migration for you; just open a ticket.
Planning and timing questions
When’s the best time to migrate?
Any time, since the migration doesn’t affect your live site. The timing that matters is your DNS cutover — schedule that for a low-traffic window, having lowered your TTL the day before so it propagates quickly. Many people migrate during the day and cut over in the evening.
How far ahead should I plan?
For a single small site, you can migrate and cut over the same day. For large accounts or reseller fleets, give a little lead time so we can set generous time ceilings and schedule the run for a quiet window. A day’s notice is plenty for most moves.
Scope and compatibility questions
Will my PHP version and settings come across?
Your site’s code is unchanged by the migration. iWebVault supports a range of PHP versions; after cutover, confirm your account is set to a compatible PHP version and your site runs cleanly. If you relied on unusual settings, check those, though standard sites need nothing.
Can you migrate from DirectAdmin or Plesk?
The self-service flows target cPanel/WHM sources, but we handle migrations from other panels too — open a ticket and we’ll use a method suited to your source panel.
What about a remote database or external email?
Anything outside your cPanel account — a remote database server, external email on Google or Microsoft — isn’t part of a cPanel migration. It carries on independently; just ensure your migrated site can still reach a remote database, and preserve external email’s MX records during cutover.
Safety and reversibility questions
What if something goes wrong after cutover?
Because you keep your old account live for a few days, rollback is instant: repoint DNS back to the old host and you’re on the known-good site while we resolve any issue. This safety net is the whole reason not to cancel the old account immediately.
Could I lose data?
The migration only reads from your old host and restores into your iWebVault account — it never alters the old side. Your original remains intact throughout. For highly active sites, run the final migration in a brief maintenance window so no last-minute changes are missed between backup and cutover.
If your question isn’t here
The other articles in this Migrations section go deep on each topic, and our team is always available. If you’d rather not handle any part of the migration yourself — single site or reseller fleet — open a ticket and we’ll run it for you and confirm when it’s ready to cut over.
What’s next
- Migrating to iWebVault — How It All Works
- How to Migrate With Zero Downtime
- 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!
