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.
Ilinca Bostan7 min readThere is a persistent myth in this category that switching billing platforms means a hand-rolled export and a month of reconciliation. It is mostly false. Every major hosting billing vendor ships an importer, several of them are free, and the best-documented one is published by the incumbent everyone is trying to leave.
What varies is not whether an importer exists. It is which direction it runs, which versions it accepts, and — the part that actually decides your weekend — what it explicitly does not carry across. Checked against vendor documentation on 18 August 2026.
How this was sourced. FluxBilling publishes this comparison and sells one of the products in it. Every claim below comes from the vendor's own documentation, linked at the end, read on 18 August 2026. Importers change between releases; verify version support against your exact versions before planning a migration. This post covers what the tools do, not how well they do it — that varies with your data.
| Destination | Tool | Imports from | Cost |
|---|---|---|---|
| WHMCS | ImportAssist | WHMCS 6.2.x–9.x, Blesta 2.x/3.x/4.1/5.x, ClientExec 5.3–5.9/6.x, HostBill 2016+, CSV (WHMCS 9.x+) | Free to licence holders |
| Blesta | Import Manager plugin | WHMCS 5.2–8.2 | Built in |
| Clientexec | WHMCS Importer plugin | WHMCS (tested against 8.x) | Built in |
| HostBill | Import tool + managed migration | WHMCS, Ubersmith, ClientExec, Blesta | Tool provided; managed migration quoted individually |
| FluxBilling | WHMCS Import, EasyDCIM Import | WHMCS, EasyDCIM | Included on every tier |
The asymmetry is the story. WHMCS's ImportAssist reads from four competing platforms; the competing platforms almost all read only from WHMCS. That is what a category with one incumbent looks like from the inside — everyone builds the road that leads away from the same place, and the incumbent builds four roads leading back.
Published by WHMCS itself and free to all licence holders. It is wizard-driven and supports importing from WHMCS 6.2.x, 6.3.x, 7.x, 8.x and 9.x, Blesta 2.x, 3.x, 4.1 and 5.x, ClientExec 5.3 through 5.9 and 6.x, and HostBill 2016 and later. From WHMCS 9.x onwards it also accepts a CSV file, and it can merge multiple WHMCS installations into one.
It is worth pausing on that list, because it undercuts a claim you will see in a lot of marketing, including from vendors positioning against WHMCS: that leaving is hard and arriving is easy. In this category, arriving at WHMCS is the best-supported path there is.
A built-in plugin, found under Settings > Company > Plugins > Installed, that imports from WHMCS 5.2 to 8.2. The documented data set is broad: payment accounts, admin and staff records, affiliates, calendar, domains, emails, invoices, support departments, taxes, clients, configuration, contacts, currencies, products and packages, services, support tickets, and the knowledge base.
Blesta's documentation is unusually candid about limitations, which is worth reading in full before you commit to a date. The migration must run on a fresh Blesta installation. All source tables should be InnoDB with utf8mb4_unicode_ci collation, and cloning the database before conversion is strongly recommended. Blesta stores ticket codes in an integer column, so non-numeric ticket codes in WHMCS have to be updated first. Legacy password support must be enabled manually or clients cannot log in after the move. PayPal subscriptions will not automatically continue and need manual .htaccess redirects. Imported tickets will not display to newly created staff accounts without department assignment.
None of those are unusual migration problems. What is unusual is that they are written down. Treat that as a quality signal rather than a warning.
A built-in plugin that imports clients, packages, invoices, tickets and servers from WHMCS. It runs either through the admin interface or from the command line, in plugins/import/whmcs, with database credentials passed to a PHP script. The documentation states it has been tested with WHMCS 8.x and may work with other versions.
Two operational notes from the documentation: back up both databases first, and set your default currency before importing, because imported data adopts it.
HostBill provides an import tool for unmanaged, automated migration along with documentation, and separately offers managed migration performed by its own staff, quoted individually after an interview and an installation check. It has publicly documented migrations from WHMCS, Ubersmith, ClientExec and Blesta.
Its own material notes that the tool is built to be as universal as possible but has limitations, particularly where the source WHMCS install depends on third-party modules. That is honest and it generalises: every importer in this post moves core records well and third-party module data badly.
This is the part worth budgeting for, and it is broadly the same across every tool above.
FluxBilling ships two importers — WHMCS Import and EasyDCIM Import — and they are included on every tier: Lite €4.95/month, Starter €24.95/month, Professional €34.95/month and Business €44.95/month. They are not gated to higher plans and there is no migration fee attached to them. Both connect over a direct MySQL connection with an optional SSH tunnel, rather than requiring an API key or an uploaded database dump.
The EasyDCIM importer is the one with no equivalent elsewhere in this post, because it addresses a different problem: providers running a billing platform alongside a separate DCIM product, who want the hardware, rack and IP records to land in the same system as the invoices rather than staying in a second one. If you are on WHMCS plus EasyDCIM today, that pair is what it is built for.
Being even-handed about the rest: our importer reads from two source platforms. WHMCS ImportAssist reads from four and is free with the licence. If you are migrating from Blesta, Clientexec, HostBill or Ubersmith, we do not have a tool for you today and WHMCS does. That is a real gap and it is on our list rather than in our product.
See the WHMCS migration guide, the EasyDCIM migration guide, and current pricing. For the process itself rather than the tooling, our earlier vendor-neutral migration checklist covers sequencing, testing and cutover.
Run the import into a scratch installation first, with a copy of production data, and let it fail there. Reconcile three numbers before you go near a cutover date: total client count, total open invoice value, and total active service count. If those three match, most of the rest is cosmetic. If any of them does not, you have found the problem while it is still free to fix.
Then plan the gateway re-authorisation separately, because it is the one part no importer solves and the one part your customers will notice.
WHMCS, Blesta, Clientexec, HostBill, Ubersmith and EasyDCIM are trademarks of their respective owners. This comparison is published by FluxBilling for evaluation purposes and is not endorsed by, affiliated with, or reviewed by any of them.
Selling hosting across borders means VAT, GST, and US sales tax. Learn how to automate tax compliance with a self-hosted billing platform.
Involuntary churn from failed payments quietly drains recurring revenue. Learn how smart dunning management in a self-hosted billing platform recovers it.
How to choose infrastructure for self-hosted billing: start from requirements, weigh cloud vs on-premise vs hybrid, plan the database, and account for hidden costs.