Migrations

Which Migration Method Is Right for You?

Single account or bulk reseller migration? A quick guide to picking the right path based on what you're moving to iWebVault.

5 min read

iWebVault supports two migration paths. Picking the right one takes about thirty seconds once you know what you’re moving. This guide makes the choice obvious.

Choose single-account if…

  • You’re moving one website or one cPanel account
  • You have the account’s own cPanel username and password
  • You want to run it yourself from your client area

This is the most common case — a single site moving from another host. You stay in control and can start it whenever you like.

Choose bulk reseller if…

  • You’re a reseller moving many client accounts at once
  • The accounts are all owned by your reseller on the old server
  • You want them migrated together and kept under your reseller on iWebVault

Bulk migration authenticates as your reseller account, moves every owned account, and keeps them all under your reseller on iWebVault — same usernames, same ownership.

Old Host (source) Your current cPanel / WHM no root needed iWebVault control & scheduling iWebVault (dest) Your new cPanel account restore happens here backup pulled directly: source to destination
📘 NoteNot sure if you’re a reseller? If you log into WHM (not just cPanel) on your old host and manage multiple customer accounts, you’re a reseller and the bulk path fits.

Can you mix both?

Yes. You can migrate a single account today and run a bulk job later, or vice versa. They’re independent and don’t interfere with each other.

A decision in one question

If you’re unsure which path you need, ask yourself a single question: do you log into WHM on your old host, or only cPanel? If you only ever see cPanel — managing one site’s files, email, and databases — you’re a single account, and the self-service path is for you. If you log into WHM and create or manage multiple customer accounts, you’re a reseller, and the bulk path fits.

Single-account in more depth

The single-account path is designed so a non-technical site owner can run it unaided. You provide your old cPanel login and server hostname, and iWebVault does the rest — backup, transfer, restore — into the account your plan already created. It suits anyone moving one website, whether that’s a WordPress blog, a small store, or a static site.

Bulk reseller in more depth

The bulk path is built for people who resell hosting. It authenticates with your reseller credentials on the old server, enumerates every account you own, and moves them in sequence — each restored under the same username and assigned to your reseller on iWebVault. It preserves your whole hierarchy, so your customers’ logins and your ownership both carry across unchanged.

📘 NoteThe two paths use different credentials: single-account uses a cPanel login; bulk uses your reseller WHM login. That difference is the clearest signal of which one you’re in.

Edge cases

  • You have several of your own sites, each its own cPanel account: run several single-account migrations, one per site.
  • You’re a reseller but only want to move a few accounts: we can scope a bulk job to a subset.
  • You have a very large or unusual account: let us run it directly with tuned settings.

You can always ask first

If after all this you’re still unsure, open a ticket describing what you’re moving — one site, several sites, or a reseller fleet — and we’ll tell you exactly which path to use and help you start it.

Comparing the two paths side by side

The clearest way to choose is to compare what each path needs and produces. Single-account uses your cPanel login, moves one account, and you can run it yourself in minutes. Bulk reseller uses your reseller WHM login, moves every account you own in sequence, preserves usernames and ownership, and is typically run by our team because it involves WHM-level credentials. If your situation matches the first description, self-serve; if the second, plan a bulk job.

What if you’re a developer or agency?

Developers and agencies often sit between the two cases: you manage several clients’ sites, but each may be its own standalone cPanel account rather than a reseller hierarchy. In that case you run a single-account migration per client site. If instead you hold a reseller account with all clients underneath it, the bulk path moves them together. The deciding factor is again whether you log into WHM as a reseller or just into individual cPanels.

Choosing when you’ll change hosts and domains together

If you’re simultaneously moving host and changing your domain name, that’s a special case — the migration moves the account, but the domain change means you’ll also update the site’s URL afterward. Tell us if you’re doing both at once and we’ll guide the extra step so links and settings update correctly. A straight host move with the same domain needs none of this.

Still unsure? Ask before you start

There’s no penalty for asking. Open a ticket describing exactly what you’re moving — one site, several separate sites, or a reseller fleet — and we’ll confirm the right method and help you begin. It’s faster to ask up front than to start down the wrong path and backtrack.

Key takeaways

  • Moving one site with a cPanel login → single-account self-service
  • Moving many accounts you own via a reseller WHM login → bulk reseller
  • Several separate sites, each its own account → one single-account migration each
  • Unsure, or unusual setup → open a ticket and we’ll confirm the method

The deciding question is simple: do you log into WHM as a reseller, or only into individual cPanels? That single distinction points you to the right path almost every time.

Can I switch methods later?

Yes. The paths are independent — you can run a single-account migration today and a bulk reseller job next week, or vice versa, without one affecting the other. Nothing commits you to a single method.

Ready to move to iWebVault?Offshore, anonymous, DMCA-ignored hosting — and our migration tools bring your sites across for you.Start from $1 →

What’s next

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?