From WHMCS
Move clients, services, invoices and tickets from WHMCS into HostCore.
This guide covers what you need from WHMCS and exactly what comes across. For how the migration itself runs, including the sandbox, pre-flight counts, approval and top-ups, see Migration overview.
Before you start
You'll need:
- WHMCS 7.0 to 9.x. If you're on another version, open a support ticket before you start.
- A full SQL dump of your WHMCS database. See Export your database.
- Admin access to WHMCS, so you can check the pre-flight counts against it.
- Access to the same Stripe and PayPal accounts WHMCS charges through, if you want saved payment methods to keep working. See Payment methods.
You don't need to take WHMCS offline. Keep billing there until you switch over, and use a top-up migration to bring across anything that changes in the meantime.
Export your database
Use the command line if you have shell access. It's faster, handles large databases better, and takes a consistent snapshot.
From the command line
On the server that hosts your WHMCS database, run:
mysqldump --single-transaction --quick \ -u YOUR_DB_USER -p YOUR_DB_NAME \ | gzip > whmcs-migration.sql.gz--single-transaction takes a consistent snapshot without locking tables, so it's safe to run on a live install.
Using phpMyAdmin
If you're on shared hosting without shell access, export from phpMyAdmin instead. In cPanel, it's under Databases › phpMyAdmin.
Select your WHMCS database
Select it in the left-hand sidebar. If you're not sure which one it is, it's the
$db_namevalue in your WHMCSconfiguration.php.Set the export options
Open the Export tab and set:
Option Value Export method Custom Format SQL Tables All selected (the default) Output Save output to a file Compression gzipped Format-specific options › Dump table structure and data Export
Click Export and save the
.sql.gzfile.
phpMyAdmin exports one table at a time rather than as a single snapshot, so run it during a quiet period, not during your WHMCS cron or a renewal batch. On large installs it can also hit your host's time or memory limits and produce a truncated file. If your pre-flight counts come up short, use the command line or ask your host for a full database backup instead.
What comes over
Migrated live and exact
These affect active billing, so they're reproduced precisely:
- Users and clients
- Active products and services
- Subscription billing state: next due dates, billing cycles and recurring amounts
- Saved Stripe and PayPal payment methods
- Recent and open tickets
- Account credit balances
Migrated as read-only history
Kept so you and your clients can look back, but they can't be edited or reissued:
- Invoices
- Payment history
- Closed tickets
Set up fresh in HostCore
These don't translate cleanly from WHMCS, so you rebuild them:
| Item | Why |
|---|---|
| Settings | HostCore's configuration doesn't map one-to-one onto WHMCS's. |
| Branding | Logos, colours and storefront styling are set up in Store Settings › Storefront. |
| Email templates | HostCore uses a different template syntax. |
| Gateway credentials | You connect your Stripe and PayPal accounts in Store Settings › Payment Gateways. |
| Modules | WHMCS provisioning modules are replaced by HostCore modules in Store Settings › Modules. |
Never migrated
- Raw card numbers. See Payment methods.
- Data owned by third-party WHMCS addons, which lives in its own tables.
Payment methods
If WHMCS charges a client through Stripe or PayPal, the token for their saved card or PayPal account comes across with them. Their next renewal in HostCore charges it automatically, and the client doesn't need to do anything.
Some WHMCS installs store card numbers in the WHMCS database instead of with a payment gateway. HostCore will not accept, decrypt or process that data under any circumstances. Clients whose cards are stored that way need to add a payment method in HostCore before their next renewal.
A saved payment method only works in the account that created it. Connect the same Stripe account and the same PayPal business account your WHMCS install uses. If you connect different accounts, every migrated payment method fails at renewal.
Before you switch over:
- Connect the same Stripe and PayPal accounts in Store Settings › Payment Gateways.
- Email clients whose cards were stored in WHMCS itself and tell them they'll need to add a payment method. Don't let a failed payment be the first they hear of it.
- Expect a few failures on your first renewal cycle. Payment methods are copied exactly as WHMCS had them and aren't tested on import, so cards that had already expired or been removed fail the same way they would have in WHMCS.
Passwords
Clients keep the passwords they already use. HostCore reads WHMCS's password hashes directly and upgrades each one to HostCore's format the first time that client signs in. There's no mass password reset and no "please set a new password" email.
Run the migration
Upload your .sql.gz dump from Migrations. [OLLIE: confirm where uploads happen] From there, the migration runs through the sandbox, pre-flight counts and approval described in Migration overview.
When you check the pre-flight counts, compare them against the totals in your WHMCS admin area: clients, active services, invoices and tickets. A mismatch almost always means an incomplete dump.
Top-up migrations
After your main migration is committed, you can upload a newer dump of the same WHMCS database as a top-up. It brings across new clients, new services, updated due dates, new invoices and tickets without duplicating anything.
To switch over with a top-up:
- When you're ready, disable the WHMCS cron so nothing else changes.
- Take a fresh dump the same way as before.
- Upload it as a top-up and approve it.
- Switch over.
A top-up has to come from the same WHMCS install as your main migration. To migrate a different WHMCS install into the same store, open a support ticket.
After you switch over
Work through these in order:
- Reconcile the final report against your WHMCS admin area. The counts should match exactly.
- Check your gateways are connected to the same Stripe and PayPal accounts WHMCS used.
- Rebuild your branding and email templates.
- Email clients who need to add a new payment method.
- Disable the WHMCS cron, if you haven't already as part of a top-up.
Step 5 is the one people forget. If WHMCS and HostCore are both running, both invoice the same services, and both can charge the same saved card.
Questions
Can I keep running WHMCS during the migration? Yes. The migration works from a dump, so nothing touches your WHMCS install. Keep billing there until you're ready, then run a top-up migration.
Can I migrate more than once? Yes. Before you commit, you can run and cancel test migrations as often as you like. After you commit, you can run top-ups from newer dumps of the same database.
Do my clients need to re-enter their cards? Only clients whose cards were stored in the WHMCS database itself. Payment methods saved with Stripe or PayPal come across.
What about my WHMCS modules and addons? Provisioning modules are replaced by HostCore modules. Check Store Settings › Modules, or the HostCore marketplace if your panel isn't listed there. Data owned by third-party addons doesn't come across.
Something's wrong after I committed. What now? Open a support ticket. We can roll the migration back for you.