Migrating from WHMCS or HostBill
Dry-run by default, idempotent, and the one thing that cannot come across.
The reason people stay on a billing platform they dislike is the migration. This one is built to be rehearsed rather than attempted.
What comes across
Clients, hosting accounts, domains and invoices — read directly from your existing MySQL database.
How to run it
The import is dry-run by default. It reports what it would do and changes nothing. Read the report, fix what is wrong at the source, and run it again.
It is also idempotent: running it twice does not double anything. Rehearse until the numbers match before you cut over.
Original invoice numbers are preserved
Your accountant’s records still line up with the new system. This matters more than it sounds like it does, and it is the detail most migrations get wrong.
Passwords cannot come across
They are hashed at the source with a scheme that cannot be reversed. Customers set a new password the first time they sign in.
Say this to your customers before the cutover, not after. It is the single most common support spike of a migration, and it is entirely avoidable with one email.
Suggested order
- Dry-run and read the report.
- Fix source data problems — duplicate clients, invoices with no client, domains with no owner.
- Dry-run again until it is clean.
- Freeze the old system.
- Run for real, then verify totals: client count, open invoice value, active services.
- Switch DNS and send the password-reset email.