Overview
How the HostCore migration tool works
HostCore can import your clients, services, billing state and history from your current billing platform, so you can switch without asking clients to sign up again or re-enter their details.
This page covers how every migration works. For what to export and what comes across from your platform, see its own guide.
| Platform | Guide |
|---|---|
| WHMCS | Migrating from WHMCS |
If your platform isn't listed, open a support ticket and we'll help you move your data across.
How a migration works
You keep billing on your current platform throughout. A migration works from an export of your data, not a live connection, so nothing in your current install changes, and nothing is written to your store until you approve it.
Export your data
Take a full export of your current platform's database. Your platform's guide says exactly what to export and how.
Upload it to HostCore
Upload the export to Dashbord > Migrations page
We restore it in an isolated sandbox
Your export is restored into a disposable database with no network access. It can't reach the internet, your store or any other store. When the migration finishes, the sandbox and everything in it is destroyed.
Check the pre-flight counts
Before anything is written, HostCore counts what it found: clients, active services, invoices, tickets and more. Compare these against your current platform's admin area. If they don't match, your export is probably incomplete, so re-take it and start again.
Review and approve
The pre-flight report lists what will move. If anything looks wrong, cancel. Nothing has been written yet.
We write it to your store
On approval, records are written in dependency order, such as clients before services, and committed together. If the process is interrupted, it picks up where it stopped without duplicating anything.
Reconcile the final report
You get a closing report with the final counts and a list of set-up items still outstanding. Check the counts against your current platform before you switch over.
You can run and cancel test migrations as often as you like before you commit one.
What comes across
Every migration sorts your data into four groups. Your platform's guide lists exactly what falls into each.
| Group | What it means | Typical examples |
|---|---|---|
| Live and exact | Anything that affects active billing, reproduced precisely. | Clients, active services, due dates, saved payment methods, credit balances |
| Read-only history | Kept so you and your clients can look back, but can't be edited or reissued. | Past invoices, payment history, closed tickets |
| Set up fresh | Things that don't map cleanly onto HostCore and are better rebuilt. | Settings, branding, email templates, gateway credentials, modules |
| Never migrated | Data HostCore won't accept. | Raw card numbers |
Payment methods
Cards and PayPal accounts saved with Stripe or PayPal come across, and clients' next renewals charge them automatically. A saved payment method only works in the account that created it, so connect the same Stripe and PayPal accounts your current platform uses before you approve.
HostCore never accepts raw card numbers. If your current platform stores cards in its own database, those clients need to add a payment method in HostCore before their next renewal. Email them before you switch over, so the first they hear of it isn't a failed payment.
Saved payment methods aren't tested on import, because the only way to check a card is to charge it. Expect a few failures on your first renewal cycle from cards that had already expired or been removed.
Passwords
Where your platform's password format is supported, clients keep their existing passwords and HostCore upgrades each one the first time that client signs in. There's no mass password reset. Your platform's guide says whether this applies to you.
Top-up migrations
You don't have to switch over the day you migrate. After your main migration is committed, a top-up migration brings across anything created or changed since, such as new clients, new services, updated due dates, invoices and tickets, without duplicating what's already there.
A typical switchover looks like this:
- Run your main migration early and approve it.
- Set up your store at your own pace while your current platform keeps billing as normal.
- When you're ready, turn off automation on your current platform so nothing else changes.
- Take a fresh export and upload it as a top-up. It goes through the same sandbox, pre-flight and approval steps.
- Approve it and switch over.
A top-up must come from the same install as your main migration. If its records don't line up with what's already in your store, it won't run.
Switching over
Turn off billing automation on your current platform before HostCore's renewals take over. If both systems are running, both invoice the same services, and both can charge the same saved card.
After you switch over:
- Reconcile the final report against your old platform. The counts should match exactly.
- Check your payment gateways are connected to the same accounts your old platform used.
- Rebuild your branding and email templates.
- Email any clients who need to add a new payment method.
If something goes wrong
The most likely problem is an incomplete export, and the pre-flight counts are there to catch it before anything is written. If the counts don't match, don't approve. Re-take the export and start again.
If you find a problem with your migrated data after committing, open a support ticket. We can roll the migration back for you.