Athenahealth → EnWella
How to leave Athena without leaving money on the table. Export menu paths, claims handover, and the % collections gotcha.
- Updated
- Updated
- Reading time
- 6 min read
- Tags
- migrationathenahealthathenaonecsv
Athena is the trickiest of the common migrations — not because the data is hard to move, but because the contract terms and in-flight claims book usually take longer to unwind than the technical export. This article covers the export itself, what to do with claims still in motion, and the trap most clinics hit on the way out.
Where the Athena export lives
In Athena: Settings → Data → Export Center. Athena exposes a "Patient Data Export" tool that produces a multi-CSV ZIP. Select Patients, Appointments, Insurance, Problem List, Medications, Allergies, Immunizations, plus the Documents Archive tool (a separate workflow that bundles every PDF on a patient chart into a per-patient folder). Athena delivers both as downloadable ZIPs within 1–3 business days of the request.
In-flight claims — finish them on Athena
Do not migrate active claims. Athena's claim scrubber and clearinghouse round-trip is the part of their product that is hardest to replicate, and trying to bridge a claim mid-cycle is the fastest way to lose collections. Finish every claim that is in any state other than "paid" or "denied + closed" on Athena. We do import the historical claim list as read-only context, and we provide a parallel-run window so your billers can keep working in Athena until the last claim closes.
The % collections gotcha
Athena charges as a percent of collections. The day you stop sending new claims through Athena, your fee drops to whatever they bill on the runoff from in-flight claims. Plan the cutover for a date that gives Athena clean accounting (most clinics pick the 1st of the following month). Read the termination clause on your contract before you start — some plans require 90 days notice; some require return of branded materials. We provide a one-pager checklist on request.
Mapping notes
Athena uses internal patient department as part of its identity model — a patient can exist in multiple departments with separate chart numbers. EnWella collapses these into one patient record with a externaldepartmentids[] history field; if you operate multiple Athena departments you should configure each as an EnWella location before importing so the appointments map cleanly. Athena encounter-level billing modifiers import as visit-level modifiers in EnWella; if you need encounter-level granularity for a specific specialty (oncology, dialysis), talk to us — we have schema for it but it is opt-in.
Frequently asked questions
Athena says they "own" some of our customizations. True?
Can you pull from athenaCollector if we are on athenaOne?
Keep reading
Switching EHRs without losing a week
How EnWella moves your patients, appointments, insurance, problem list, medications, and chart docs off your current system — in a weekend, not a quarter.
Practice Fusion → EnWella
Step-by-step export menu paths, column mappings, and pitfalls when moving from Practice Fusion.