Guide
A cutover-day checklist for moving a clinic to a new system
Cutover day goes calmly when its decisions are made four weeks earlier: a clear freeze date, a final export, a signed balance snapshot, users and roles ready, printers and invoices tested, the insurance and e-invoicing connections switched, appointments re-confirmed, and a written rollback plan. This checklist is ordered by time, so you can print it and hand each item to its owner.
Last reviewed:
In this guide
It assumes the data has been test-loaded and reconciled at least once. If not, start with how to move your clinic to a new system without losing data or balances. To see how we run the move for you, see moving to a new system.
What must be settled four weeks before?
- [ ] Cutover date. Ideally the start of a month or right after a month is closed, on a quieter day. Avoid month-end and payroll days.
- [ ] Freeze date and time. The moment after which no financial transactions go into the old system. Write it down to the hour.
- [ ] Cutover owner. One person at the group who decides when a difference appears, paired with a lead from the new vendor.
- [ ] What moves and what does not. The list signed off after the test load, including what moves as balances only.
- [ ] Export deadline from the old vendor. The final export date in writing and confirmed by them, plus read-only access after cutover.
- [ ] User list. Every staff member, their branch, their role, and what they should and should not see.
- [ ] Training plan. Short sessions per role, held in the last week, not long before.
- [ ] Rollback criteria. What would make you go back to the old system, who decides, and until what time (see the last section).
What do you prepare one week before?
- [ ] A last test load with a fresh copy of the data, and the counts and balances reconciled again.
- [ ] User accounts created, and every staff member has logged in at least once and changed their password.
- [ ] Printers at every point: invoices, prescriptions, labels, wristbands if used. Print a real page from each device.
- [ ] Print formats with the group's logo and tax details, and the QR code visible and readable on the printed invoice.
- [ ] Card terminals set up in the new system for every collection point.
- [ ] Price lists and insurance contracts checked on a sample of services for each payer.
- [ ] Doctors' schedules in the new system match the coming weeks.
- [ ] A message to patients if anything they see changes, such as the invoice layout or reminder messages.
- [ ] E-invoicing connection. The new system is onboarded on the Fatoora portal to get a cryptographic stamp identifier for each invoicing unit, the old system's units are reviewed on the same portal, and its e-invoices stay archived. The process is in ZATCA's E-Invoicing Detailed Guideline. Agree the timing with both vendors and your tax adviser.
- [ ] Insurance connection. Agree with the new vendor the day the NPHIES connection switches over, and pull a list of open prior approvals and pending claims from the old system to follow up.
What do you do the day before?
- [ ] Close every cash shift in the old system, verify them, and deposit the cash.
- [ ] Freeze on time. Tell every branch the hour and stop financial transactions after it.
- [ ] Final export from the old system, including attachments added since the last load.
- [ ] Balance snapshot: patient balances and deposits, doctor dues, receivables per payer, and the trial balance. Signed by the finance manager.
- [ ] Final load into the new system, then totals reconciled to the snapshot.
- [ ] Tomorrow's and the following days' appointments are there, with the same doctor at the same time.
- [ ] Appointments re-confirmed with patients for the first days, so the attendance list is right.
- [ ] A clear support number for each branch, and a rota of who from the new vendor is on site in each branch in the morning.
What happens on cutover day?
- [ ] Before the doors open: every user has logged into the new system, every printer has printed, and every card terminal has run a small transaction.
- [ ] First patient in each branch: followed from registration to invoice and payment, and the invoice checked.
- [ ] First insured patient: eligibility, approval and invoice followed to the end.
- [ ] One issue log: every issue written down with its time, branch and owner, instead of scattered messages.
- [ ] No silent return to the old system. Any transaction recorded in the old system after the freeze will be lost or duplicated.
- [ ] First shift closed in the new system with a count and a check, and the card-terminal report matched.
- [ ] A short end-of-day meeting: open issues, the decision to continue, tomorrow's plan.
What do you watch in the first week?
- [ ] Daily cash reconciliation per branch, with every difference explained the same day.
- [ ] A sample of issued invoices reviewed: prices, insurer share, VAT, printout.
- [ ] The list of approvals and claims carried over from the old system, followed until closed.
- [ ] Appointments beyond week one reviewed, especially recurring ones and package sessions.
- [ ] Doctors' questions: can they find the clinical history and attachments they need?
- [ ] Permissions adjusted where they turned out too wide or too narrow.
- [ ] The first month closed in the new system before access to the old one ends.
For what the finance manager should see daily and monthly after the move, read what gets lost between the clinic system and the accounting program.
What is the rollback plan, and when do you use it?
The rollback plan is written before cutover and rarely used, but having it keeps the decision calm. It should set:
- Rollback criteria: for example, being unable to issue invoices or register patients in more than one branch for hours, not a problem with one report or screen.
- The rollback deadline: usually the end of day one. After that, the new system builds up transactions that are hard to move back.
- Who decides: the group's cutover owner, after hearing the new vendor.
- How the first hours' transactions go back into the old system if you roll back, and who enters them.
- The old system kept workable until the rollback deadline passes, not just read-only.
Who owns each item?
| Item | Suggested owner |
|---|---|
| Cutover date, freeze and rollback decision | General manager or cutover owner |
| Balance snapshot and reconciliation | Finance manager |
| Users and permissions | Operations manager with the new vendor |
| Clinical history and documentation templates | Medical director |
| Insurance and invoicing connections | Finance manager with the new vendor |
| Appointments and patient contact | Front-desk supervisor |
| Export from the old system | The old vendor, chased by the cutover owner |
How Nixpend helps
In Nixpend the clinic, insurance, cash shifts, doctor dues, inventory, purchasing, HR and payroll, and accounting share one record, so there are not two new systems to reconcile on cutover day. Our own team moves your patients, balances and history from the old system and works through this checklist with you item by item, from the freeze to the first month-end close. See moving to Nixpend or book a demo.
FAQ
What is the best day to switch to a new clinic system?
The start of a month or right after a month is closed, on a quieter day, away from payroll.
Do I have to close the clinic on cutover day?
Usually not. Freezing financial transactions in the old system the evening before and starting on the new system in the morning is enough.
What do I do with prior approvals still open at cutover?
Pull the list from the old system before the freeze and follow each one until it is closed.
When do I end access to the old system?
After the first month is closed and reconciled in the new system, keeping a copy for reference.
Sources
See Nixpend on a day like yours
A 30-minute walk through the platform, on a scenario close to your day: from the booking to the claim and the journal entry.