Switching billing systems: a migration checklist

Businesses switch billing systems for good reasons: the old one can't handle debit orders, doesn't connect to their gateway, can't produce VAT invoices properly, or simply needs too much manual work. The risk is in the move itself. A badly planned migration can mean customers billed twice, subscriptions that quietly stop renewing, or a month-end where nothing reconciles.

This checklist walks through a migration in the order that keeps the risk lowest.

1. Write down what you have today

Before you choose a new system, document what the current one actually does, including the things nobody thinks about until they break:

• How many customers, active subscriptions and open invoices you have.
• Each way you collect: card, instant EFT, debit order, manual EFT, cash.
• Billing dates, trial rules, proration and how failed payments are retried.
• Every email customers receive: invoices, receipts, reminders, renewal notices.
• Integrations: accounting system, website checkout, CRM, internal reports.
• Who uses the system and what each person needs to do.

This list becomes your requirements and, later, your test plan. If you are still deciding whether you need separate billing and accounting tools, see billing software vs accounting software.

2. Check what can move and what can't

Some data moves easily. Some doesn't move at all, and it is better to know that early.

Customer and product data

Customer names, contact details, VAT numbers, products and prices usually export to CSV and import into the new system. Clean the data before you move it: merge duplicates, archive customers who left years ago, and fix missing email addresses.

Open invoices and balances

Decide whether to move every open invoice or only the balance per customer. Moving balances is simpler; moving invoices keeps the detail customers may ask about. Either way, totals must match your accounting system on cut-over day.

Saved cards

Card tokens belong to the payment gateway that created them, not to your billing system. If you keep the same gateway, you may be able to keep using existing tokens, depending on the gateway. If you change gateways, customers usually need to enter their card again unless both providers support a secure token transfer. See card tokenisation explained.

Debit order mandates

Mandates are tied to the creditor and the debit order provider. If your provider stays the same, existing mandates may continue to apply. If the provider changes, ask both providers what is needed, and plan for customers to sign new mandates where required. See debit order mandate requirements and DebiCheck explained.

3. Set up and test the new system

Configure the new system completely before any customer touches it:

• Business details, VAT settings, invoice numbering and branding. See invoice numbering best practices.
• Products, plans, prices, trial lengths and discount codes.
• Gateways, first in sandbox or test mode. See payment gateway sandbox testing.
• Email templates and your sending domain, so invoices don't land in spam. See invoice emails going to spam.
• User accounts and roles for your team.

Then run every scenario from your step 1 list with test customers: a new sign-up, a renewal, a failed payment, a refund, a plan change and a cancellation.

4. Plan the cut-over

The most important rule: no customer should be billed by both systems for the same period.

• Pick a cut-over date, ideally just after a billing run so that you have the longest gap before the next one.
• Switch off automatic billing in the old system before the new one starts billing.
• Set each migrated subscription's next billing date to match where it was in the old system.
• Freeze changes in the old system during the move, or record them for re-entry.

5. Tell customers what is changing

Customers notice when invoices look different or come from a new address. Tell them before cut-over:

• What will look different: invoice layout, sender address, payment page.
• What they need to do, if anything, such as re-entering a card or signing a new mandate.
• That their price and billing date stay the same, if that is the case.
• Who to contact with questions.

6. Watch the first cycle closely

For the first full billing cycle after cut-over:

• Check that every expected invoice was issued and every expected charge was attempted.
• Reconcile collections against your bank account daily. See bank reconciliation basics.
• Follow up quickly on customers who haven't updated cards or mandates.
• Keep read-only access to the old system for history and audit.

How CentraPoint helps

CentraPoint brings invoicing, payment links, subscriptions, debit orders and reconciliation into one system, so a move often replaces several tools at once. You can connect the gateways you already use, including PayFast, Netcash, Ozow, Yoco, Peach Payments, PayGate, Paystack and others, and test them before going live. Subscriptions run from packages and plans with trials, renewals and dunning, and debit orders run through Netcash with online mandates customers sign themselves.

Branded invoices and receipts, your own email templates and SMTP server, and roles with fine-grained permissions let you set up the new system properly before cut-over. Accounting integrations sync customers, invoices and payments to Sage, Xero, QuickBooks or Zoho Books. See the full features list, the supported gateways and pricing, or contact sales to talk through your migration.

Frequently asked questions

How long does a billing migration take?

It depends on how many customers, integrations and collection methods you have. A simple setup can move within days; complex debit order or multi-gateway setups need more time for testing and customer communication.

Will my customers have to re-enter their card details?

If you change payment gateway, usually yes, because card tokens belong to the gateway. If you keep the same gateway, ask whether existing tokens can be used.

What is the biggest risk when switching?

Billing customers twice, or not at all, around the cut-over date. Switch off automatic billing in the old system first and check the first cycle carefully.