Move from Paymenter to ClientFence
The Paymenter import copies your Paymenter clients, products, services, billing and tickets into ClientFence. It reads Paymenter’s database directly and only reads it. It saves what it reads in a private file on your server, then imports that file with the same steps as the WHMCS import. Nothing changes in Paymenter, and nothing is emailed, charged or created on a server.
What you need
Section titled “What you need”- Paymenter 1.4 or newer. Update Paymenter first if it is older.
- A fresh install. The import keeps Paymenter’s invoice numbers, so it does not start on an install that already has data.
- A database user that can read Paymenter’s database from your ClientFence server. Read access
(
SELECT) is enough. Paymenter’s database details are in its.envfile. - PHP’s
pdo_sqliteextension, which most PHP builds include. - The same payment gateways set up here.
Run the import
Section titled “Run the import”- Go to System → Settings → System and open the Migration tab (Super Administrators only).
- Under Move from, select Paymenter. Under Import from Paymenter, enter the database host, port, name, username and password, then select Save and test. If a plan was made from another system, saving deletes it after you confirm, and you make a new one.
- Select Read Paymenter and keep the page open. If it stops, fix the cause and select Go on reading Paymenter.
- Select Make the plan. It shows what was read and lists the server checks to fix. Check Clients with the most credit in the plan: imported credit pays the client’s next invoices automatically, so correct a wrong balance on the client’s Credit Balance tab right after the import.
- Select Start the import and keep the page open, then Check against Paymenter to compare the counts.
What comes over, and what does not
Section titled “What comes over, and what does not”Clients with their address, phone, currency, notes and credit balance; categories, products and their prices and setup fees for each billing period; upgrade paths; priced configurable options with their values; services with their options, price, due date and cancellation requests; invoices and their lines; payments; tickets with their replies; support departments; and tax rates.
Clients keep their Paymenter passwords.
An invoice paid from the client’s credit comes over as paid with credit, not as money received.
Not imported (the warnings name what was found):
- Coupons. A service with a coupon comes over at its discounted price.
- Servers. Add them again, then link the services to them.
- Saved payment methods and gateway subscriptions. Those services get renewal invoices.
- Two-factor sign-in. The client signs in with the password until it sets two-factor up again.
- Ticket attachments.
- Staff. Their replies keep their names.
- Text and number options. The answers your clients gave are kept in the service’s notes.
- Payments still processing. Check them at the gateway.
- Prices and services billed hourly, daily, weekly or every 4 years or more: ClientFence bills 1, 3, 6, 12, 24 or 36 months, or once.
When you move over, stop Paymenter’s cron, so clients are not billed or emailed twice.
From the console
Section titled “From the console”For a large Paymenter install, run the same steps as the site user once the details are saved:
php console.php clientfence:whmcs-import paymenterphp console.php clientfence:whmcs-import planphp console.php clientfence:whmcs-import applyphp console.php clientfence:whmcs-import verifyAdd --restart to the first command to read Paymenter again from the start.

