Guide

How to move your clinic to a new system without losing data or balances

A safe move to a new clinic system rests on four steps: decide exactly what moves, secure your right to export data from the old vendor, clean and map the data, then run a test load in which balances are reconciled per patient and per doctor before cutover day. What usually gets lost is not patient names but balances, deposits, attachments and financial history.

Last reviewed:

In this guide

This guide is for the owner, general manager and finance manager of a polyclinic or group thinking about changing systems. To see how we handle the move for you, see moving to a new system.

What data should move?

Start with a written list, with one check for each item that you answer after the load:

DataWhy it mattersCheck
Patients, file number, national ID or Iqama, mobileEverything else hangs on themDoes the count of active files match? Is the old file number still visible and searchable?
Upcoming appointmentsPatients will turn up whatever happensIs every appointment after cutover there, with the same doctor at the same time?
Clinical historyDoctors' notes, diagnoses, procedures, treatment plansCan a doctor see the last visit of a patient they know?
Attachments and x-raysImages, reports, signed consentsDo attachments open from the right patient's file?
Price listsPer service and per payerDoes a sample of service prices match?
Insurance contracts and policy classesCover, co-pay and discountsIs the patient share calculated as before?
Patient balances and depositsMoney the patient owes, or the clinic owes the patientDoes the total match, and does each patient's balance match?
Doctor duesWhat is owed to or by each doctor at cutoverHas each doctor signed off their opening balance?
Opening balances in the booksCash, banks, receivables, suppliers, stockDoes the opening trial balance equal the closing one in the old system?

Not everything has to move at the same level of detail. Many groups move old financial history as balances only and keep the old system, or a copy, for looking up detail. What matters is that this is a written decision, not a surprise.

Who owns the export from the old vendor?

The data belongs to the clinic, but access usually goes through the old vendor. Before you tell them you are leaving:

  • Read the contract. Look for data ownership, handover at the end of the contract, format, timing and cost.
  • Ask for a sample early. An export of ten patients with all their tables shows whether the data is usable before time runs short.
  • Ask for a readable format. Tables (CSV or Excel) or a database copy with field descriptions, and attachments in folders linked to the file number.
  • Do not end the subscription before checking. Keep read-only access until after the first month-end close in the new system.

Health data is sensitive personal data, so ask your legal adviser what the Personal Data Protection Law requires when it is transferred to a new vendor, and what your contract with that vendor should say.

How do you map and clean the data?

Cleaning before the load is much cheaper than fixing after it. What most often needs work:

  • Duplicate patients. The same patient with two files, registered once with three names and once with four, or with two mobiles. Agree a merge rule (ID first, then mobile and date of birth) and review doubtful cases by hand.
  • File numbers. If each branch had its own number series, decide how they stay distinct in the new system, and keep the old number searchable, because staff and patients remember it.
  • Mobile formats. Numbers stored as 05… and as 9665… look different to a system, so messages fail and patients get duplicated. Standardise them before the load.
  • Doctors and services. Map every doctor code and service in the old system to its match in the new one, in a single table signed off by the medical director and finance.
  • Arabic and English names. Decide which field is the master, and do not leave patients without an Arabic name if your printouts are in Arabic.

How do you test the load and reconcile balances?

There is no good migration without at least one test load in a test environment. After it, reconcile:

  1. Counts: patients, upcoming appointments, visits, attachments.
  2. Total patient balances, then a sample of patients one by one, especially large balances and deposits.
  3. Each doctor's dues balance, signed off by the doctor or the finance manager.
  4. Receivables per payer and pending claims.
  5. The opening trial balance against the closing one in the old system.

Record every difference, its cause and the decision on it. If there are many, repeat the test load after fixing, and do not cut over until every difference has a known cause.

What is the cutover plan, and do you need a parallel run?

Set a freeze date: after it, no financial transactions are recorded in the old system, and the final export and balance snapshot are taken. Many groups prefer to move at the start of a month or right after a month is closed, so the closing balance is clear.

A full parallel run (every transaction entered in both systems) is exhausting and creates its own errors. A more realistic option: run the new system alone, keep the old one read-only, and reconcile cash and appointments daily in the first week. The hour-by-hour detail is in the cutover-day checklist.

Remember invoicing: the new system must be onboarded on the Fatoora portal to get its cryptographic stamp identifier before it issues its first invoice, and the old system's e-invoices must stay archived under the record-keeping rules, as set out in ZATCA's E-Invoicing Detailed Guideline. The same goes for insurance: prior approvals open in NPHIES at cutover need a follow-up list so none are lost.

Who needs training, and when?

Train each role on its own work only, days rather than weeks before cutover, using your real patients in the test environment: reception on booking, registration and the cash drawer; doctors on the patient file and orders; finance on the daily and monthly close. Pick one go-to person per branch to answer questions in the first week.

On how long old medical records must be kept: we did not find a published period on the Ministry of Health pages we checked, so ask your licensing authority or legal adviser, and do not destroy any old copy before then.

What usually goes wrong?

  • Balances are left to the end and moved in a rush, without per-patient reconciliation.
  • Attachments are forgotten because they sit outside the database, in a folder on a branch PC.
  • A doctor or service code is mapped wrongly, so revenue lands on another doctor.
  • The old vendor is slow to export because the contract sets no deadline.
  • Upcoming appointments are not checked, so patients arrive and reception cannot find them.
  • Nobody owns the decision when a difference shows up on cutover day.

How Nixpend helps

In Nixpend the clinic, insurance, cash shifts, doctor dues, inventory, purchasing, HR and payroll, and accounting share one record, so balances land in the right place from day one. Our own team moves your patients, balances and history from the old system: we take the export, clean it, run a test load and reconcile the balances with you before cutover day. See moving to Nixpend or book a demo.

FAQ

How long does it take to move clinic data to a new system?

It depends on the volume and quality of the data and how fast the old vendor exports. The test load and reconciliation set the date, not the load itself.

Do I have to move every old invoice?

Not necessarily. Many clinics move balances and keep old detail for reference. The old e-invoices must stay archived.

Do I need to run both systems together?

Usually the new system alone is enough, with the old one read-only and a daily reconciliation in the first week.

What if the old vendor refuses to hand over the data?

Go back to the contract. That is why you should ask for a sample export well before telling them you are leaving.

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.