# WHMCS Migration Service

> Clients, services, domains, invoices and balances moved into WHMCS from Blesta, HostBill, FOSSBilling or custom tools.

Billing platform migration into WHMCS: data mapped, test-imported on staging, reconciled against the old system, then cut over during a short billing freeze.

- **Price:** Starting at $199
- **Billing:** One-time, fixed scope
- **Category:** WHMCS
- **Quote turnaround:** Fixed-price quote within 24 hours
- **Start a project:** https://whmcspilot.com/start-project
- **Details:** https://whmcspilot.com/services/whmcs-migration
- **Last updated:** 2026-11-03

## Overview

A WHMCS migration moves your customer and billing records from another platform into WHMCS, so you can change systems without retyping accounts or losing payment history. Hosting companies and resellers come to us when leaving Blesta, HostBill, BoxBilling or FOSSBilling, ClientExec, WiseCP, Paymenter or a home-grown tool. Small, clean datasets start at $199, and the fixed quote depends on record volume and how unusual the source data is.

## What moves across

DataDetailsClients and contactsCompany details, tax IDs, custom fields and admin notesProducts and servicesBilling cycle, recurring amount, next due date, status, server and usernameDomainsRegistrar, expiry date, renewal price and auto-renew flagInvoices and transactionsPaid and unpaid, with original numbers kept where possibleCredit balancesCarried over and checked client by clientSupport ticketsOptional, because ticket history can be very large

## What usually cannot move

A few things do not transfer cleanly between billing systems. Planning for them beats discovering them on launch day:

- **Passwords.** If the old platform's password hashes are not usable by WHMCS, clients get a password reset email at launch.
- **PayPal subscriptions.** Recurring agreements are tied to the old integration, so customers re-authorize on their next invoice.
- **Stored cards.** Gateway tokens can sometimes be mapped when you keep the same Stripe account. Otherwise customers add a card again.
- **Custom logic.** Pricing rules, scripts or plugins in the old system need a WHMCS equivalent, such as a hook or module, quoted separately.

## How the migration runs

1. **Export.** We get database or API access to the old system and list everything actually in use.
2. **Mapping.** A written map of each field, status, product and billing cycle to its WHMCS equivalent, approved by you before anything is imported.
3. **Test import.** Data goes into a staging copy of WHMCS, and you click through real client accounts to spot anything odd.
4. **Reconciliation.** We compare totals between the two systems: client count, active services, unpaid invoice total, domain count and credit balances. Every difference is explained or fixed.
5. **Cutover.** In an agreed window we pause automation on the old system, import the final data, connect WHMCS to your servers and registrars, and point your billing domain at WHMCS.

Customer websites stay up throughout, because hosting accounts on your cPanel/WHM or other servers are not touched. Services are matched to their existing accounts by username, so WHMCS can suspend and terminate them from the first day. The only interruption is a short pause on new orders while the final import runs.

## The double-billing trap

The costliest migration mistake is leaving both systems' cron jobs running, so customers receive two invoices, or a suspension notice from a platform you have already left. Our cutover checklist switches off invoicing, reminders and suspensions on the old side before WHMCS automation starts, and the old system is kept read-only for reference rather than deleted.

## Moving WHMCS to a new server

Already on WHMCS and only changing hosts? That job is simpler. Files, database, configuration.php and the cron move together, and we confirm that the license, the encryption hash and gateway callbacks all still work on the new address. A straightforward server move usually fits the starting price.

## What we need from you

- Database access or a full export from the old platform, plus admin access to look up records
- A WHMCS license and an empty install, or permission for us to set one up
- A list of the server modules, registrars and gateways the old system talks to
- A preferred cutover window, ideally away from your busiest renewal days

## Timeline

A few hundred clients from a common platform typically take about a week from export to cutover, including the test import and your review. Larger datasets, several brands or a custom source system take longer, and the quote states the planned cutover date.

## Pricing

ScopePriceSmall, clean dataset from a common platform, or a WHMCS server moveFrom $199Large volumes, full ticket history or several brandsFixed quoteCustom or in-house system without a standard exportFixed quote after we review a data sample

Projects above $5,000 are split into three milestones instead of the usual deposit and final payment.

## Platform-specific guides and tools

We have dedicated pages for [Blesta to WHMCS](/services/whmcs-migration-from-blesta) and [HostBill to WHMCS](/services/whmcs-migration-from-hostbill) with more detail on each source. To move individual clients between two WHMCS installs, the [Client Transfer module](/modules/client-transfer) may be all you need, and our other [migration modules](/modules/migration) cover cPanel account moves. Send an export sample or a list of record counts through the [contact page](/contact) and we can size the job before the call.

## What's included

- Export from Blesta, HostBill, BoxBilling, FOSSBilling, ClientExec, WiseCP, Paymenter or custom databases
- Written field and status mapping approved before import
- Clients, contacts, custom fields and notes imported
- Services with billing cycles, due dates and server usernames
- Domains with registrar, expiry and auto-renew settings
- Paid and unpaid invoices, transactions and credit balances
- Test import on a staging WHMCS for your review
- Reconciliation report comparing counts and totals between systems
- Cutover checklist that disables old-system automation first
- Optional ticket history import

## Business outcomes

- Switch billing platforms without retyping a single customer
- Totals are proven to match before the old system is switched off
- Customers are not double-invoiced or wrongly suspended during the move
- Hosting accounts keep running while only the billing layer changes
- Known gaps such as passwords and subscriptions are planned for, not discovered

## Frequently asked questions

### Which billing systems can you migrate to WHMCS?

Blesta, HostBill, BoxBilling, FOSSBilling, ClientExec, WiseCP, Paymenter and custom systems with database or API access. If the data can be exported, it can be mapped.

### Will my customers' websites go down?

No. Hosting accounts stay on your servers untouched, and only billing changes, with a short pause on new orders during cutover.

### Do clients have to reset their passwords?

Sometimes. When the old platform's password hashes cannot be used by WHMCS, clients receive a reset email at launch, and we draft that announcement with you.

### Can invoice numbers stay the same?

Usually, yes. Original numbers go into the WHMCS invoice number field where possible, which helps with tax records, and new invoices continue from the next number.

### What if a record is wrong after launch?

Mapping errors within the agreed scope are corrected free for 14 days after cutover. Because the old system stays read-only, any record can be checked against the source.

### How much does a WHMCS migration cost?

From $199 for a small, clean dataset or a simple server move. Larger or custom migrations get a fixed quote within one business day of the scoping call.
