Guides

Moving from WHMCS to ClientFence: a practical guide

How the built-in WHMCS import moves your clients, services, invoices and tickets into a fresh ClientFence install, and what to check before and after.

Illustration of client, invoice and ticket cards crossing a glowing bridge from an old platform to a new protected one.

Leaving a billing system you have used for years can feel like a big job. Your clients, their services, years of invoices and every support ticket all live in it. ClientFence, the free and open-source billing and client portal for hosting providers by cPFence, has a WHMCS import built in, so you do not have to start over.

This post walks through the move at a high level: what comes over, what to prepare, the steps, and what to check afterwards. For every detail, keep the full WHMCS import guide open next to you.

What moves over

The import copies a whole WHMCS install into ClientFence. That covers clients and their logins, the catalogue, services and domains, invoices, payments and credit, tickets with attachments, the knowledge base, announcements and email history. Affiliates come over too, with their commissions and visits, and their old aff.php?aff= links keep working. ClientFence also keeps WHMCS’s ids and invoice numbers.

A few things stay behind. Hosting account passwords, product bundles and quotes are not imported. A client whose password cannot be checked in ClientFence signs in with Forgot Password?. Saved cards stay in Stripe, and with the same Stripe account Find saved cards links them to your clients after the import.

Best of all, the import only reads the WHMCS database. Nothing changes in WHMCS, and nothing is emailed, charged or created on a server.

Before you start

A little preparation makes the import go smoothly:

  • A fresh install. Because the import keeps WHMCS’s ids and invoice numbers, it does not start on an install that already has data. Check the server requirements, then install ClientFence.
  • Database access. You need a database user that can read the WHMCS database from the ClientFence server.
  • The encryption key. This is $cc_encryption_hash in WHMCS’s configuration.php. Without it, two-factor sign-in does not come over.
  • Ticket attachments. Copy WHMCS’s attachments folder to the ClientFence server if WHMCS runs elsewhere.
  • Payment gateways. Set up the same payment gateways in ClientFence. If you use PayPal billing agreements, PayTabs or eWAY in WHMCS, the guide explains what to install before the import so those clients and invoices land in the right place.

The steps in brief

The whole import runs from one tab in the admin area, and only Super Administrators can open it.

  1. Go to System → Settings → System and open the Migration tab.
  2. Under Move from, select WHMCS.
  3. Fill in the WHMCS database details and select Save and test.
  4. Select Make the plan. The plan shows what WHMCS holds, what happens to it, and any server checks to fix first.
  5. Select Start the import and keep the page open. If it stops, fix the cause and select Go on with the import.

One thing deserves a close look: imported credit pays a client’s next invoices automatically, so check the credit balances that came over and correct any that look wrong on that client’s Credit Balance tab right after the import.

Prefer the terminal? The guide also lists the command-line version, with separate plan, apply and verify steps.

After the import

When the import finishes, select Check against WHMCS and read the Warnings. Staff accounts and hosting servers come over switched off. Switch them on when you are ready to move over.

A few more things to do on the day you switch:

  • Cancel the PayPal and Stripe subscriptions WHMCS made. They keep charging clients, and their payment notices still go to WHMCS.
  • If you brought PayPal billing agreements over, stop WHMCS’s automatic charges and point PayPal’s IPN URL to ClientFence, so the same agreement is never charged twice.
  • Make sure scheduled tasks run every five minutes, then check that the client sign-in page loads and look at System Health.

Finally, test on your own setup before you go live. Place a test order, pay its invoice and make sure your emails reach clients, so you know ClientFence works the way your business needs.

Ready to move?

Grab the latest release from the download page, then follow the WHMCS import guide step by step. If you get stuck or spot a bug, ask on the ClientFence forum or open an issue in GitHub Issues.

All posts