If you’re a reseller moving to iWebVault, you don’t have to migrate each client account by hand. The bulk migration moves every account your reseller owns, keeps the same usernames, and leaves them all under your reseller on iWebVault. This overview explains how it works.
What bulk migration does
Bulk migration authenticates as your reseller on the old server, lists every account you own, and moves them one at a time to iWebVault. Each restored account is placed under your reseller here, so your structure is preserved.
What you need
- Your reseller WHM username and password on the old server (or an API token)
- Your reseller account already set up on iWebVault — we provision this for you
- An iWebVault reseller plan large enough for all your accounts
How it runs
Accounts migrate one at a time, in sequence. For each, the system backs it up through your reseller access, pulls it to iWebVault, restores it under the same username, and assigns ownership to your reseller. The next account starts only when the previous one finishes.
Who runs it
Bulk reseller migrations are typically run by our team or an administrator, because they involve your WHM-level reseller credentials. Open a ticket to schedule one and we’ll coordinate it with you.
What to expect timing-wise
Because accounts run sequentially to protect both servers, a reseller with many accounts can take several hours overall. It’s fully automated — you’ll get a summary when it finishes.
The lifecycle of a bulk job
A bulk reseller migration has a clear lifecycle. First we provision your reseller account on iWebVault, so there’s an owner waiting for your accounts. Then the job authenticates as your reseller on the old server and lists every account you own. It works through them one at a time: back up an account through your reseller access, pull it to iWebVault, restore it under the same username, assign it to your reseller. When the last account finishes, you get a summary.
What we need from you to start
- Your reseller WHM username and password (or API token) on the old server
- Confirmation of which accounts to move (all, or a specified subset)
- A short maintenance window agreed for the move, if your accounts are busy
Monitoring progress
Throughout the job you can see which account is currently being processed and which have completed or failed. Because accounts are independent, you get a live, account-by-account picture rather than a single opaque progress bar. The completion summary tells you how many succeeded and flags any that need a retry.
Handling a partial result
If most accounts succeed and one or two fail — usually a transient issue or an oversized account — the job still completes for the rest, and you retry just the stragglers. Nothing about a single failure jeopardises the accounts that already moved successfully.
Why this beats traditional reseller transfers
Conventional server-to-server reseller transfers demand root on the source and move everything in one giant operation that can overload both servers. iWebVault’s approach needs only reseller access, moves accounts gently one at a time, preserves usernames and ownership, and isolates failures — a materially safer way to move a hosting business.
What success looks like
A successful bulk migration ends with every one of your accounts present on iWebVault, each under its original username, each owned by your reseller, with files, databases, and email intact — and a completion summary confirming how many succeeded. Your customers keep their logins, their sites work unchanged, and your management hierarchy mirrors what you had. The move is invisible to your end customers beyond improved performance.
Coordinating the move with us
Because bulk migrations involve your reseller-level credentials and can run for hours, they’re best coordinated with our team. You provide your reseller WHM login (or token) and confirm the scope; we provision your iWebVault reseller account, schedule the run for a quiet window if your accounts are busy, and monitor it through to completion. You get progress visibility throughout and a summary at the end.
Scoping a partial move
You don’t have to move every account at once. If you’d rather migrate a subset first — a pilot batch to build confidence, or just your less-critical accounts ahead of the busy ones — we can scope the job to specific accounts. This staged approach lets you validate the process on a few accounts before committing your whole customer base.
After the bulk job completes
- Review the completion summary for any failed accounts to retry
- Open your reseller account list in WHM to confirm ownership
- Spot-check a few accounts’ sites and databases
- Map accounts to your iWebVault packages if you use defined tiers
- Plan DNS cutover per account or per domain as appropriate
The reassurance for your business
Moving a hosting business sounds daunting, but the design removes the usual risks: no root needed on the source, gentle one-at-a-time processing, preserved usernames and ownership, isolated failures, and the ability to migrate in batches. Combined with our team running it for you, a reseller migration becomes a planned, low-risk operation rather than a leap of faith.
Key takeaways
Bulk migration authenticates as your reseller on the old server, moves every owned account one at a time, restores each under its original username, and assigns ownership to your reseller on iWebVault — no source root needed. We provision your reseller account first, then run the job (scoped to all accounts or a subset) and give you a completion summary. Your customers keep their logins and sites; only performance changes.
Can I migrate just a few accounts first as a test?
Yes. We can scope a bulk job to specific accounts, so you can pilot the process on a few less-critical accounts, confirm the results, and then move your whole customer base with confidence. Staging the move this way is a sensible way to build certainty before committing everything.
What’s next
- Migrating as a Reseller Without Source Root
- Your Accounts Stay Under Your Reseller
- 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.
Was this helpful?
Thanks for your feedback!
