Why Bulk Migration Runs One Account at a Time
Bulk migrations process accounts sequentially on purpose — to protect both servers and guarantee each account arrives intact. Here's the reasoning.
Knowledge Base
iWebVault Blog
Tutorials, comparisons, and resources for offshore web hosting. Everything you need to know about DMCA-ignored hosting, anonymous infrastructure, and offshore privacy.
More articles
Retrying Individual Failed Accounts in a Bulk Job
If one account fails during a bulk reseller migration, you can retry just that account without re-running the whole job.…
Migrating as a Reseller Without Source Root Access
You don't need root on your old server to bulk-migrate your reseller accounts to iWebVault. Here's how reseller-level access is…
Your Migrated Accounts Stay Under Your Reseller
After a bulk migration, every account is owned by your reseller on iWebVault — your hierarchy and control are preserved…
Bulk-Migrating a Reseller’s Accounts to iWebVault
An overview of moving an entire reseller's accounts to iWebVault at once — how it works, what you need, and…
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…