When your reseller accounts migrate, each one arrives with its resource limits intact. This article explains how packages and quotas carry over and how to manage them on iWebVault afterward.
Limits come across with each account
Each account’s existing limits — disk space, bandwidth, email accounts, databases, subdomains — are brought over as part of the restore. Accounts arrive provisioned the way they were on your old server, so nothing your customers had is silently reduced.
Packages on iWebVault
On iWebVault you manage your accounts under your reseller’s package allocation. After migration you can map accounts to your iWebVault packages, or keep their migrated limits and adjust per-account as needed.
Adjusting limits after migration
- Change a single account’s quota from WHM under your reseller
- Create iWebVault packages that match your pricing tiers
- Assign migrated accounts to those packages for consistent limits
If an account needs more room
If a migrated account is close to its disk limit, raise it from your reseller WHM (within your plan’s total). There’s no need to re-migrate to change a quota.
Capacity planning before the move
The one capacity check that matters for a reseller move is total footprint: add up the disk and bandwidth your accounts use, and make sure your iWebVault reseller plan comfortably exceeds it. Individual account limits come across automatically; what you’re sizing is the overall allocation your reseller plan provides.
How limits arrive with each account
Each migrated account brings its existing quotas — disk, bandwidth, email accounts, databases, subdomains, addon domains. Nothing your customers had is silently trimmed. An account that allowed ten email accounts still allows ten after the move.
Mapping accounts to iWebVault packages
On iWebVault you’ll typically define packages that match your pricing tiers — Starter, Business, and so on — and assign migrated accounts to them so limits are consistent and easy to manage going forward. You can do this after the migration at your own pace; accounts work fine in the meantime with their migrated limits.
Adjusting an individual account
Need to give one customer more disk? Change it from your reseller WHM, within your plan’s total allocation. There’s no re-migration involved in a quota change — it’s a live setting on the account.
Overselling considerations
If your business model uses overselling (allocating more total limits than the plan’s raw capacity, betting that not everyone uses their full quota), set that up through your iWebVault package definitions as you would on any reseller platform. The migration is neutral to your overselling strategy — it brings accounts across; how you allocate going forward is your policy.
Bandwidth resets
Bandwidth counters typically start fresh in the new billing context on iWebVault. Confirm your customers’ bandwidth allocations look right after migration, especially for high-traffic accounts near their limits.
The one capacity calculation that matters
Before a reseller move, do a single sum: add up the total disk and bandwidth your accounts consume, and confirm your iWebVault reseller plan comfortably exceeds that total, with headroom for growth. Individual account limits carry over automatically — what you’re sizing is the overall allocation your reseller plan provides to hold everything at once.
How per-account limits arrive
Each migrated account brings its existing quotas: disk, bandwidth, email accounts, databases, subdomains, and addon domains. Nothing your customers had is silently reduced — an account that permitted ten mailboxes still permits ten after the move. The limits are part of what the restore preserves, so your customers’ allowances are intact from the first moment on iWebVault.
Standardising with packages
On iWebVault you’ll typically define packages matching your pricing tiers and assign migrated accounts to them, so limits are consistent and easy to manage going forward. You can do this after the migration at your own pace — accounts work fine with their migrated limits in the meantime. Setting up packages before the bulk job, though, lets you assign accounts to them immediately afterward for a tidy result from day one.
Adjusting and overselling
Need to give one customer more disk? Change it from your reseller WHM, within your plan’s total allocation — no re-migration required. If your business model uses overselling, configure that through your iWebVault package definitions as you would on any reseller platform. The migration is neutral to your allocation strategy; it brings accounts across, and how you allocate going forward remains entirely your policy.
Post-migration capacity review
- Confirm your reseller plan’s total usage sits comfortably below its cap
- Check high-traffic accounts’ bandwidth allocations look right
- Verify disk-heavy accounts have headroom before their limits
- Map accounts to packages if you use defined tiers
A quick review like this just after migrating catches any account that’s close to a limit, so you can raise it proactively rather than reactively.
Key takeaways
Each account’s quotas — disk, bandwidth, email, databases, subdomains — carry over intact, so nothing your customers had is reduced. The one capacity check before moving is confirming your iWebVault reseller plan exceeds your accounts’ combined total with headroom. Afterward, map accounts to iWebVault packages matching your tiers for consistency; per-account adjustments are made live from WHM with no re-migration.
What should I check about limits right after migrating?
Confirm your reseller plan’s total usage sits comfortably below its cap, check high-traffic accounts’ bandwidth allocations look right, and verify disk-heavy accounts have headroom before their limits. Catching an account that’s close to a limit now lets you raise it proactively rather than after a customer hits a wall.
What’s next
- Your Accounts Stay Under Your Reseller
- Bulk-Migrating a Reseller’s Accounts
- Accounts Keep the Same Usernames
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!
