WHMCS Migration Service

This package migrates WHMCS to a new server, or brings your clients, services and invoices into WHMCS from another billing platform, with everything tested on the new machine while the old one keeps billing until a short, planned cutover. It is for businesses moving to faster or cheaper infrastructure, leaving a host that is slow or closing, or switching from Blesta, ClientExec, HostBill or a spreadsheet.

A server move, step by step

It starts with an audit of your WHMCS and PHP versions, extensions, custom modules, hooks, gateways and cron schedule, so you see the risks before work begins. I prepare the new server with the right PHP version, ionCube Loader and database settings, copy files with rsync and the database with mysqldump --single-transaction, and compare table and row counts. configuration.php comes across with its $cc_encryption_hash, since encrypted fields cannot be read without it.

• Testing happens through a hosts-file entry, so real clients never see the test install.
• DNS TTL is lowered a few days ahead, so the switch spreads in minutes.
• At cutover I take a final dump, reissue the license for the new IP, recreate the cron and watch the first invoice run and payments.

Moving from another billing platform

Business imports clients, products, active services, domains and open invoices, then checks balances and next due dates on sample accounts, because wrong due dates make WHMCS bill early or never. Premium adds invoice and transaction history, ticket history where the old system exports it, and stored gateway tokens where the gateway allows them to move.

Good to know

The old server stays untouched as a fallback until you approve removing it. A license bought from the host you are leaving stays with that host, so you would need a new one. Cutovers run in your quietest night hours. The full method is on the WHMCS migration page.