Migrate WHMCS to a New Server, Done for You

How do you migrate WHMCS to a new server?

You copy WHMCS to the new server and test it there while the old one keeps billing, then move clients over in one short, planned cutover. These are the steps I follow on every move:

1. Check the new server against WHMCS requirements. PHP version and extensions, the ionCube Loader, MySQL or MariaDB settings, SSL and the firewall, before any data is copied.
2. Lower the DNS TTL on the WHMCS domain a few days ahead, so the switch spreads in minutes rather than hours.
3. Copy the files with rsync: the WHMCS folder, custom modules, hooks, templates, attachments and downloads.
4. Copy the database with mysqldump --single-transaction and restore it, then compare table and row counts.
5. Carry over configuration.php, including $cc_encryption_hash. Without the same hash, stored card tokens and encrypted fields cannot be read.
6. Test privately through a hosts-file entry: admin area, client area, a test order, a server module action and a gateway callback.
7. Cut over: freeze changes, take a final dump, restore it, reissue the license for the new IP, recreate the cron job and switch DNS.
8. Watch the first runs: the next cron cycle, the daily invoice run, the first payments and the first emails from the new server.

If you want to do it yourself, my step-by-step WHMCS migration guide has the commands. If you would rather not risk your billing on it, a standard move with these steps is a fixed-price service, priced below.

Migrating WHMCS for hosting companies in the US, Canada and Australia

The cutover runs in your quietest night hours, which fall inside my working day in India, so you do not pay overnight rates and your clients are asleep when billing pauses. Example cutover windows at 2:00 a.m. your time, in November:

Times move by an hour when daylight saving starts or ends where you are. Three things I re-check for these markets after every move:

• Tax rules. US state sales tax rules, Canadian GST, HST, PST or QST rules and Australian GST move with the database; I check the first invoices on the new server carry the same tax lines.
• Country domains. .ca and .au registrations have their own eligibility fields. I run a lookup and a test through the registrar module after the move, because registrar APIs often allow only listed IP addresses.
• Where the new server sits. If your clients or contracts expect data in your country, the new server can be in a US, Canadian or Australian data center; I set it up wherever you choose.

More on working with me from your market: US businesses, Canadian businesses and Australian businesses.

What a WHMCS migration includes

A WHMCS migration is the move of a live billing system to a new server, hosting account or version without losing client data, invoices or recurring billing. The database is only part of it. Most failed moves go wrong in the details around the database.

What usually breaks after a WHMCS move

These are the problems I see most often on migrations I am asked to repair. Each one has a cheap fix if it is found before cutover and an expensive one after it.

If you plan to do the move yourself, my low-downtime WHMCS migration runbook lists every step in order, including the checks above.

Should I move and upgrade WHMCS together?

No, not if you can avoid it. Moving to a new server on the same WHMCS version changes one variable. Upgrading changes many, including database schema, templates and module compatibility. Doing both at once makes failures hard to trace. I move first, confirm the new server is stable for a few days, then upgrade as its own step. The exception is when the old server cannot run a PHP version the new WHMCS release needs. In that case I plan two linked stages inside one project.

Moving to WHMCS from another billing platform

Switching platforms is a data-mapping job rather than a file copy. I export clients, products, services, domains and open invoices from the old system and import them through the WHMCS API or SQL, preserving client IDs where the source allows it. Then I compare client counts, active services and outstanding balances line by line against the old system. Anything that does not match is fixed before you go live. Payment tokens stored by a previous system rarely transfer, so clients may need to re-enter card details. I tell you that up front.

What I need from you

• Admin access to the current WHMCS and SSH or root access to the old and new servers.
• A list of installed addons and custom modules, and who built them if you know.
• A quiet period for the cutover, ideally outside your ticket peak.
• Access to DNS, so the TTL can be lowered and the switch made on time.

What I will not do

I do not move or install nulled, cracked or unlicensed WHMCS copies, and I will not edit WHMCS core files, because those edits disappear on upgrade. Customizations go in the supported hooks, modules and template folders. I also do not delete your old server. It stays as a fallback until you say otherwise.

Cost and timing

A standard move of one WHMCS installation to a new server is a fixed price from $99, and you can order it online. Larger moves are quoted after a short scoping call, or billed at $55 to $65 per hour if you prefer. The main cost drivers are the number of custom modules, the number of integrations that need re-testing, and whether a version upgrade or a platform switch is included. For related work, see WHMCS development, server migration and backup and the WHMCS security audit.