Leaving eClinicalWorks is less about the new tool and more about getting your data out of the old one. That part is slow and often fee-bearing. In at least one reported case, a practice was told extraction would take four to five weeks, and third-party trackers put migration around $500 to $1,500 per provider. So plan the export as a real project with a timeline and a budget, then keep the first week on the new system focused on today’s visits, not a decade of history. This guide walks both.
If you’re still pricing the decision, our eClinicalWorks cost breakdown covers the base fee plus the per-encounter Sunoh scribe. This page picks up after you’ve decided to move.
Key takeaways
- Data extraction from eCW can take weeks. One reported switch was quoted 4 to 5 weeks; plan accordingly.
- Export often carries a fee. Third-party trackers cite ~$500 to $1,500 per provider for migration.
- eCW’s 2017 DOJ settlement required data transfer on request, but some customers reported non-compliance, so push early.
- C-CDA export covers structured clinical records; billing history and archives may need a separate service.
- First week on the new tool is about running current visits cleanly, not migrating everything at once.
Why getting data out of eClinicalWorks is the hard part
Most migration guides start with the new tool. This one starts with the exit, because that’s where practices get stuck.
When a healthcare organization asked about switching away from eClinicalWorks, per Healthcare IT News, they were told it would take four to five weeks to get their data out. That’s not a download; that’s a project. Practices have also reported being pushed to keep paying while extraction dragged, rather than getting a clean glide path to close out accounts receivable. Other vendors, the same reporting notes, give departing customers a smoother off-ramp. eCW’s reputation on this is the reason to plan hard.
There’s a legal backdrop too. eCW’s 2017 DOJ settlement, which resolved a $155 million False Claims case, required the vendor to transfer customer data to a rival EHR on request. But some customers publicly reported that eCW hadn’t fully complied. So don’t treat the settlement as a guarantee of fast, free extraction. Assume you’ll have to actively push for your data, and start that conversation early.
Before you sign anywhere new, confirm the destination can take your data cleanly and give you a portable export back out.
What the export actually covers, and what it doesn’t
eCW supports C-CDA data portability, which lets you export clinical records and pick specific patient records before exporting. That’s the structured clinical piece, and it’s genuinely useful. What it doesn’t automatically hand you is everything.
| eCW data type | Extraction path |
|---|---|
| Structured clinical records | C-CDA data portability export |
| Full historical archive | Often a separate migration / archiving service |
| Billing and AR history | Frequently a paid extraction; plan a wind-down window |
| Documents and scanned files | Confirm coverage; may need bulk EHI export |
The practical read: your live clinical data can move via C-CDA, but the long tail, years of billing history, scanned documents, closed encounters, may need a separate paid extraction or a migration vendor. Third-party trackers put that migration around $500 to $1,500 per provider depending on volume. Ask eCW, in writing, exactly what the C-CDA export includes and what costs extra. The gap between those two answers is your migration budget.
Split your data into live and archive
Here’s the mindset that keeps a big-EHR switch from stalling: you do not have to move everything before go-live. Split the data.
Live data is what you need on day one: your active patient panel, current demographics, upcoming appointments, and recent clinical context. Move that first. Archive data is the history you look up but rarely edit: old billing, closed encounters, scanned records from five years ago. That can follow as a downloaded C-CDA and document set you keep accessible for reference, or via an archiving service if your specialty needs deep lookback.
This matters because trying to migrate ten years of history before you see a single patient on the new tool is how practices delay a switch for months. Run current visits cleanly first. Backfill the archive on its own timeline.
Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. It ships EHR-ready export (PDF, HL7, FHIR) on every plan, so whatever you bring in can also leave, which is the lock-in question you just learned to ask.
The first-week plan on a new EHR
The switch checklist, ordered so nothing blocks a patient visit.
- Get the eCW extraction quote and timeline in writing. Start this weeks before go-live, given the reported 4-to-5-week windows. This is the long pole.
- Trial the new tool on real visits. Confirm the note quality and the record flow hold on your actual patient mix, not a demo script. Run the 7-day trial.
- Import live data only. Active panel, demographics, upcoming appointments. Leave the archive for later.
- Set go-live on a low-volume week. Not month-end, not the Monday of a packed schedule. Brief your front desk on the new check-in and note flow.
- Keep eCW read-accessible. You’ll reference old charts and close out open AR for weeks. Cancel only after the new system holds a full clinic week and your export files are downloaded and backed up.
For the documentation-tool version of this cutover, our AI scribe migration checklist covers switching without losing a clinic day, and the pricing page lists exactly what ships per plan. Compliance sign-off details, encryption, access, audit status, are on the security page.
Protect your accounts receivable during the switch
The clinical data gets the attention. The money is where a rushed eCW exit quietly costs you.
When you flip to a new system, you still have open claims and unpaid balances sitting in eCW. Some vendors give departing customers a glide path: keep the old account read-accessible so you can work down existing accounts receivable while the new system runs current visits. The reporting on eCW’s DOJ-settlement compliance suggests you should not assume a generous off-ramp here. Plan for a wind-down window where you keep eCW live long enough to close out billing, even after clinical go-live on the new tool.
Practically, that means two overlapping timelines. Clinical cutover happens on your chosen go-live week: new visits, new notes, new scheduling. Billing cutover trails it, sometimes by a month or two, while your team finishes collecting on claims that were already in flight. Don’t cancel eCW the day you love the new EHR. Cancel it once the AR is worked down and your export files are safely in hand. A practice that rushes this can strand thousands in unpaid claims inside a system it can no longer log into. That’s an avoidable, expensive mistake, and it’s the one we’d flag hardest before you set a cancellation date.
When you should stay on eClinicalWorks
The honest counter-case, because a switch this heavy needs a real reason. Stay on eCW if billing depth runs your practice. Its revenue-cycle engine, claims workflows, and enterprise support are deep and battle-tested across large multi-provider groups. Patient Square offers ICD-10 suggestions to speed coding, not a claims-scrubbing platform, and it isn’t trying to replace a full RCM suite. If your evaluation centers on billing capability and scale, the export friction and switching cost probably aren’t worth trading that away.
Move if your day is mostly visits and notes, you’re tired of the per-encounter scribe meter climbing every busy Tuesday, and you want one predictable bill for documentation and the record. We think a lot of independent practices are paying enterprise-EHR prices for capability they never touch, and the flat bundle is the honest fit there. Run the 7-day trial on a real week, see the note against your own visits, and start the eCW extraction conversation early, because that timeline, not the new tool, is what decides your go-live date.