How to Migrate from WHMCS to FluxBilling

Switching billing platforms sounds intimidating. Years of client data, invoices, support tickets, and service records are tied up in your current system. The fear of losing data or breaking workflows keeps many hosting providers on WHMCS even when they are ready for a change.

FluxBilling addresses this head-on with a built-in WHMCS migration wizard. It connects directly to your WHMCS database and imports everything in a guided, six-step process. No CSV exports, no manual data entry, no third-party tools.

This guide walks you through the entire migration from start to finish.

What Gets Migrated

The migration wizard handles the following data:

• Clients — Names, emails, addresses, phone numbers, company information, and custom fields

• Products — Product groups, individual products, pricing, and configuration options

• Services — Active services, their current status, renewal dates, and assigned products

• Invoices — Invoice history, line items, payment records, and outstanding balances

• Support Tickets — Ticket threads, replies, departments, and status

• Payment History — Transaction records and payment method references

Passwords are handled securely. WHMCS stores passwords with bcrypt hashing — our platform will handle the transfer too. We import the bcrypt hashes directly, so your clients can log in with their existing passwords from day one.

Before You Start

Run through this checklist before beginning the migration:

1. Take a WHMCS database backup — Even though the migration is read-only (it does not modify your WHMCS database), having a backup is good practice

2. Note your WHMCS database credentials — You will need the host, port, database name, username, and password

3. Ensure network access — FluxBilling needs to connect to your WHMCS MySQL/MariaDB database. If it is on a remote server, make sure the port is accessible

4. Set up FluxBilling — Complete the initial FluxBilling setup (admin account, company details, payment gateways) before migrating

5. Migrate EasyDcim — Migrate your devices before you begining the WHMCS migration if you are using it

6. Plan a maintenance window — While the migration itself takes minutes, you will want time to verify data and update DNS if needed

Step-by-Step Migration Process

Open the FluxBilling admin panel and navigate to Settings > WHMCS Migration. The wizard has six steps.

Step 1: Connect to Your WHMCS Database

Enter your WHMCS database connection details:

• Host — The MySQL server hostname or IP (e.g., localhost or db.yourhost.com)

• Port — Usually 3306

• Database — Your WHMCS database name

• Username — A MySQL user with read access to the WHMCS database

• Password — The MySQL user password

Click Test Connection. The wizard validates the connection and verifies it can read the required WHMCS tables. If the connection fails, check your firewall rules and MySQL user permissions.

Step 2: Select Data to Import

The wizard scans your WHMCS database and displays a summary of available data:

• Number of clients found

• Number of products and product groups

• Number of active services

• Number of invoices

• Number of support tickets

You can select which data types to import. Most providers import everything, but you might skip tickets if you are starting fresh with a clean support queue.

Each category shows a count with a checkbox. Select what you need and click Next.

Step 3: Resolve Conflicts

The wizard checks for potential conflicts between your WHMCS data and existing FluxBilling data. Common conflicts include:

• Duplicate email addresses — A client email already exists in FluxBilling

• Product name collisions — A product with the same name already exists

• Currency mismatches — WHMCS uses currencies not configured in FluxBilling

For each conflict, you choose how to handle it:

• Skip — Do not import this record

• Merge — Combine with the existing FluxBilling record

• Rename — Import with a modified name to avoid collision

If there are no conflicts, this step is skipped automatically.

Step 4: Preview the Import

Before any data is written, the wizard shows a detailed preview:

• Exact number of records that will be created for each data type

• Any transformations applied (e.g., status mappings from WHMCS to FluxBilling equivalents)

• Estimated import time

Review the preview carefully. This is your last chance to go back and adjust selections before the import runs.

Step 5: Run the Migration

Click Start Migration. The wizard processes data in batches with a real-time progress bar showing:

• Current data type being imported

• Records processed vs. total

• Any warnings or skipped records

• Elapsed time

The import is transactional. If something fails mid-import, the entire batch rolls back and no partial data is written. You can safely re-run the migration after fixing the issue.

For a typical hosting provider with 200 clients, 50 products, and 1,000 invoices, the migration completes in under 1 minute.

Step 6: Review Results

The final screen shows a complete summary:

• Total records imported per category

• Records skipped (with reasons)

• Any warnings that need attention

• Links to verify imported data in FluxBilling

Click through to the Clients, Products, and Invoices pages to spot-check the imported data.

Post-Migration Checklist

After the migration completes, work through these items:

1. Verify client data — Open a few client profiles and confirm names, emails, and addresses match WHMCS

2. Check service assignments — Ensure active services are linked to the correct products and have the right renewal dates

3. Review invoice history — Open a few invoices and verify line items, amounts, and payment records

4. Test the client portal — Log in as a test client (use the Forgot Password flow) and check that their services and invoices display correctly

5. Configure payment gateways — Set up Stripe, PayPal, or your preferred gateway in FluxBilling. Payment gateway configurations are not migrated since they contain sensitive API keys

6. Update DNS — If you are switching your billing domain, update DNS records to point to FluxBilling

7. Notify clients — Send an email explaining the platform change and the need to reset passwords. FluxBilling's email system can handle bulk sends

Frequently Asked Questions

Can I run both systems in parallel during the transition?

Yes. The migration is read-only on the WHMCS side. You can keep WHMCS running while you verify data in FluxBilling. Once you are satisfied, switch DNS and decommission WHMCS.

What about WHMCS modules and integrations?

WHMCS PHP modules are not compatible with FluxBilling. However, FluxBilling's visual plugin system can replicate most provisioning workflows without code. If you use a specific WHMCS module, check if the equivalent functionality is available as a FluxBilling visual plugin or can be built with the flow editor.

Will my clients notice the change?

The client portal will look different since FluxBilling uses a modern React-based UI. Their service details, invoices, and ticket history will all be there.

Can I migrate from other platforms?

The built-in wizard currently supports WHMCS. For other platforms like Blesta or HostBill, contact the FluxBilling team for assistance with custom migrations.

Is the migration reversible?

The migration does not modify your WHMCS database. Your WHMCS installation remains fully functional throughout and after the process. If you decide to go back, simply switch DNS back to WHMCS.

Ready to Switch?

The migration process is designed to be low-risk and fast. Most providers complete the full migration in under an hour, including verification.

Start your free trial, set up your instance, and run the migration wizard. Your WHMCS data will be intact throughout the process, so there is zero risk in trying.

WHMCS, Blesta, EasyDCIM and HostBill are trademarks of their respective owners. FluxBilling is not affiliated with or endorsed by any of these companies.