FluxBilling

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.

Mario MarinMario Marin9 min read

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.

What happens when you migrate from Blesta to FluxBilling?

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.

What does the Blesta importer bring across, and what does it leave?

Blesta dataBecomes in FluxBilling
Clients, from each client's primary contactClient accounts with name, company, email, phone, address and preferred currency
Package groupsProduct categories
PackagesProducts with monthly, quarterly, semi-annual and annual prices and the setup fee
ServicesServices with status, billing cycle, recurring amount, next due date, hostname and IP address
InvoicesPaid ones become invoices, the rest become proformas by default, numbered with your prefix plus the Blesta number
TransactionsPayments linked to the invoices they paid
Unapplied creditThe client's credit balance, plus a credit history entry per transaction

What stays behind, and why:

  • Client passwords. Blesta hashes them with its own system key, so every imported client gets a random password and uses Forgot password before the first sign-in.
  • Saved cards. Blesta encrypts them with the same key, so automatic payment starts again only when the customer adds a payment method.
  • Staff, extra contacts, support tickets, coupons and configurable option definitions. Option renewal prices are still added into each service's recurring amount.
  • Services on terms FluxBilling does not bill, such as 2 or 3 years, 2 months, weekly or daily. Each is listed in the errors with its term and amount for you to add by hand.

The import sends no emails. Telling customers about the move is your job, which is usually what you want.

How do you prepare FluxBilling before the import?

  1. Set your base currency and add every currency Blesta uses. Package prices are read in your base currency. A package with no price in it is imported with another currency's prices, unconverted, and flagged in the errors.
  2. Set your invoice and proforma prefixes in Billing Settings. An imported document number is your prefix plus the Blesta number, and it never changes later.
  3. Install your payment gateway plugins so the wizard can map Blesta gateways to them. See Payment Gateways.
  4. Enable your provisioning plugins so Blesta modules can be mapped. Products whose module stays unmapped import without a plugin.
  5. Download a database backup from Settings, Security. A cancelled run keeps what it already wrote, and restoring the backup is the clean way back. See Security Settings.

This is how common Blesta modules and gateways line up with FluxBilling plugins at the time of writing (November 2026):

In BlestaIn FluxBilling
cPanel and WHM, PleskcPanel/WHM and Plesk plugins
Proxmox, VirtFusion, PterodactylProxmox VE, VirtFusion and Pterodactyl plugins
DirectAdmin, Enhance, TCAdmin and other modulesNo FluxBilling plugin: the products import without one
Stripe, PayPal, Authorize.net, GoCardlessThe matching gateway plugins. Stripe is preselected when its plugin is installed, check the others
Other gateways and manual payment typesAny enabled gateway, or Manual (record only)
Blesta in-house creditImported 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.

How do you give FluxBilling read-only access to Blesta?

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.

How do you run a rehearsal import?

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.

  1. On Data Selection, keep all six types ticked: Clients, Products, Services, Invoices, Payments and Credits.
  2. Leave Unpaid, Proforma, Draft and Void ticked so open documents become proformas. In FluxBilling the invoice is the document issued on payment.
  3. Map each Blesta module to a plugin and each payment method to a gateway.
  4. Read the Preview. Clients, products and invoices that already exist are skipped and linked, services, payments and credits are created.
  5. Start the run, then download the Report from the Results step. It holds the full error list.

The errors that need a decision before cut-over day:

  • No primary contact email address or a duplicate email: fix the client in Blesta.
  • Billed every 2 years and other unsupported terms: decide whether to move those customers to annual billing or bill them by hand.
  • Prices copied as-is: edit those products' prices in your base currency.
  • Credit not imported in a second currency: a FluxBilling balance holds one currency, so settle the rest with the customer.

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.

How do you plan the cut-over?

  1. Email customers a few days ahead with the new client area address, the password reset step and a request to add a card after the move.
  2. Freeze Blesta. Disable its cron job, which runs every minute and handles tasks such as Create Invoice, Auto Debit, Payment Reminders and Suspend Services, so Blesta stops billing in parallel.
  3. Run the full import once on the restored panel. Because a rerun never updates records, an import taken before the freeze would miss invoices paid since.
  4. Point gateway webhooks at FluxBilling and switch each gateway on.
  5. Send the announcement and watch sign-ins and new payment methods over the first days.

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.

What should you check after the move?

  • Totals: client, active service and open document counts against Blesta, and total credit per currency.
  • Numbering: when Blesta numbers are plain numbers, your next invoice and proforma numbers move past the highest imported one. Check the first new document.
  • The first renewal run: pick a day when several services renew and confirm the proformas, amounts and due dates.
  • Provisioning: suspend and unsuspend a test service on each plugin.
  • Payments: confirm a card payment reaches FluxBilling through the webhook, not just the gateway dashboard.

For the wider project, our vendor-neutral migration checklist covers discovery, communication and reconciliation.

Questions people ask about leaving Blesta

Can I migrate from Blesta without losing invoice history?

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.

Will my customers have to re-enter their cards?

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.

Can I run the import more than once?

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.

Does the importer work with old Blesta versions?

It reads Blesta 3.0 and newer. An older database is refused at the Connection step with a message to upgrade Blesta first.

Where to go next

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.

Tagged
migrate from blestablesta migrationswitch from blestablesta to fluxbillingblesta importleave blestablesta database migration
Written by
Mario Marin
Mario Marin
View all posts →