Skip to content

Move from Blesta to ClientFence

The Blesta import copies your Blesta clients, packages, services, domains, billing and tickets into ClientFence. It reads Blesta’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 Blesta, and nothing is emailed, charged or created on a server.

  • A fresh install. The import keeps Blesta’s ids and invoice numbers, so it does not start on an install that already has data.
  • A database user that can read Blesta’s database from your ClientFence server. Read access (SELECT) is enough.
  • Blesta’s system key: Blesta.system_key in Blesta’s config/blesta.php. With it, clients sign in with their Blesta passwords. Without it, they set a new one with Forgot Password?.
  • Blesta’s ticket attachments folder, if Blesta runs on another server: copy its support_manager_files folder (inside Blesta’s uploads folder, Settings → System → General) to your ClientFence server. Attachments are copied only from that folder.
  • PHP’s pdo_sqlite extension, which most PHP builds include.
  • The same payment gateways set up here.
  1. Go to System → Settings → System and open the Migration tab (Super Administrators only).
  2. Under Move from, select Blesta. Under Import from Blesta, enter the database host, port, name, username and password, the System key and, if needed, the Attachments folder, 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.
  3. Select Read Blesta and keep the page open. If it stops, fix the cause and select Go on reading Blesta.
  4. 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.
  5. Select Start the import and keep the page open, then Check against Blesta to compare the counts.

Clients with their primary contact, phone, tax ID, group, currency, notes and credit balance; billing and other contacts (without a login); package groups, packages and their prices and setup fees; domain extensions with their registration, renewal and transfer prices; services and domains with their renewal price and due date; invoices and their lines; payments and unapplied payments as credit; tickets with their replies, staff notes and attachments; and tax rates. Each client’s language comes over, and package and package group names and descriptions in other languages ClientFence ships come over as their translations. Packages of an add-on group become addons of the packages in its parent groups, and add-on services come over as add-ons of their service, with their own price, billing cycle and due date. Affiliates of the Order System come over with their referrals, pending and matured commissions, approved payouts and visits; each keeps its commission, its available balance and its code, so order/forms/a/ links keep working. Open payout requests are listed in the warnings instead.

Each client’s password works on its first sign-in and is then saved again the ClientFence way. A client marked as fraud in Blesta comes over as closed. A cancellation set for a later date waits under Cancellation Requests, so the service does not renew.

Not imported (the warnings name what was found):

  • Saved cards and bank accounts. Blesta encrypts them with its own key. With the same Stripe account, Find saved cards links Stripe cards to the clients after the import: see Saved cards.
  • Two-factor sign-in. Clients who used it set it up again.
  • Coupons, recurring invoices, package options and custom client fields.
  • Refunded payments.
  • Staff. Their replies keep their names.
  • Prices billed in days, weeks or other terms that ClientFence does not bill (1, 3, 6, 12, 24 or 36 months, or once), and services that renew on such a term. A package that renews and also has a one-time price keeps only its renewing prices.
  • Encrypted client notes.

Only Blesta’s first company is read.

ClientFence charges one tax rate to every item of a taxable client. If Blesta did not tax some packages or domains, tax comes over switched off: check the rules under System → Tax Rules, then turn on Enable Tax Support before new invoices are made. See Taxes. Imported invoices keep the tax Blesta charged.

When you move over, stop Blesta’s cron, so clients are not billed or emailed twice.

For a large Blesta install, run the same steps as the site user once the details are saved:

Terminal window
php console.php clientfence:whmcs-import blesta
php console.php clientfence:whmcs-import plan
php console.php clientfence:whmcs-import apply
php console.php clientfence:whmcs-import verify

Add --restart to the first command to read Blesta again from the start.