Migrating a reseller business is about more than the accounts themselves. Your packages (the plans you sell), your feature lists (what each plan can use), and your ACLs (reseller privileges) define how your business runs. This guide covers how those carry over to iWebVault.
What each piece does
- Packages — named plans bundling disk, bandwidth, and limits (e.g. Starter, Business)
- Feature lists — which cPanel features a plan’s accounts can access
- ACLs — the privileges your reseller account itself has
Accounts bring their limits regardless
Even before you recreate packages, each migrated account arrives with its own limits intact — disk, bandwidth, email, databases, and so on. So your customers’ allowances are preserved immediately. Packages are about standardising and managing those limits going forward, not about whether the limits survive the move.
Recreating packages on iWebVault
The cleanest approach is to set up packages on iWebVault that match your pricing tiers, then assign migrated accounts to them. This gives you consistent, manageable plans rather than a collection of individually-limited accounts. You can do this before the migration (so assignment is immediate) or afterward at your own pace.
Feature lists and what plans can use
Feature lists are defined on iWebVault to match what each of your plans should offer. Because they’re a server-side definition rather than per-account data, you recreate them on iWebVault to mirror your tiers. We can help you reproduce your existing feature-list structure so your plans behave the same.
Reseller ACLs
Your reseller ACL — the set of privileges your reseller account holds — is configured on iWebVault when your reseller account is provisioned. We set it to give you the management capabilities your business needs. If you require specific privileges, mention them when we set up your reseller account.
Getting it mapped
Open a ticket with your current package names and what each includes, and your feature-list structure. We’ll help reproduce them on iWebVault so that, after the account migration, your whole plan catalogue and privileges match what you had — and your business runs unchanged on faster infrastructure.
Why this is part of a reseller move
Migrating accounts moves your customers’ sites; migrating your packages, feature lists, and ACLs moves your business structure. Without recreating these, you’d have a pile of individually-limited accounts and no tidy plans to sell or manage. Reproducing them on iWebVault means your business operates the same way it did — same plans, same privileges — just on better infrastructure.
Packages — your sellable plans
A package bundles limits (disk, bandwidth, email, databases, and so on) under a name like Starter or Business. On iWebVault you recreate these to match your pricing tiers and assign migrated accounts to them. This restores consistency: every account on a given plan has identical limits, and changing a plan updates all its accounts.
Feature lists — what each plan can use
Feature lists control which cPanel features the accounts on a plan can access. They’re defined server-side, so you reproduce them on iWebVault to mirror what each of your tiers offered. This ensures, for example, that your basic plan exposes the same feature set it always did, and your premium plan its richer set.
ACLs — your reseller privileges
Your reseller ACL is the set of administrative privileges your reseller account holds — what you’re allowed to do in WHM. This is configured when your iWebVault reseller account is provisioned. If your business needs particular privileges, tell us when we set up your reseller account so the ACL matches your requirements.
A clean order of operations
- Share your current package names and what each includes
- Share your feature-list structure
- We help reproduce packages and feature lists on iWebVault
- Migrate the accounts (limits carry over regardless)
- Assign accounts to their matching packages
Reassurance: limits survive either way
Even if you recreate packages afterward, no account loses its limits in the meantime — each migrated account keeps its own disk, bandwidth, and feature allowances from the moment it arrives. Packages are about management and consistency going forward, not about whether your customers’ allowances survive the move. They do.
What’s next
- Packages and Limits After a Reseller Migration
- Migrating a Whole Server’s Accounts With Root/WHM
- Bulk-Migrating a Reseller’s Accounts
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
Account limits carry over automatically, so customers lose nothing — but to run your business you also recreate your packages and feature lists on iWebVault and have your reseller ACL set when your account is provisioned. Set up packages before the bulk job so you can map each account to its plan as it lands. Limits survive regardless; packages are about consistency and management going forward.
Do my customers’ limits survive even before I set up packages?
Yes. Each migrated account keeps its own disk, bandwidth, email, and feature limits from the moment it arrives — independent of whether you’ve recreated packages yet. Packages standardise and simplify management going forward; they’re not what determines whether your customers’ allowances carry over. They do.
Common mistakes to avoid
- Believing accounts lose their limits if packages aren’t recreated first
- Skipping feature lists and leaving plans behaving inconsistently
- Not stating the reseller privileges you need when your account is set up
- Leaving accounts unmapped to packages, making management harder later
Recreating your packages, feature lists, and ACL is what makes your business — not just your customers’ sites — run the same on iWebVault. Set them up before the bulk job, map accounts as they land, and confirm your reseller privileges up front, and your whole plan catalogue and management model arrive intact on faster infrastructure.
Was this helpful?
Thanks for your feedback!
