Move from FOSSBilling to ClientFence
The FOSSBilling import copies your FOSSBilling clients, products, services, domains, billing and tickets into ClientFence. It reads FOSSBilling’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 FOSSBilling, and nothing is emailed, charged or created on a server.
What you need
Section titled “What you need”- A fresh install. The import keeps FOSSBilling’s invoice numbers, so it does not start on an install that already has data.
- A database user that can read FOSSBilling’s database from your ClientFence server. Read
access (
SELECT) is enough. FOSSBilling’s database details are in itsconfig.php. - 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 FOSSBilling. Under Import from FOSSBilling, 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 FOSSBilling and keep the page open. If it stops, fix the cause and select Go on reading FOSSBilling.
- 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 FOSSBilling 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, VAT number, group, currency, notes, credit balance and its history; product categories, products and their prices and setup fees; add-ons and the products that offer them; upgrade paths; domain extensions with their registration, renewal and transfer prices; orders as services and domains with their renewal price and due date, and add-on orders as add-ons of their service; invoices and their lines; payments; tickets with their replies and staff notes; support departments; and tax rules. Each client’s language comes over.
Clients keep their FOSSBilling passwords.
FOSSBilling puts a payment in the client’s credit balance before it pays the invoice. So a payment for an invoice that is still unpaid stays in the client’s credit, and the invoice comes over unpaid.
Not imported (the warnings name what was found):
- Promotions.
- Hosting servers and hosting plans. Add them again, then link the hosting services to them.
- Gateway subscriptions.
- Ticket attachments.
- Staff. Their replies keep their names.
- Prices and orders billed weekly or every 4 or 5 years: ClientFence bills 1, 3, 6, 12, 24 or 36 months, or once.
- License and download settings. Those products come over as plain products.
When you move over, stop FOSSBilling’s cron, so clients are not billed or emailed twice.
From the console
Section titled “From the console”For a large FOSSBilling install, run the same steps as the site user once the details are saved:
php console.php clientfence:whmcs-import fossbillingphp 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 FOSSBilling again from the start.

