DrChrono / EverHealth → EnWella
Two paths: CSV export and the DrChrono API. When to use each, and the column mappings EnWella applies.
- Updated
- Updated
- Reading time
- 5 min read
- Tags
- migrationdrchronoeverhealthcsvapi
DrChrono (now EverHealth) supports two export paths: a CSV export from the admin UI, and an API-based pull. Both land in the same EnWella migration wizard. This article covers when to use each, how to authorize the API path, and which mappings differ from the Practice Fusion route.
CSV vs API — which path to use
Use the CSV export if you are under 10,000 active patients and want to finish in one weekend. Use the API pull if you are over 10,000, if you want incremental syncs while you trial EnWella in parallel, or if your DrChrono plan does not include the bulk export tool (some legacy plans do not). The API path takes longer to authorize (1–2 business days for DrChrono to issue OAuth credentials) but does not require an admin to babysit the export.
CSV export path
In DrChrono: Account → Practice Settings → Data Export. Tick Patients, Appointments (12 mo), Insurance, Problem list, Medications, Allergies, Immunizations, Documents. DrChrono ships the export as a ZIP attached to an email within a few hours. Drop the ZIP into EnWella's migration wizard. Everything works the same as the Practice Fusion path from there.
API pull path
Tell EnWella you want the API path. We provide a one-page authorization form that you send to DrChrono support; they reply with OAuth client credentials within 1–2 business days. Once we have the credentials, the importer pulls your data directly — no CSV to manage. We pull on a configurable schedule (one-time, or hourly during a parallel-run window). The API exposes one detail the CSV does not: DrChrono's internal chart_id separately from the user-visible mrn. We preserve both so cross-references in your scanned PDFs continue to resolve.
Mapping differences from Practice Fusion
DrChrono stores gender in a free-text field; EnWella normalizes it against the FHIR administrative-gender value set (male, female, other, unknown) and parks unmatched values for review. DrChrono appointment "profiles" become EnWella appointment types — we ship a default mapping but encourage you to review it before go-live. DrChrono custom forms export as PDFs attached to the visit; if you want the structured-data version, the API path can pull form responses as JSON and we map them into our Intake Forms surface.
Frequently asked questions
We just renewed DrChrono for a year. Can we run both?
Do you import DrChrono e-prescribing history?
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.
Athenahealth → EnWella
How to leave Athena without leaving money on the table. Export menu paths, claims handover, and the % collections gotcha.