Some people aren’t ‘resellers’ in the billing sense but do have full root/WHM on a server — for example, you run your own VPS or dedicated box and want to move every account on it to iWebVault. The bulk process applies here too, and having root gives you a bit more flexibility. This guide covers that scenario.
Root/WHM vs reseller access
A reseller can access and back up the accounts they own. With root/WHM, you can access every account on the server, see all packages and settings, and have full administrative control. For a migration, that means the move can encompass the entire server rather than one reseller’s slice.
Planning a whole-server move
- Inventory every account on the server and its rough size
- Confirm your iWebVault plan (reseller or larger) has capacity for everything combined
- Decide whether to move all accounts at once or in batches
- Note server-wide settings (packages, feature lists) you want reproduced
What root lets us preserve
With root-level visibility on the source, a migration can faithfully reproduce more of the server’s structure on iWebVault — packages, ownership relationships, and account settings — rather than just account contents. This is useful when you’re effectively recreating your whole hosting environment on iWebVault.
Coordinating the move
Whole-server migrations are best coordinated with our team because of their scale and the root-level access involved. Open a ticket describing your server (panel, number of accounts, total size, and whether you have root or WHM), and we’ll plan a batched, low-impact migration and confirm the schedule with you.
Decommissioning the old server
Who this applies to
This scenario fits anyone who controls a whole server — a VPS or dedicated box with root/WHM — rather than holding a reseller slice of someone else’s server. You might be a small host consolidating onto iWebVault, an agency that ran its own box, or a business that outgrew self-management. With root, the move can encompass everything on the server.
What having root changes
Reseller access lets you migrate the accounts you own. Root/WHM lets you see and migrate every account, plus the server-wide structure around them — packages, feature lists, and ownership relationships. So a root-level migration can reproduce more of your environment on iWebVault, not just account contents. It’s the difference between moving your accounts and recreating your hosting setup.
Planning the move
- Inventory every account and its approximate size
- Confirm your iWebVault plan has capacity for the combined total
- Decide on a single run or batches by priority
- List server-wide settings (packages, feature lists) to reproduce
Still gentle and sequential
Having root doesn’t change the careful approach: accounts still migrate one at a time so neither server is overloaded, and failures stay isolated. Root simply widens the scope of what can be included and lets more of the surrounding structure be preserved — it doesn’t make the move more aggressive.
Coordinating and decommissioning
Because of the scale and the root access involved, whole-server moves are best coordinated with our team. We’ll plan a batched, low-impact migration and confirm timing with you. And as always, keep the old server fully intact until every account is migrated, verified, and cut over, with a few days of clean running on iWebVault before you decommission it.
What’s next
- Bulk-Migrating a Reseller’s Accounts
- Migrating WHM Packages, Feature Lists, and ACLs
- Why Bulk Migration Runs One Account at a Time
Still stuck? Our team can run or finish the migration for you — open a support ticket and we’ll take it from there.
Key takeaways
If you have root/WHM on a whole server (a VPS or dedicated box), the bulk approach can move every account plus your packages, feature lists, and ownership structure — not just one reseller’s accounts. It still migrates one account at a time to protect both servers. Coordinate with our team for scale, and keep the old server intact until everything is verified and stable on iWebVault.
What’s the difference from a reseller migration?
A reseller migration moves the accounts you own; a root/WHM migration can move the entire server and reproduce more of its structure (packages, feature lists, ownership). The gentle one-at-a-time mechanism is the same — root simply widens what can be included and preserved.
Common mistakes to avoid
- Wiping or cancelling the source server before everything is verified
- Underestimating combined capacity needs across all accounts
- Trying to migrate everything in one frantic pass instead of batches
- Forgetting to reproduce server-wide packages and feature lists
A whole-server move is the largest kind of migration, so it rewards planning: inventory everything, size your iWebVault plan for the total, batch the work, and reproduce your structure. Coordinated with our team and kept gentle and sequential, even a full server consolidates onto iWebVault without drama — and the old server stays as your fallback until it’s all proven.
When to let us handle it
Whole-server migrations are best run in partnership with our team from the outset, given their scale and the root access involved. Rather than attempting to move dozens of accounts and reproduce server-wide settings alone, open a ticket describing your server — the panel, the number and size of accounts, and whether you have root or WHM. We’ll plan a batched, low-impact schedule, reproduce your packages and structure, and confirm timing with you. Coordinating from the start means the consolidation runs smoothly and your old server stays as a complete fallback until everything is verified on iWebVault.
Was this helpful?
Thanks for your feedback!
