---
title: "How to Migrate Patient Records from an Old System Without Losing Data"
url: "https://doccure.io/how-to-migrate-patient-records-without-losing-data/"
updated: "2026-11-13T05:03:27+00:00"
type: "post"
business:
  name: "Doccure"
  phone: "+44 7438 823475"
  location: "City Business Centre, 11a Lower Road, London SE16 2XB, United Kingdom"
---

# How to Migrate Patient Records from an Old System Without Losing Data

The fear that keeps clinics on software they dislike is simple: “What if we lose our patient records?” It is a reasonable fear. A migration done carelessly can drop allergies, detach lab reports from patients or duplicate half the register. Done properly, it is a controlled project with a clear end. Chemist Doctor in the UK moved from an older WordPress-based system to a platform we rebuilt for them, with their existing data migrated ([read the customer story](/customers/chemist-doctor/)). This guide sets out the steps we recommend.

## What “migration” covers

List what you hold before you plan anything. A typical clinic system contains:

- patients: identity, contact details, identifiers;
- clinical history: allergies, problems, medications, immunisations;
- encounters and notes;
- prescriptions;
- lab orders and results;
- documents and images: scanned letters, reports, consent forms;
- appointments, past and future;
- invoices, payments and balances;
- staff accounts and roles;
- stock, if you run a pharmacy.

Not all of it needs to move in the same way. Decide for each: migrate as structured data, migrate as a document, archive, or leave behind.

## Step 1: get a full export, early

Ask your current vendor for a complete export and a description of its format. If the system is your own, take a copy of the database and the file storage. Do this before you give notice. Some vendors become slow once they know you are leaving, and you want to know what you have while there is time.

Check three things at once: the patient count matches what the system shows, attachments are included and can be opened, and dates and special characters have survived.

## Step 2: clean before you move

Old systems collect clutter. Moving it makes the new system worse from the first day.

- **Duplicates.** The same patient registered twice with different spellings. Merge them with rules a clinician has approved.
- **Test records.** “Test Patient” and “Mickey Mouse”.
- **Free-text fields.** Allergies typed in a notes box will not become structured allergies by themselves. Decide whether to map, review by hand or carry as text.
- **Inactive patients.** Check how long the law requires you to keep records before archiving anyone.

## Step 3: map every field

Make a table: each field in the old system, where it goes in the new one, and any transformation. “Sex: M/F” to “Male/Female”. Dates from day-month-year to a standard format. Phone numbers to one pattern. Where the new system has no home for a field, decide whether it becomes a note, a document or is dropped. Have a clinician sign off the clinical mappings. Engineers should not decide what happens to an allergy list alone.

## Step 4: run a trial migration

Never migrate once. Load the export into a test copy of the new system and check it.

- **Counts.** Patients, encounters, prescriptions, documents and invoices in the old system equal those in the new.
- **Totals.** Outstanding balances add up to the same figure.
- **Samples.** Pick thirty patients, including complicated ones, and compare screen by screen with a clinician.
- **Attachments.** Open them. A link to a missing file counts as a lost file.
- **Edge cases.** Patients with no date of birth, very long notes, names with accents.

Fix the mapping and repeat until a trial runs clean. Expect at least two rounds.

## Step 5: plan the cutover

- Choose a quiet time: a weekend or a holiday.
- Freeze changes in the old system, or record them on paper during the gap.
- Take a final export and run the migration you have rehearsed.
- Repeat the counts and a short sample check.
- Move future appointments last, so that none are booked in between.
- Tell patients if their booking link or login changes.

## Step 6: keep the old system, read-only

Do not switch it off on the day. Keep it available, read-only, for an agreed period so that staff can look up anything that seems wrong. Keep the final export and the migration logs for as long as your record-keeping rules require. Then close it down properly and get written confirmation that the vendor has deleted your data.

## Step 7: train, then watch the first weeks

Many “lost data” reports after a migration are data that is present but in a different place. Show staff where history, documents and old invoices now live. Give them one channel to report anything missing, and check each report against the old system.

## Protecting data during the move

- Transfer exports by secure channels, never by ordinary email.
- Limit who can open them, and delete working copies when you finish.
- Have a BAA or data processing agreement with whoever performs the migration.
- Never use real patient data in a demonstration environment.
- Record what was moved, when and by whom.

## A simple timeline

| Stage | What happens | Who leads |
|---|---|---|
| Inventory and export | List data, obtain and check the export | Clinic manager |
| Cleaning and mapping | Duplicates, field mapping, clinical sign-off | Clinician and migration team |
| Trial runs | Load, count, sample, fix, repeat | Migration team |
| Training | Staff learn the new system on migrated test data | Clinic manager |
| Cutover | Freeze, final run, checks, go live | Migration team |
| Aftercare | Old system read-only, issues tracked and closed | Both |

How long it takes depends on the size and state of your data. A small, tidy clinic moves in days. A large one with years of free text needs weeks, most of it cleaning and checking.

## Migrating to Doccure

Migration to Doccure is done with our team as a scoped piece of work, and the destination is a structured record: allergies, problems, family history, immunisations, documents and consents, encounters with diagnoses, prescriptions and lab results. Doccure also provides standards-based FHIR and HL7 interfaces for connecting to other systems. Once you are in, your data belongs to you. Doccure is HIPAA-ready and GDPR-ready. We sign a BAA.

## Frequently asked questions

### Will we lose data when we change system?

Not if you run trial migrations and check counts and samples before cutover.

### How long does a migration take?

From days to weeks, depending on the amount and tidiness of the data.

### Can scanned documents be moved?

Yes, as documents attached to the right patient. Check that the export includes the files and not only their names.

### What if our old vendor will not give us an export?

Check your contract and your rights under data protection law. You are generally entitled to your patients’ records. Take advice if the vendor refuses.

### Do we need to tell patients?

Tell them if anything changes for them, such as a new portal login or booking link, and update your privacy notice if your vendors change.

## Planning a move?

Tell us what system you use now and roughly how many patients you hold. Start on the [custom development page](/custom-development/) or [book a 30-minute call](/book-a-demo/).
