How to Migrate from Blesta to FluxBilling: A Step-by-Step Guide
A step-by-step Blesta migration: read-only database access, module and gateway mapping, a rehearsal you can roll back, the cut-over plan and what to check after the move.
A step-by-step Blesta migration: read-only database access, module and gateway mapping, a rehearsal you can roll back, the cut-over plan and what to check after the move.
To migrate from Blesta to FluxBilling, you point FluxBilling's built-in Blesta importer at your Blesta MySQL database with a read-only user, map your modules and gateways, and import clients, packages, services, invoices, payments and credit. Blesta is never changed. Passwords, saved cards and tickets do not come across, so customers reset their password and add a card again.
How this was sourced. FluxBilling publishes this guide and makes the importer it describes. The steps follow our Blesta Migration documentation and the importer's code as of 16 November 2026. Blesta facts (version 6.0.4, licence terms, cron and database requirements) were read on blesta.com and docs.blesta.com the same day.
The importer is a five-step wizard under Settings, Migration Tools, Blesta Migration: Connection, Data Selection, Preview, Progress and Results. It reads the Blesta database directly, optionally through an SSH tunnel, and opens every connection as a read-only session. It works with databases from Blesta 3.0 onwards, including the current 6.x releases.
Two rules shape the whole plan. First, only a super administrator can run it, because the wizard holds another system's database password. Second, the importer never overwrites a record. It remembers every Blesta record it brought across, so a second run adds what is new and skips the rest. That makes reruns safe, and it also means a record that changed in Blesta after a run is not updated by the next one.
| Blesta data | Becomes in FluxBilling |
|---|---|
| Clients, from each client's primary contact | Client accounts with name, company, email, phone, address and preferred currency |
| Package groups | Product categories |
| Packages | Products with monthly, quarterly, semi-annual and annual prices and the setup fee |
| Services | Services with status, billing cycle, recurring amount, next due date, hostname and IP address |
| Invoices | Paid ones become invoices, the rest become proformas by default, numbered with your prefix plus the Blesta number |
| Transactions | Payments linked to the invoices they paid |
| Unapplied credit | The client's credit balance, plus a credit history entry per transaction |
What stays behind, and why:
The import sends no emails. Telling customers about the move is your job, which is usually what you want.
This is how common Blesta modules and gateways line up with FluxBilling plugins at the time of writing (November 2026):
| In Blesta | In FluxBilling |
|---|---|
| cPanel and WHM, Plesk | cPanel/WHM and Plesk plugins |
| Proxmox, VirtFusion, Pterodactyl | Proxmox VE, VirtFusion and Pterodactyl plugins |
| DirectAdmin, Enhance, TCAdmin and other modules | No FluxBilling plugin: the products import without one |
| Stripe, PayPal, Authorize.net, GoCardless | The matching gateway plugins. Stripe is preselected when its plugin is installed, check the others |
| Other gateways and manual payment types | Any enabled gateway, or Manual (record only) |
| Blesta in-house credit | Imported as credit spent, not as money received |
When a service's Blesta module fields hold a server ID, it is stored with the service for the mapped plugin. Test one service of each type in the client area before you rely on that link.
Create a MySQL user that can only read the Blesta database. SELECT is all the importer needs. On the Blesta database server, as an example:
CREATE USER 'flux_import'@'203.0.113.10' IDENTIFIED BY 'a-long-random-password';
GRANT SELECT ON blesta.* TO 'flux_import'@'203.0.113.10';
Replace the example address with the address your FluxBilling server connects from, and the database name with yours. If MySQL only listens locally, which is common on a single Blesta server, tick Use SSH Tunnel in the wizard and enter an SSH login instead. The MySQL host is then the address as the SSH server sees it, usually its loopback address.
Click Test. A green banner shows the Blesta version and the number of clients, products, invoices and services. If the database holds several Blesta companies, the wizard asks you to choose one. A FluxBilling panel is one company, so each extra company, the ones Blesta sells as addon companies, goes into its own panel.
There is no mode that imports nothing, so the rehearsal is a real run that you can roll back with the backup you just downloaded.
The errors that need a decision before cut-over day:
Open a few client accounts and compare them with Blesta: next due dates, recurring amounts, open proformas and credit. When you are satisfied, restore the backup so the real import starts clean.
Keep the Blesta database. Blesta's pricing page says monthly licences can be cancelled at any time with the data staying on your server, and owned licences never expire. Answer open Blesta tickets there or recreate them by hand, since tickets are not imported.
For the wider project, our vendor-neutral migration checklist covers discovery, communication and reconciliation.
Yes. Invoices in every state, their line items and the payments against them are imported, numbered with your prefix plus the Blesta number. Totals are copied as Blesta stored them, and a tax included in prices becomes its own line.
Yes. Blesta encrypts saved cards with its own system key, so they cannot be carried over. Customers add a payment method in the client area after the move.
Yes. A rerun creates only what is new and skips what was already imported. It never updates a record, so for the final move restore your backup and import once after freezing Blesta.
It reads Blesta 3.0 and newer. An older database is refused at the Connection step with a message to upgrade Blesta first.
Every FluxBilling tier includes the Blesta importer. Compare the two products on FluxBilling vs Blesta, see why hosts choose FluxBilling as a Blesta alternative, or check our Blesta pricing breakdown before your next renewal. If you are still choosing between platforms, our FOSSBilling vs WHMCS comparison covers the free and the paid default.
Blesta, WHMCS, FOSSBilling, cPanel, Plesk, Proxmox, VirtFusion, Pterodactyl, DirectAdmin, Enhance, TCAdmin, Stripe, PayPal, Authorize.net and GoCardless are trademarks of their respective owners. FluxBilling is not affiliated with or endorsed by any of them. Blesta details are as published on 16 November 2026 and may change.
Every Blesta licence price as published on 2 November 2026, monthly, owned and lifetime, plus add-ons, paid services, what each option costs over three and five years, and how it compares with WHMCS.
WHMCS prices by client count and its self-hosted ladder stops at 1,000. Blesta is flat and unlimited, and will sell you the licence outright. A sourced comparison, including the gap neither one fills.
A dollar a month separates them on price, so the decision is licensing terms. Blesta will sell you the licence outright; Clientexec will let you try it first. What else differs, and what neither one does.
Every major hosting billing vendor ships an importer, and the best-supported one belongs to the incumbent. Here is what each tool reads, what it costs, and the five things none of them carry across.
Blesta is a paid, source-available licence with 100+ integrations and vendor support. Paymenter is free MIT software you run and patch yourself. Cost, modules, WHMCS import and self-hosting effort compared.