When you bulk-migrate to iWebVault, the accounts don’t just land as orphaned cPanel accounts — each one is assigned to your reseller, so you keep ownership and control just as you had on your old server.
Ownership is set automatically
As each account is restored, the migration sets its owner to your reseller account on iWebVault. That means the accounts appear under your reseller in WHM, you can manage them, suspend them, change packages, and your customers stay yours.
Why this matters
- Your client accounts remain under your control, not the server admin’s
- Your reseller’s account list looks the same as it did before
- Billing and management stay in your hands
Same names, same structure
Accounts keep their original usernames, and they all sit under your reseller — so your hierarchy is reproduced faithfully. Nothing is flattened or renamed.
Verifying ownership after migration
After the job completes, your reseller’s account list in WHM shows every migrated account owned by you. The completion summary also notes that each account was restored and assigned to your reseller.
Ownership in WHM terms
In WHM, every account has an ‘owner’ — the reseller responsible for it. Ownership controls who can manage, suspend, modify, and bill the account. When your accounts migrate to iWebVault, each one’s owner is set to your reseller, so they appear in your reseller’s account list and you retain full management control, exactly as on your old server.
Set automatically, account by account
As each account finishes restoring, the migration assigns its owner to your reseller before moving to the next. By the time the job completes, every migrated account is already under you. There’s no separate ownership step for you to perform afterward.
Why ownership matters for resellers
- You — not the server admin — manage and bill your customers
- Your reseller’s account list mirrors what you had before
- Suspensions, package changes, and support stay in your hands
- Your white-label relationship with customers is preserved
Verifying after the job
Once the bulk job completes, open your reseller’s account list in WHM on iWebVault. Every migrated account should appear, owned by you. The job’s completion summary also records, per account, that it was restored and assigned to your reseller — so you have a written confirmation as well as the WHM view.
If an owner looks wrong
In the rare event an account shows the wrong owner, it’s corrected with a single ownership change — no re-migration required. Flag it to support with the account name and we’ll set it right immediately.
What ownership controls
In WHM, the account owner is the reseller responsible for an account — and ownership is what gives you the power to manage it: suspend or unsuspend, change packages and limits, modify settings, and handle billing. When your accounts migrate with ownership set to your reseller, you retain every one of those powers on iWebVault, exactly as you held them before.
Ownership and your white-label relationship
For resellers, ownership underpins the white-label relationship with customers. Your customers deal with you, not the underlying server admin. Preserving ownership through the migration means that relationship is unbroken — your customers remain yours, your branding and billing stay in place, and the change of underlying infrastructure is invisible to them.
Verifying ownership, account by account
After the bulk job, the quickest confirmation is your reseller’s account list in WHM on iWebVault — every migrated account should appear under your reseller. The completion summary also records, per account, that it was restored and assigned to you, giving you a written audit trail alongside the live WHM view. Between the two, you can confirm ownership comprehensively.
Correcting a misassigned owner
Should an account ever show the wrong owner — uncommon, but possible — it’s fixed with a single ownership change, no re-migration required. Flag the account name to support and we’ll correct it immediately. Because ownership is a setting rather than a property of the data, adjusting it is instant and safe.
The bigger picture
Ownership preservation is one of three pillars — alongside same usernames and preserved databases — that together make a reseller migration feel seamless. Ownership keeps control in your hands; usernames keep customer logins working; preserved databases keep their sites functioning. Remove any one and the move gets bumpy; together they deliver continuity your customers barely notice.
Key takeaways
Every migrated account is assigned to your reseller on iWebVault, automatically and account by account, so you keep full management control — suspend, modify, package, and bill — exactly as before. This preserves your white-label relationship with customers. Confirm ownership afterward in your reseller’s WHM account list; a misassigned owner (rare) is a one-line fix, never a re-migration.
Why does ownership matter so much for a reseller?
Ownership is what makes the accounts yours to manage and bill, keeping your customers dealing with you rather than the underlying server admin. Preserved through migration, it means your business relationship and white-label setup continue unbroken — your customers never see the infrastructure change beneath them.
A note on how ownership is recorded
Ownership in cPanel/WHM is stored as an attribute of each account, not as a property of its files or databases — which is why it can be set during the restore and adjusted afterward without ever touching your data. When the migration assigns an account to your reseller, it’s writing that attribute; if it ever needs correcting, it’s rewriting the same attribute. This is why an ownership fix is instant and carries no risk to the account’s contents.
It also explains why ownership and data integrity are completely independent concerns. A migrated account could, in principle, hold perfect data while showing the wrong owner — and the fix would be a single ownership change leaving every file and database untouched. In practice the migration sets the correct owner as it restores each account, so this is a reassurance about safety rather than a step you’ll usually need.
What’s next
- Accounts Keep the Same Usernames
- Bulk-Migrating a Reseller’s Accounts
- Packages and Limits After a Reseller Migration
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!
