When your practice decides to move to a new EHR (electronic health records), one of the first questions that comes up is “what about the data?” You’ve got years of patient records, appointment history, clinical notes, and billing information living inside your current system, and all of it needs to go somewhere.
Here’s the short version. An EHR data migration isn’t one thing, it’s three: demographic, appointment, and clinical, each on its own timeline. Two of them tend to surprise practices. Your clinical data moves after go-live, not before, and your financial data doesn’t move at all. The rest of this page walks through what transfers, what doesn’t, and what to have ready before your first call.
A quick note on terms before we go further. You’ll hear this work called EHR data conversion, medical data migration, or just “the conversion.” Whether you’re making the transition to EHR for the first time or transitioning from one EHR to another, it’s the same set of moving parts, and it’s what we walk through on every conversion call.
The three types of conversion
When we talk about data conversion, there are three categories. Each one covers different data and runs on a different timeline, so the fastest way to see the shape of it is side by side.
| Conversion type | What it covers | Timing |
| Demographic | Patient identifiers: names, contact information, insurance details | At least 6 weeks before go-live |
| Appointment | Scheduling history: past visits and future appointments | At least 8 weeks before go-live |
| Clinical | Chart documents, visit notes, discrete clinical data | After go-live, then 6–8 weeks to complete |
The timing column is where most of the planning lives, so here’s what sits behind each one.
Demographic conversion
Demographics are the baseline information that identifies who your patients are. This is usually the first piece to move, because your new system needs to know who your patients are before anything else can happen.
Because patient data migration needs at least six weeks before go-live, the process starts well before your practice is anywhere near switching systems. If your implementation timeline is tight, this is one of the first things to lock down.
Appointment conversion
Appointment data is your scheduling history, and it’s critical for practices that need continuity in their scheduling workflow from day one. Past visits, future appointments, the record of when patients were seen and when they’re coming back: all of it has to land in the right place on the new platform.
Appointments need at least eight weeks, longer than demographics, because the data is more complex. Mapping your old system’s scheduling structure to your new one takes more time to get right.
Clinical conversion
Clinical is the big one. This is your chart documents, your visit notes, your discrete clinical data: the full record of what happened in every patient encounter.
Here’s the part most practices don’t expect: the clinical conversion doesn’t happen before go-live. It happens after.
The reason makes sense once you hear it. Your providers are documenting in your current system right up until the day you go live on the new one, so if we pulled the clinical data before that, we’d miss everything documented in those final weeks. Instead, we wait until your charts are signed off and closed out in the old system. Your old vendor then extracts a snapshot of the complete clinical record, and we convert from that.
From the time we receive those documents, the clinical conversion usually takes six to eight weeks to complete on our end.
Before go-live, you’ll receive a sample of your converted data loaded into the new system. Take that review seriously. Every issue you catch during the sample review can be fixed before go-live. Every issue you miss becomes something your clinical staff discovers while treating patients.
What to do while the clinical conversion is running
This is the part where most practices get nervous. You’re live on your new system and your providers are documenting there, but the historical clinical data hasn’t moved over yet. So what do you do when someone needs to look up a patient’s history from before the switch?
The short answer is to keep two tabs open. Here’s how that works in practice:
- Document everything new in your new EHR, the way you normally would.
- For the interim, click back into the old system whenever you need to view historical chart notes.
- Keep read-only access or downgraded licenses on your legacy system for about 90 to 120 days after go-live.
That window covers the clinical conversion and gives your team a safety net while the historical data is being moved. Nobody loves running two systems at once, but it’s temporary, and it beats rushing the conversion and ending up with incomplete records on the other side.
The clinical conversion isn’t the only reason you’ll need that legacy access, though.
Financial data doesn’t transfer
This one catches more practices off guard than almost anything else.
Generally speaking, your financial data doesn’t move from one EHR to the next. This is a structural reality of how EHR systems handle financial records, and it’s true in most cases regardless of which systems are involved.
The logic holds up. The claims you’ve already created in your current system have been submitted, they’re tied to a specific clearinghouse, and the revenue cycle is already in motion. Moving that mid-stream would create more problems than it solves, and you don’t want a pause in your cash flow.
So instead, you do what’s called a billing wind-down. Once you’re live on your new EHR, you bill all new visits out of that system. Everything already in the pipeline stays in the old system, and you work it down over time. That wind-down usually runs 90 to 120 days after go-live, which is the other reason the legacy access we mentioned matters.
Once you’ve worked the old billing down to a point where you feel comfortable, you can manually enter any remaining balances into the new system. But the full financial history stays where it is.
Financial data isn’t the only thing that falls outside the scope of a standard conversion.
Non-standard data and custom work
Standard conversions cover demographics, appointments, and clinical data. But every now and then, there’s data that doesn’t fit neatly into those three categories.
If your practice needs something outside the standard scope, there’s an option called a document build (sometimes called PDF conversion or archiving). If we can run a report on the information and tie it to a patient, we can build a PDF version of that data and place it under the patient’s attachment section in your new EHR. It’s not the same as a native conversion, but it gets the information into a format your providers can access from within the new system.
There are also situations where your practice has data feeds from third parties built into your current system. Maybe you’re receiving information from an insurance carrier that flows directly into your EHR, and that connection was set up years ago by someone who may not even work there anymore.
When you switch systems, that connection doesn’t automatically come with you. In those cases, we can build interfaces, the connections that bridge your new EHR with those outside data sources so the flow continues.
These aren’t part of a standard conversion, and we don’t bring them up on the initial call because they add cost and complexity to a deal that needs to close first. But once the conversion is underway and these needs surface, there’s usually a path to solving them.
What adds cost and complexity to a conversion
Not every conversion is the same amount of work. A three-provider practice moving off a modern cloud-based system is a very different project than a 50-provider group with 10 locations coming off a legacy server-based platform that’s no longer supported.
Most of the EHR data migration challenges that affect your EHR data migration cost and timeline come down to a handful of factors:
- How old your current system is. Older systems create harder extractions, because the data formats are less standardized and the export options are more limited.
- Server-based vs. cloud-based. If your current EHR is cloud-based and we can access the data directly, the extraction is straightforward. Server-based systems are harder.
- Whether the vendor still supports it. If your system is no longer supported, or the vendor controls access, you may have to pay an EHR data extraction fee to get your own data out. That cost comes from your old vendor, not the conversion partner, and it’s worth raising early.
- How many providers and locations you have. Larger groups mean more coordination, more patient data, and more moving pieces during implementation.
- Whether you have third-party data feeds or interfaces. These need to be accounted for separately and can add custom work.
If your current vendor has gone through an acquisition or sunset, getting access to your data may require working through channels that don’t move as fast as your timeline needs them to. None of this makes a conversion impossible, and we’ve handled all of these scenarios. But knowing where your practice falls before the first call means fewer surprises and better planning on both sides.
What to have ready before your first conversion call
Your first call goes a lot faster when you’ve thought through a few things ahead of time. You don’t need any of this perfectly documented, but a general picture of your environment gets you to a realistic plan faster.
- What system you’re currently on, and whether it’s cloud-based or server-based
- How many providers and locations you have
- Any third-party data feeds or integrations built into your current system, even if you’re not sure how they work
- Whether your current vendor charges an extraction fee, and their timeline for releasing data
- How your billing is set up and who manages the revenue cycle, since the wind-down conversation involves them
- Any non-standard data you rely on, like custom reports or document templates, flagged early
The sooner a conversion team knows about the non-standard items, the sooner they can tell you what’s possible and what might require custom work.
Where Focus comes in
We’re usually the last piece of the puzzle when a practice switches EHRs, and it helps to know how the relationship works. Your EHR vendor sells the software and handles implementation and training. We handle the EHR data migration services under a separate contract, working directly with your practice and alongside the implementation so everything comes together at go-live.
There are three common entry points: before you’ve signed with your new vendor, during implementation when a project manager realizes a conversion needs to be added, or after an acquisition when you’re bringing a new practice onto your platform.
The reason practices trust us with this is the track record. We’ve completed more than 2,000 data conversions across 100+ EHR systems, and we’ve never missed a go-live. We also make it work when the timeline gets tight. Recently a group going live in six weeks needed an appointment conversion added on, which is less time than we’d normally want, and we made it work without charging extra.
When a deal needs to close and the conversion is the last piece, we don’t let the timeline be the reason it falls apart.
As your Unified Partner we handle IT, security, and data together, so the conversion is often just the first conversation of many.
Frequently asked questions
What are the three types of EHR data conversion?
Demographic conversion moves patient identifiers: names, contact information, and insurance details. Appointment conversion moves scheduling history, both past visits and future appointments. Clinical conversion moves chart documents, visit notes, and discrete clinical data. Each one runs on its own timeline and has its own scope.
Why does the clinical conversion happen after go-live?
Your providers are documenting in your current system right up until go-live day. Pulling clinical data before that would miss the most recent notes. Instead, the old vendor extracts a complete snapshot of the clinical record after charts are signed off and closed out. We convert from that snapshot, which usually takes six to eight weeks.
Does financial data transfer between EHR systems?
No, and this is industrywide. Your existing claims, clearinghouse connections, and revenue cycle activity stay in your old system. You do a billing wind-down over 90 to 120 days after go-live, working those balances down while billing new visits out of your new system.
What is a document build?
If your practice needs data converted that falls outside the standard demographic, appointment, or clinical scope, a document build can pull that information into a PDF format and place it under the patient’s attachment section in your new EHR. It requires the data to be reportable and tied to a patient.
How long should I keep access to my old EHR after switching?
We recommend maintaining read-only access or downgraded licenses on your old system for 90 to 120 days after go-live. This covers the clinical conversion window and the billing wind-down period, and gives your team a way to reference historical records while the conversion is completing.
How do I know if my conversion will be complex?
The main factors are the age and type of your current system, your practice size, and whether you have third-party integrations. Server-based systems, legacy platforms that are no longer supported, multi-location groups, and practices with outside data feeds all add complexity. None of it is unmanageable, but knowing where you fall helps set realistic expectations from the start.
When does Focus typically get involved in an EHR transition?
There are three common entry points: before you sign with your new EHR vendor (when the sales team wants to give you the full conversion picture), during implementation (when the project manager identifies a conversion need), or after an acquisition (when your group brings a new practice onto your platform). In all three cases, our contract is separate from the EHR agreement, and we work directly with your practice.