Changing systems · 5-minute read
Your first week after changing billing software: a daily check-in plan
A low-drama first-week migration plan: reconcile every shift, capture issues, assign owners and decide when to keep or revise the cutover.
The practical answer
What should you check during the first week after a POS migration?
For the first week, pick a named owner for end-of-day reconciliation, keep an issue log and compare expected with recorded sales, payments and stock movement. Test high-impact fixes on sample records first. Keep the previous records available according to your retention plan and review unresolved issues before you call the change stable.
Before day one, agree who owns each check.
Name one person for daily reconciliation, one person who can approve corrections and one contact for unresolved software issues. Save the old and new system's cutover time, opening stock position and payment totals in the migration record. Keep an agreed read-only way to access historical records.
Write a stop rule before the shop opens: which missing records, payment errors or equipment problems mean the team should pause and use the fallback? A fallback is useful only when staff know how to activate it and reconcile any work entered after cutover.
Use a short daily check-in.
| When | Compare | Record |
|---|---|---|
| Opening | Users, devices, opening float and sample high-priority products | Who confirmed the setup and any unresolved issue |
| During shift | Sale, correction, return, payment and receipt tasks | Example transaction reference; never customer private data in a public issue log |
| Closing | POS totals, payment-provider totals, refunds and selected stock | Variance, reviewer and next action |
| Next morning | Open issues, prior-day balance and any pending export or sync | Whether the fallback remains needed |
Prioritise issues by customer impact and business risk, not by how quickly they are fixed. A label alignment issue and a missing payment record do not have the same urgency.
Keep corrections small and traceable.
For a suspected data issue, reproduce it using a test record before editing live data. Capture the expected outcome, the observed outcome, the edition and steps. Avoid sending customer names, phone numbers or real receipts in a support screenshot unless a secure approved channel requires them.
Train by task: new sale, correction, return, shift handover and the local invoice flow you have agreed. Let the cashier repeat each task. A signed attendance sheet shows training occurred; it does not show the workflow is understood.
Review the week before declaring the move stable.
Summarise which transactions reconcile, which exceptions remain and who owns each one. Compare actual work with the original cutover plan and adjust the process if needed. Keep old-system access under the business's record-retention plan, and revoke it according to the agreed security process when it is no longer required.
Measure a useful baseline.
If you want to compare checkout time, item errors or stock variance, define the same sample and measurement period before and after. Report what was actually measured and the store context; do not assume a migration improved a metric.
Frequently asked questions
How long should we keep the old billing system?
That depends on access, support and applicable record-retention duties. Ask your accountant or qualified adviser, and confirm the old provider's export and access terms.
Should we fix every issue in the first week?
Fix urgent issues first, then schedule lower-risk improvements. Keep issues visible with an owner and due date, and do not hide a difference by rewriting source records without a trace.