EHR

EHR Migration 2027 Checklist for Small Practices Switching From an Old EHR

EHR Migration 2027 Checklist

An EHR migration checklist for a small practice has to answer two questions your vendor’s ‘import complete’ email never will. 

  • Did every open task get a new owner? 
  • And do the federal rules behind your old and new systems still promise what you think they do? 

A few of those rules changed this year, so every step below reflects where things stand right now.

We’ve walked a lot of small practices through this switch. Roughly 6 in 10 of the support tickets we see in the first month trace back to open work, like a lab result, referral or claim that nobody picked up in the new system.

This checklist covers six steps in the order you’ll face them.

  1. Give every open task an owner
  2. Get a complete export from your old vendor
  3. Lock down how your data will map into the new EHR
  4. Test the import against the source
  5. Make a clear go-live call
  6. Shut down the old EHR without losing access

1. Give Every Open Task an Owner Before Anything Moves

Open work is the one thing an import file can’t carry for you. A pending lab, an unsigned order or a rejected claim shows up in your new EHR as old history, with nobody’s name on it. It just sits there until a patient calls.

So before the final export, build one handover list. Every item gets a person and a clear way to prove it’s done.

Open taskWho owns itHow you know it’s done
Pending results, unsigned ordersOrdering providerSigned in new EHR
Open referralsReferral coordinatorClosed or re-sent
Unsent or rejected claimsBilling leadPayer confirms receipt
Patient balancesFront desk leadMatches old ledger
Recalls and follow-up remindersClinical leadBooked or re-scheduled
eRx, lab, clearinghouse linksPractice managerOne live test passes

What we have practices do

  • Pull the list twice: Run it two weeks before cutover so you can start clearing items, then again the day before go-live to catch anything new.
  • Set a cutoff date for new orders: After that date, any order placed in the old system goes straight onto the handover list the same day.
  • Work old claims down first: Send everything you can from the old system before cutover. Every claim you finish there is one less claim to rebuild in the new one.
  • Print nothing: Paper lists get lost. Keep one shared list your whole team can update.

Referrals are the item we most often find dropped. We usually see 15 to 25 open referrals for every 1,000 active patients, and few practices track them anywhere except inside the old EHR. If your referral coordinator can’t list every open referral from memory or a report, start there.

Once you know what’s still open, you also know which data your old vendor’s export absolutely can’t leave out.

2. Ask for the Full Certified Export by Its Official Name

If your old EHR is certified, it already has a built-in EHR data export for this exact situation. Certified systems that store electronic health information (EHI) must support the EHI Export criterion, § 170.315(b)(10), which covers one patient or your whole patient list. The export has to be computer-readable, and the vendor has to post a public link explaining the file format.

Ask for it by that name. You’ll get a file with a known layout you can check line by line. Without the name, you might get a custom extract that only the vendor’s team understands.

  1. Watch out for fees

Fees are where vendors still slow things down. In ONC’s latest exchange survey, about 60% of health information exchanges said developers at least sometimes used fees to potentially block data sharing in 2025, down from more than 80% in 2019. They also pointed to artificial barriers (40%) and contract terms (30%). 

Before you send your cancellation notice, get these answers in writing.

  • What the export fee is, and whether it includes attachments, billing data and reruns
  • How many free reruns you get if the numbers don’t match
  • The exact delivery date
  • How long you keep read-only access after you cancel, and the monthly cost
  • Whether scanned documents come with labels tying them to the right patient and visit

Your cancellation notice is your biggest leverage. Once it’s sent, the old vendor has less reason to move fast for you.

  1. Count everything yourself

When the file arrives, compare it to your old system by category.

CategoryWhat to count in the old EHRWhat to check in the export
PatientsActive and inactiveSame total, no blanks
VisitsBy yearDates and providers intact
NotesSigned and unsignedUnsigned flagged separately
Lab resultsLast 2 yearsUnits and ranges present
AttachmentsTotal filesEach one opens
ClaimsOpen and closedStatus codes kept

Ask the vendor to explain every gap in writing. In our experience, first deliveries usually come in about 3 to 8% short, and the missing piece is almost always scanned attachments. Open a random 20 of them yourself. A file that’s listed but won’t open is still missing.

  1. Keep the file safe

This export is protected health data the moment it leaves the old system. HHS has pushed back its big Security Rule update, and the current rule stays fully in force until a new one replaces it. Before the file arrives, write down three names, the person who can download it, the person who checks where it’s stored, and the person who can approve deleting it later. Add the transfer to your current risk analysis.

Even a perfect file doesn’t tell you what your new EHR will do with it.

3. Get the New Vendor’s Data Mapping in Writing

The mapping document decides which of your old data turns into usable, searchable data in the new EHR. Anything that doesn’t map lands as a flat document or doesn’t land at all.

  1. Don’t rely on standards labels

Federal standards only set the minimum. ONC released USCDI v7 on July 23, 2026, and it adds 31 new data elements and two new data classes. But certification still only requires USCDI v3, and v6 became available for voluntary certification on August 29, 2026. So when a vendor says it’s “v7-ready,” that doesn’t mean it has to import those fields. Get the mapping in writing, field by field. 

Questions to ask the new vendor for each data type

Data typeAsk this
MedicationsDo strength, dose, route and status all carry over?
AllergiesDo reaction and severity stay attached?
Lab resultsDo units and normal ranges come through?
Problem listDo codes keep their original meaning?
NotesDo author, date and visit stay linked?
AttachmentsDoes each file stay tied to the right visit?
  1. Test medication matching yourself

Certification may soon stop covering this, so see it working with your own eyes. The HTI-5 proposal would drop the clinical information reconciliation criterion starting January 1, 2027. No final HTI-5 rule had been published as of September 27, 2026, but the contract you sign now will last longer than that decision. Ask the vendor to merge your own test patients’ imported medication and allergy lists into their active lists during a live demo. 

  1. Set simple patient matching rules

A wrong match puts one person’s history in someone else’s chart. These are the rules we set with every practice.

  • Never auto-merge two records just because the name and birth date match
  • Send any record with conflicting details to one named reviewer
  • Keep unclear records locked until that person signs off
  • Clean up obvious duplicates in the old system before the export, since fixing them there is faster

This matters more than most practices expect. In small-practice exports, we usually find that about 2 to 4 in every 100 patient records are duplicates or near-matches. Families who share a name across generations and patients who changed last names cause most of them.

  1. Decide what happens to data that won’t map

For each field that won’t map cleanly, pick one option up front.

  • Convert it into the new format, and get the vendor to explain how
  • Attach it as a document linked to the right patient
  • Archive it in the old system and note where it lives

Know the trade-off with attachments. An old medication saved only as a PDF is still readable, but it never reaches the active medication list. That means drug interaction checks won’t see it. Anything a provider needs for current prescribing should be converted, not attached.

Once the mapping is signed, the next job is proving the vendor followed it.

4. Check the Test Import Against the Source

Checking a test import means comparing actual values, units, dates and patient links against the export. Matching totals alone don’t prove much, because a full count can still hide wrong numbers.

  1. Pick your test patients by risk

We have practices start with about 30 patients, chosen on purpose.

  • Patients on five or more medications
  • Patients with a recent abnormal lab result
  • Patients with known allergies
  • Anyone flagged as a near-match in step 3
  • Patients with an open balance or a recent claim denial
  • A handful of long-time patients with many years of history

Have a provider check the clinical charts and your billing lead check the financial ones. Each person should know what “right” looks like in their own area.

  1. Look wider when a mistake repeats

One wrong value in one chart is usually a one-off. The same wrong value in two charts usually means a bad mapping rule, and it’s probably in hundreds of charts you haven’t opened yet. In our experience, around 70% of import issues trace back to a single mapping rule, not to random typos. When you see a repeat, stop and ask the vendor to fix the rule, then re-run the import and recheck.

  1. Keep one issue list

Track every problem in a single list with these columns.

  • What’s wrong and which patients it affects
  • How serious it is
  • What caused it
  • Who’s fixing it
  • When it was retested
  • Whether it’s closed

One list keeps everyone looking at the same picture. Separate lists for clinical, billing and technical problems end up contradicting each other.

  1. Make sure the new EHR logs changes

Your issue list only holds up if the new system records who touched migrated data. HTI-5 also proposes dropping the audit report, integrity and accounting of disclosures certification criteria. If that becomes final, certification would no longer prove your new system logs changes to imported records. 

So put it in your contract. During a demo, check that the system saves who imported each record, when it happened and every edit made afterward. Then ask to see that log for one of your test patients.

With clean test results and a working log, you’re ready to make the call on go-live.

5. Make a Clear Go-Live Call

Go-live should be a yes or no decision based on a short list of conditions. A date on the calendar shouldn’t decide it (see why EHR go-lives fail).

What must be true before you say yes

AreaMust be true
Patient matchingNo unresolved high-risk matches
Medications and allergiesTest patients match the source
Open tasksEvery item has an owner
BillingTest claim accepted by clearinghouse
PrescribingTest eRx reaches a pharmacy
LabsTest order sent and result received
Old systemRead-only access confirmed in writing

Who signs off

Pick three people, one lead provider, your practice manager and your billing lead. Each one signs off on their own area. If one says no, you wait. A one-week delay costs far less than a month of fixing charts while you’re seeing patients.

How we suggest running the first week

  • Cut the schedule: Book about 50 to 60% of your normal patient load for the first week. Staff will be slower, and that’s normal.
  • Start with simpler visits: Put follow-ups and routine visits first, and save complex new patients for week two.
  • Keep one person free: Choose a team member who doesn’t see patients that week and handles questions and issues.
  • Meet for 15 minutes daily: At the end of each day, go through new issues and add them to your list.
  • Check claims early: Submit your first batch within two or three days so payer rejections show up fast.

Most practices we work with feel back to normal speed in about three to four weeks, well inside a typical 90-day EHR go-live timeline. Billing usually takes a little longer to settle than clinical work.

The old system still matters during all of this, because it’s your backup for anything the import missed.

6. Shut Down the Old EHR Without Losing Access

Retiring your old EHR is the last step, and it’s the easiest one to rush. Once you lose access, anything you didn’t move is gone.

A. Keep read-only access for a while

Plan to keep read-only access for at least 90 days after go-live. That covers most of the questions that come up, like a patient asking for an old record, a payer asking about an old claim or a provider who needs an old note.

Test it before you need it. Once a month, have someone pull one old chart and one old attachment. If retrieval doesn’t work, you’ll find out on your own schedule, not when a patient is waiting.

B. Shut things down in the right order

  1. Confirm every item on your handover list is closed
  2. Confirm old claims are paid, denied or moved to the new system
  3. Turn off old lab, pharmacy and clearinghouse connections so nothing gets sent to the wrong place
  4. Save a final archive copy of the full export in a secure location
  5. Cancel the old contract

Doing it in this order means nothing new lands in the old system after your team stops checking it.

C. Plan how long you’ll keep the archive

Record retention rules depend on your state and the payers you bill. Check with your compliance advisor and write down three things.

  • How long you must keep the archive
  • Who’s allowed to open it
  • Who can approve deleting it when that time comes

Put a reminder on the calendar for the deletion date. That way the decision gets made on purpose, not by accident years later.

D. Note where everything lives

Make a one-page guide for your team that shows where to find each type of old record. List what’s in the new EHR as structured data, what’s attached as a document and what’s only in the archive. New staff who join after the switch will need this the most, because they’ll never have used the old system.

Dr Girirajtosh Purohit

Dr. Giriraj Tosh Purohit is an experienced Product Manager and Security officer with a strong background in healthcare technology and management consulting. With expertise spanning clinical workflows, EHR, RCM, Digital Health, and AI-driven products, he has been instrumental in shaping innovative healthcare solutions.