Reconciling Billing and WHMCS After a Reseller Migration

Migrating your hosting accounts is one half of moving a reseller business; the other half is making sure your billing system matches the new reality. If you use WHMCS or a similar platform, this guide covers reconciling it after a reseller migration so invoicing and provisioning keep working.

Why reconciliation is needed

Your billing platform holds records linking each customer to their hosting account on a specific server. After migrating, those accounts now live on iWebVault — so your billing system needs to know where they are, or its automated functions (suspend, unsuspend, create, terminate) will target the old server.

The core things to update

• Server definitions — add your iWebVault server so the billing platform can manage accounts there
• Service records — repoint each migrated service to the iWebVault server
• Credentials — ensure the billing platform authenticates to iWebVault correctly
• Provisioning module — confirm it’s configured for the new server

A practical reconciliation order

1. Add iWebVault as a server in your billing platform with working credentials
2. Confirm a test action (like a connection check) succeeds against it
3. Repoint migrated services to the iWebVault server, matching each to its account
4. Verify automated functions (suspend/unsuspend) work on a test account
5. Only then decommission the old server definition

Matching by username helps

Because migrated accounts keep their original usernames, matching billing records to accounts is straightforward — the username in your billing system still matches the account on iWebVault. This is one more way preserved usernames make a reseller migration cleaner.

Keeping invoicing uninterrupted

Your customers’ billing cycles and invoices live in your billing platform, not on the server, so they continue uninterrupted by the migration. What you’re reconciling is the link between billing records and the now-migrated accounts — get that right and invoicing, renewals, and automated provisioning all carry on normally.

The two halves of moving a hosting business

Moving a reseller business has two halves: the accounts (handled by the migration) and the billing records that manage them. Your billing platform — WHMCS or similar — links each customer to their hosting account on a particular server and automates actions like create, suspend, and terminate. After migrating, those links point at the old server until you reconcile them.

What needs updating

• Server definition — add iWebVault so the platform can manage accounts there
• Service records — repoint each migrated service to the iWebVault server
• Authentication — ensure the platform can connect to iWebVault
• Provisioning module — confirm it targets the new server

A safe reconciliation order

1. Add iWebVault as a server with working credentials
2. Run a connection test to confirm it authenticates
3. Repoint migrated services to iWebVault, matching each to its account
4. Test an automated action (suspend/unsuspend) on one non-critical account
5. Only after that works, remove or retire the old server definition

Usernames make matching easy

Because migrated accounts keep their original usernames, matching each billing record to its account on iWebVault is straightforward — the username your billing platform already stores still identifies the account. This is one more way preserved usernames smooth a reseller migration, right down to the billing layer.

Invoicing continues uninterrupted

Your customers’ billing cycles, invoices, and payment records live in your billing platform, not on the server — so they carry on uninterrupted by the migration. What you’re fixing is the link between those records and the now-migrated accounts. Get that right and renewals, invoicing, and automated provisioning all resume normally on iWebVault.

What’s next

• Suspended Accounts in a Reseller Migration
• Accounts Keep the Same Usernames
• Migrating WHM Packages, Feature Lists, and ACLs

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

After migrating, your billing platform’s links still point at the old server, so add iWebVault as a server, repoint each migrated service to it, confirm authentication, and test automated suspend/unsuspend on one account before trusting it fleet-wide. Preserved usernames make matching records to accounts easy. Invoicing continues uninterrupted; you’re only reconciling the link between billing and the moved accounts.

Will my customers’ billing be interrupted?

No. Billing cycles, invoices, and payment records live in your billing platform, not on the server, so they continue uninterrupted. What you reconcile is the connection between those records and the now-migrated accounts — once repointed to iWebVault, automated provisioning and renewals resume normally.

Common mistakes to avoid

• Removing the old server definition before services are repointed
• Trusting fleet-wide automation without testing one account first
• Forgetting to add iWebVault as a server in the billing platform
• Assuming invoicing breaks during the move — it doesn’t

Reconciling billing is the often-forgotten second half of a reseller migration, but it’s quick when done in order: add the server, repoint services, test automation on one account, then retire the old definition. Preserved usernames make matching trivial, and your customers’ invoicing never skips a beat because it lives in your platform, not on the server.

When to let us handle it

If your billing platform setup is involved — many services, custom provisioning, or automation you rely on heavily — it’s worth letting us help with the reconciliation. We can confirm the right server settings and credentials for iWebVault, advise on repointing services in bulk, and help you test automated actions safely before you trust them across the fleet. Getting the billing layer reconciled correctly is what restores hands-off provisioning after a move, so a little guidance here pays off every time your platform suspends, unsuspends, or creates an account on your behalf.