Changing systems · 6-minute read
Switch billing software: a safer migration checklist
Plan a billing software migration with a data inventory, trial import, stock reconciliation, staff rehearsal and a clear go-or-stop decision.
The practical answer
How do you prepare to switch billing software?
Start with an export and a recoverable backup, agree which records will move, then rehearse the import in a separate test environment. Reconcile stock and balances before choosing a cutover time. Keep an approved fallback and readable historical records; a successful import alone does not prove the migration is correct.
1. Decide what needs to move—and what can stay readable.
A software change is also a data decision. List product codes, units, barcodes, prices, stock, customer and supplier balances, users and historical transactions. For each category, agree whether to import it, enter an opening balance or retain it in a readable archive. These are different jobs and may have different costs.
Confirm export access before ending the old service. Ask which formats and fields the new system accepts. Keep the original export untouched, and work on a copy. Do not assume that importing product names also transfers sales history, serial numbers or outstanding balances.
2. Build a mapping sheet before importing.
| Record | Decision to document | Check after import |
|---|---|---|
| Products | Which field is the unique item key? | Item count, duplicates, units and barcodes |
| Stock | Which location and cutoff time apply? | Quantity by item and location, including exceptions |
| Prices | Which price list and rounding rules apply? | Sample bills against approved expected totals |
| Balances | Who approves the opening balances? | Individual balances and control totals |
| History | Import or retain a readable archive? | Find a past sale and its related records |
| Staff | Which roles need which permissions? | Access using a normal cashier account |
Resolve ambiguous units before loading stock: “box” and “piece” can produce very different quantities. Investigate duplicate barcodes rather than deleting rows simply to make the import finish.
3. Rehearse with a recoverable copy.
Use a separate test environment and a representative data sample. Include difficult cases such as inactive products, variants, returned goods and balances. Confirm that any test receipt, payment or integration cannot trigger a real transaction.
After the trial import, compare source and destination counts and totals. Investigate mismatches item by item. Have the person responsible for stock approve stock differences, and the person responsible for accounts approve balances. A green “import complete” message is only the beginning of verification.
A backup is a recovery plan only after a restore test.
Ask where the backup lives, who can access it and how to restore it. Demonstrate recovery in the test environment. Keep a copy separate from the working machine according to your agreed access and retention policy.
4. Choose a cutover with a clear stop rule.
Pick a quieter trading period. Decide when entries stop in the old system, who exports the final changes, who imports them and who approves opening stock and balances. Avoid recording the same live sale in both systems without an agreed reconciliation method.
- Go: required records reconcile, staff can complete core tasks, equipment works and the fallback is ready.
- Stop: unexplained balances, missing essential records, failed receipt printing or an untested recovery process remain.
- Fallback: agree who can call the decision, which system resumes and how transactions since cutover will be reconciled.
Keep the old records accessible for your business’s retention obligations. Ask your accountant about required records and periods; this checklist does not set a legal retention policy.
5. Watch the first close, not just the first sale.
Reconcile the first day’s payments, refunds, discounts and stock movements. Keep an issue log with the transaction, expected result, observed result and owner. Separate data corrections from staff training issues so one does not hide the other.
Considering a move to Oasis POS? Discuss the existing software, available exports, approximate record counts and required history first. Migration feasibility, effort and supported fields need assessment; this guide is not a promise of automatic or loss-free transfer.
Questions to settle before migration
Must all old transactions be imported?
Not necessarily. An approved opening position plus a readable historical archive may fit some businesses. Decide based on operational needs, available exports and record obligations, then document the choice.
Can migration happen while the shop is open?
That depends on the volume of changes and the systems involved. A trial should establish the process and timing. Never assume that an initial export includes sales entered after that export.