# WHMCS Migration from Blesta

> Blesta to WHMCS via the official ImportAssist import, with custom fields, options and coupons it skips moved by script.

Blesta to WHMCS migration: ImportAssist database import, the missing data moved by script, servers relinked, totals reconciled and a planned cutover.

- **Price:** Starting at $199
- **Billing:** One-time, fixed scope
- **Category:** WHMCS
- **Quote turnaround:** Fixed-price quote within 24 hours
- **Start a project:** https://whmcspilot.com/start-project
- **Details:** https://whmcspilot.com/services/whmcs-migration-from-blesta
- **Last updated:** 2026-11-05

## Overview

Moving from Blesta to WHMCS has an official starting point: ImportAssist, a free WHMCS addon that reads a Blesta database directly and creates the matching WHMCS records. It does not carry everything across, and the gaps are where Blesta migrations go wrong. We run the import for Blesta users switching to WHMCS, move the missing pieces by script, and reconcile the result before you switch, starting at $199. Coming from a different platform? HostBill has [its own page](/services/whmcs-migration-from-hostbill), and other sources are covered by general [WHMCS migration](/services/whmcs-migration).

## What ImportAssist moves from Blesta

The WHMCS documentation lists Blesta 2.x, 3.x, 4.1 and 5.x as supported sources, with different coverage per version:

DataBlesta 3.x, 4.1, 5.xBlesta 2.xClients, contacts, product addonsImportedImportedPackages and package groups (become products and product groups), with pricingImportedImportedServices, invoices, invoice items, transactionsImportedImportedSupport departments and ticketsImportedImportedTicket replies and staff ticket notesImportedNot importedDomains and currenciesImportedNot importedCustom client fields and values, client groups, client notesNot importedNot importedPackage options (configurable options), service addons, couponsNot importedNot importedServers (Blesta module rows), saved payment methods, user loginsNot importedNot imported

The bottom three rows are our main work. Custom fields and package options are often where Blesta stores the details that matter, such as a VAT number, an IPTV line type or a VPS location, so losing them is not acceptable even when the client list looks complete.

## How the migration runs

1. **Inventory.** We list your packages, package options, custom fields, coupons, module rows and gateways, and note which Blesta modules and plugins you actually use.
2. **Target install.** A clean WHMCS on 9.x with PHP 8.2 or later is the usual target, since WHMCS lists 8.13's end of life as December 31, 2026. If a module you depend on is not ready for 9.x, 8.13 on PHP 8.1 or later still works for now.
3. **Staging import.** ImportAssist is uploaded to /modules/addons, activated at Configuration &gt; System Settings &gt; Addon Modules, and pointed at a copy of the Blesta database through Addons &gt; ImportAssist for WHMCS &gt; Select Database Import. The Blesta database must accept a connection from the WHMCS server, which usually means a remote MySQL grant and a firewall rule.
4. **Gap scripts.** We recreate custom fields, client groups and configurable options in WHMCS, then fill in each client's and service's values from the Blesta tables. Coupons become WHMCS promotions.
5. **Servers.** Each Blesta module row becomes a server at Configuration &gt; System Settings &gt; Servers, and services are attached to it by username and domain, so WHMCS can suspend, unsuspend and terminate from day one.
6. **Reconciliation.** Client count, active services, open invoice total, domain count and credit balances are compared between Blesta and WHMCS, and every difference is explained.
7. **Cutover.** Blesta's automation tasks are stopped first, a final import runs, and WHMCS takes over billing on the agreed day.

## Blesta habits that need a decision

- **Multiple companies.** One Blesta install can run several companies. WHMCS has one company per install, so you choose between separate WHMCS installs or merging brands.
- **Passwords.** User logins are not in the ImportAssist list for Blesta, so customers should expect a password reset email at launch. We draft that message with you.
- **Cards.** Saved payment methods do not transfer. If you keep the same Stripe account, existing Stripe customers can sometimes be linked by script. Otherwise customers add a card when paying their first WHMCS invoice.
- **Plugins.** Custom Blesta plugins or events need a WHMCS hook or module, quoted separately through [hooks development](/services/whmcs-hooks-development).

## What to send us

- Blesta admin access and a recent database dump, or read access to the live database
- A WHMCS license and server, or permission for us to set them up
- Your registrar, gateway and server credentials for reconnecting in WHMCS
- A cutover date away from your heaviest renewal days

## Migration pricing

ScopePriceBlesta 3.x to 5.x, small dataset, standard modules: ImportAssist run, server relinking, reconciliation, cutoverFrom $199Custom fields, package options, client groups and coupons moved by scriptFixed quote by record countBlesta 2.x, multi-company installs or custom pluginsQuoted once we inspect the data

Still deciding whether to switch at all? Our [WHMCS vs Blesta vs HostBill vs Upmind comparison](/blog/whmcs-vs-blesta-vs-hostbill-vs-upmind) sets out the trade-offs, and the [migration modules](/modules/migration) help with moves between WHMCS installs and cPanel servers after you arrive.

## What's included

- Inventory of Blesta packages, options, custom fields, coupons, module rows and gateways
- Clean WHMCS target on 9.x (PHP 8.2+) or 8.13 (PHP 8.1+)
- Official ImportAssist database import run on staging first
- Custom client fields and values recreated and filled by script
- Package options rebuilt as configurable options with each service's selections
- Client groups, client notes and coupons moved across
- Blesta module rows recreated as WHMCS servers and services relinked
- Reconciliation of clients, services, invoices, domains and credit balances
- Blesta automation stopped before WHMCS billing starts
- Password reset and card update messages drafted for customers

## Business outcomes

- Data that ImportAssist skips, such as custom fields, is not lost
- WHMCS can manage existing hosting accounts from the first day
- Totals are checked against Blesta before customers see WHMCS
- Customers are told in advance about password resets and card updates
- You land on a supported WHMCS version with a clear upgrade path

## Frequently asked questions

### Does WHMCS have an official Blesta importer?

Yes. ImportAssist is a free WHMCS addon that imports from Blesta 2.x, 3.x, 4.1 and 5.x databases. It skips custom fields, package options, coupons, servers and saved cards, which we move separately.

### Will my Blesta custom fields come across?

Not through ImportAssist. We recreate the fields in WHMCS and copy each client's values from the Blesta database by script, then spot-check them with you.

### Do customers need new passwords?

Plan for it. ImportAssist does not list user logins for Blesta, so customers receive a reset email at launch, which we write with you.

### Can I keep running Blesta during the migration?

Yes. Blesta keeps billing while we import into a staging WHMCS. Its automation is stopped only at cutover, just before the final import.

### Should I migrate to WHMCS 8.13 or 9?

Usually 9.x on PHP 8.2 or later, because WHMCS lists 8.13's end of life as December 31, 2026. We use 8.13 only when a module you rely on is not yet ready for 9.x.

### How much does a Blesta migration cost?

From $199 for a small Blesta 3.x to 5.x dataset. Larger datasets, custom fields and plugins get a fixed quote, with three milestones on projects over $5,000.
