A hosting billing
migration checklist
Changing billing software is not the same as moving a website. You need to preserve the relationship between the customer, invoice, service and next renewal. Use this checklist before deciding a cutover date.
14-day free trial · No credit card required
Build a migration inventory
Start with an export and a dependency list, not a live import. Record which system currently owns customer records, scheduled invoices, service provisioning, domain renewals and payment collection. Include scripts and staff routines that are not visible in the billing application's feature list.
- Customers: source ID, destination ID, account status, currency and tax treatment.
- Services: panel or registrar, provider-side identifier, package, options and renewal date.
- Finance: open invoices, credits, balances and the date each total was recorded.
- Payments: gateway account, authorisation type and the system responsible for the next charge.
- Operations: support access, email templates, cancellation rules and recovery contacts.
Store exports securely. They may contain personal and financial information. Retain only what the migration requires and control access to the archive.
Choose a representative pilot
| Test account | What to verify | Stop if |
|---|---|---|
| Active hosting customer | Existing service links to the correct order without creating another account | A duplicate service appears |
| Annual subscription | Next renewal, amount and cycle match the source | The next invoice is generated too early |
| Unpaid customer | Outstanding invoices and credits reconcile | Balance differs without an explanation |
| Domain customer | Registrar record and renewal ownership remain clear | Both systems can renew the same domain |
| Usage customer | Unbilled usage and period boundary have an explicit treatment | Usage is lost or counted twice |
An import does not prove payment portability
A customer export may move names and invoices, but stored payment methods and mandates need their own review. Confirm with the provider which identifiers and authorisations can remain valid, and whether the destination integration supports that arrangement.
Do not copy raw card details into exports or ask customers to send them by email. If reauthorisation is required, plan a clear customer message and secure payment flow. Schedule this before the next renewal, not after a failed collection.
BillingServ documents customer and invoice CSV imports and supported source-system imports. Check the options actually available in Import and Export; this is not a guarantee that every source platform, service object or payment method migrates automatically.
Prevent duplicate invoices and charges
For every pilot account, identify one system that will generate its next invoice, one that will initiate its next collection and one that will send its reminders. Set a documented cutover time and account for time zones and jobs already in progress.
Pause overlapping scheduled actions only as part of an approved cutover procedure. Keep the source available for investigation, but do not let both systems continue collecting against the same customer balance. Record changes after the initial export and reconcile them before release.
Define rollback before you need it
A rollback is not simply restoring an old database if payments or registrar orders have occurred since the backup. Identify those external side effects and reconcile them first. Keep an operator responsible for the go/no-go decision and the provider contacts needed for an incident.
Check money, service and communication
- Customer and open-invoice counts match, or every difference is documented.
- Balances reconcile by currency; do not combine currencies into an unexplained total.
- Existing services remain accessible and correctly linked.
- Representative next invoices, reminders and customer emails are correct.
- No duplicate charges, domain requests or provisioning actions occurred.
- Staff can locate an order, investigate a payment and handle a cancellation.
Start with the hosting billing workflow and your relevant integration setup pages. For comparisons, see WHMCS, Blesta, HostBill and Clientexec.
Plan your move with the right checks
Try BillingServ with your products, customers and payment workflow.
No credit card required.