WHMCS to Blesta: The Complete, Stress-Free Migration Guide

Moving from WHMCS to Blesta is very doable, and Blesta includes a tool built for it. The import itself is often the quick part. The real work is checking your integrations first, testing the result and planning the switch so customers barely notice. This guide walks through the whole WHMCS to Blesta move, from the first checklist to turning off WHMCS, with the details that are easy to miss.

If you’re still deciding whether to switch at all, start with our WHMCS vs Blesta comparison.

Why Hosts Move From WHMCS to Blesta

The reasons we hear most are cost, with WHMCS pricing rising as client numbers grow, and code: much of Blesta’s source is open to read, which makes it easier to customize and debug. Others simply prefer Blesta’s cleaner staff area. Whatever your reason, a WHMCS to Blesta migration goes best when you treat it as a project with stages, not a weekend button-press.

Step 1: Check Everything You Rely On Exists in Blesta

Make a list of every integration in your WHMCS install and find the Blesta equivalent for each:

• Control panels: cPanel, Plesk, DirectAdmin, VPS platforms
• Domain registrars
• Payment gateways, and whether saved cards can come across
• Addons your clients use, such as a forum or tools. Ours exist for both: Client Forum for Blesta and Caddie for Blesta.
• Custom hooks, which become Blesta events inside a small plugin

If something you depend on has no Blesta version, solve that before going any further. It may need a custom module or plugin; our guides to Blesta module development and Blesta plugin development explain what’s involved.

What Becomes What in Blesta

Most WHMCS ideas have a direct match in Blesta, just with a different name. Knowing the mapping makes the rest of the WHMCS to Blesta move much easier to follow:

Step 2: Set Up a Fresh Blesta Install

Blesta’s Import Manager documentation is clear that migrations must run on a fresh Blesta installation. Install Blesta on a test address first, such as billing-new.example.com, and don’t add clients or packages by hand before importing. Take a backup of the empty install so you can reset it and import again if you need to. Use the same PHP version you plan to run in production, and install the ionCube Loader Blesta needs, so the test behaves exactly like the real thing. If you’re also moving to a new server, build and test Blesta on that new server from the start, so you only switch once and don’t have to move Blesta again later.

Step 3: Run Import Manager

1. In the new Blesta, go to Settings > Company > Plugins > Available and install Import Manager.
2. Click Manage on it under the Installed tab and choose WHMCS.
3. Enter your WHMCS database details and the CC Encryption Hash from your WHMCS configuration.php (the WHMCS documentation explains where it lives), then start the import.

For a large install, Blesta calls the command-line method the most reliable, because it can’t time out the way a browser can. Run it from your Blesta folder:

php index.php admin/plugin/import_manager/admin_manage_plugin/index

Check the Import Manager docs for the WHMCS versions it supports and its full list of options before you start. If your WHMCS is much older than the supported versions, update it first, then run the WHMCS to Blesta import.

Step 4: Test the Imported Data

Don’t trust a successful message on its own. Pick a handful of real clients, including your most complicated ones, and compare them side by side in WHMCS and Blesta:

• Contact details and account balances
• Services, their packages, prices and next due dates
• Open and recent invoices
• Domains and their expiry dates
• That services are linked to the right servers, so suspensions will work

Then connect your modules (see our Blesta cPanel guide), set up gateways, and place a test order. If anything is badly wrong, restore the empty backup and import again. You can repeat the WHMCS to Blesta test import as many times as you need.

What Doesn’t Move Automatically

Import Manager moves your data, not your setup. Plan time to redo these by hand during a WHMCS to Blesta migration:

• Email templates. Blesta uses its own tags, so rewrite welcome, invoice and reminder emails in Blesta’s style.
• Your client area design. WHMCS themes don’t work in Blesta. Our client area customization guide shows how to brand Blesta safely.
• Custom code. Hooks and addon modules need rewriting as Blesta plugins.
• Automation settings. Check invoice days, late fees, reminders and suspension timing match how you ran WHMCS.
• Gateway and module credentials. Re-enter API keys in Blesta and test each one.

Step 5: Plan the Switchover

1. Pick a quiet day, away from your main invoice run.
2. Tell clients a few days ahead: the new client area address, and that they’ll need to reset their password if passwords don’t carry over in your setup.
3. Turn off the WHMCS cron so it stops sending invoices and suspending services.
4. Reset the test Blesta and run the final import from the live WHMCS data.
5. Turn on the Blesta cron and point your website’s links and payment provider webhooks at Blesta.
6. Uninstall Import Manager once you’re happy, as Blesta’s docs recommend.

Keep WHMCS in read-only form for a few months. You’ll want to look things up in it.

Telling Clients About the Move

Clients worry when their billing changes without warning. A short, clear email a few days ahead keeps support quiet. Say what’s changing, when, and what they need to do, and keep it to a few lines. For example:

We’re moving to a new billing system on Tuesday. Your hosting won’t be affected. From Tuesday, log in at billing.example.com. You may need to reset your password the first time, and if you pay by card, you may be asked to add it again before your next invoice.

Send a short reminder on the day, and pin a notice in your client area for the first week. Clear communication is the cheapest part of a WHMCS to Blesta migration and the one that clients remember most.

Keep Old Links Working

Clients have bookmarks, old emails and saved links pointing at your WHMCS address. If Blesta lives at a new address, add redirects from the main WHMCS pages, such as the client area login and the cart, to their Blesta equivalents. A short, friendly notice on the old WHMCS login page also helps anyone who lands there. This small step saves a lot of “I can’t log in” tickets after a WHMCS to Blesta switch.

Saved Cards: Plan for Re-Entry

Whether saved cards come across depends on your gateway. Cards stored as tokens at Stripe or a similar gateway may work in Blesta with the same gateway account; cards stored another way often can’t be moved. Assume some customers will need to add their card again, and send a friendly reminder before their next invoice.

Your First Month on Blesta

Watch the first full billing cycle closely. Check each day’s invoices against what WHMCS would have sent, confirm suspensions and unsuspensions reach your servers, and read the module log for errors. Keep a short list of anything clients ask about; those questions become your knowledge base articles. Most WHMCS to Blesta problems show up in the first cycle, so by the end of the month you’ll know the move is done.

Common WHMCS to Blesta Mistakes

• Importing into a Blesta you already set up. Import Manager needs a fresh install, so do your setup after the import, not before.
• Leaving both crons running. Two systems billing the same clients leads to double invoices and angry emails.
• Forgetting gateway webhooks. If payment callbacks still point at WHMCS, payments won’t mark Blesta invoices as paid.
• Skipping the test import. A practice run shows problems while there’s still no pressure to fix them.

Your WHMCS to Blesta Checklist

• Every integration has a Blesta equivalent or a plan.
• Fresh Blesta installed and backed up while empty.
• Test import done and checked against real clients.
• Modules, gateways, email templates and branding set up and tested.
• Clients told, switch day chosen, redirects ready.
• WHMCS cron off, final import run, Blesta cron on, webhooks moved.

Frequently Asked Questions

How long does a WHMCS to Blesta migration take?

The import itself can take minutes to hours depending on size. Allow a week or two in total for checking integrations, testing and telling customers.

Will my customers notice?

They’ll see a new client area and may need to reset their password or re-add a card. Their services keep running, because migration doesn’t touch the servers themselves.

Can I run WHMCS and Blesta side by side?

Only briefly, and only one should ever bill. Running both crons at once risks double invoices and suspensions, so switch billing in one clear step.

Can I move back from Blesta to WHMCS?

Keeping WHMCS untouched until the first billing cycle on Blesta is done is your safety net. If something goes badly wrong early, you can restart the WHMCS cron and try again later.

Can you help with the move?

Yes. Tell us about your setup and we’ll plan your WHMCS to Blesta move with you. Browse more Blesta guides.