Paymenter Plus with Migration

Migrate from WHMCS

The WHMCS migration tool included in Paymenter Plus with Migration on Alma Linux 10 moves your WHMCS data into your new Paymenter panel in one command, and holds billing until you have checked everything and are ready.

What moves, and what does not

Moves: clients and their contacts, administrators, products and their categories, configurable options, orders, services and their add-ons, domains, invoices and their items, payments and refunds, tax rules, promotions and support tickets. Your WHMCS invoice numbers are kept, so your clients can find their invoices by the numbers they were sent. Where two WHMCS invoices share a number, or an invoice without a number of its own matches another’s, one of them is given a marked number; the tool lists every one before you import.
Not migrated: saved cards and gateway subscriptions (your clients add their payment method again), registrar connection settings, server and service passwords (encrypted with your WHMCS installation’s own key, so you re-enter them in Paymenter), email templates, and data held by WHMCS add-on modules.
Recurring card payments stop until each client adds a payment method in Paymenter. The tool tells you how many of your clients this affects before anything is imported.

Before you start

Install first. Complete the One-Click Installation and sign in to the admin panel once. Import into a new panel. If the panel already holds clients, products or invoices, the tool stops and lists what is in the way, and changes nothing.
Take a backup of your WHMCS database on your WHMCS server, for example:

mysqldump --single-transaction your_whmcs_database | gzip > whmcs-backup.sql.gz

Copy the backup to your Paymenter instance, for example:

scp whmcs-backup.sql.gz ec2-user@<your-aws-public-ip>:

WHMCS version 8 is supported. The instance needs free disk space of about three times the size of the backup when uncompressed.

Step 1: Run the migration tool

sudo /usr/local/bin/egl-import-whmcs.sh ~/whmcs-backup.sql.gz

The tool checks the backup file, loads it into a temporary database on this instance and runs its checks. Nothing in your panel has changed at this point.
It then shows a summary: what the import will change, what you need to do afterwards, and what is not migrated. Read it.
Type yes to import. Anything else stops, removes the temporary copy and leaves your panel as it was.

Step 2: Let the import finish

The tool backs up your panel’s database first, then imports. A typical WHMCS takes a few minutes.
If your connection drops, the import carries on. Run the same command again to see its progress.
If the import fails, your panel is left as it was before it started.

Step 3: Read the report and finish setting up

In the admin panel, open System, then Migrate from WHMCS. The report compares every count with your WHMCS data and lists what you need to do, for example entering your server passwords and payment gateway keys.
Billing is on hold. Paymenter raises no invoices, sends no reminders and suspends nothing until you start billing, so you can check everything first.

Step 4: Start billing

On the Migrate from WHMCS page, click Start billing. This opens Ready to start billing?
It checks what can be checked for you: that the scheduler is running, that outgoing mail is set up, that your payment gateways and servers have their settings, and that tax rates exist if your WHMCS charged tax. Each item shows OK or Fix, and where to fix it.
It then asks you to confirm what cannot be checked for you, such as cancelling the old gateway subscriptions so nobody is charged twice, and that your domains renew at your registrar.
It also shows what the first billing run will do: how many services it will invoice, suspend or terminate.
The final Start billing button becomes available when every check is OK and every box is ticked.

Important Notes:

Your WHMCS data stays on your instance.
The backup is loaded into a temporary database on this instance and removed when the import ends. Nothing is sent anywhere else. Delete the backup file from the instance when you no longer need it.
Keep WHMCS running until you have checked the report.
The migration does not change your WHMCS installation or its database.
Need a hand?
We also offer migration as a service. Email [email protected] before you start.