Switching EHR systems in a behavioral health practice comes down to six steps. Read your exit terms, map your data, request the export, check a sample of patients, run both systems for a short overlap, then cut over. Most of the risk sits in three places. Records land on the wrong chart, the export leaves data out, and billing history has nowhere to go.
This guide is for the owner or practice administrator who has to run the switch. It covers what moves, the rules specific to behavioral health and a week by week plan. It ends with the checks to run before go-live and the questions for both vendors.
- What moves cleanly in an EHR migration, and what needs a manual check
- Psychotherapy notes, 42 CFR Part 2 records and controlled substance prescribing
- A six step plan with an owner for each step
- Eight common problems, and how to catch each one
- What leaving your current system costs, and what to ask before you give notice
When is switching EHR systems worth it?
A switch is worth it when the current system blocks how the practice bills, documents or grows, and a setting change will not fix it. Plenty of complaints are fixable without moving. Rule those out first, because a migration costs months of staff attention.
| What you are seeing | What it costs the practice | Fixable without switching? |
|---|---|---|
| Claims go out through a separate tool and get rekeyed | Staff time and avoidable denials | Sometimes, if the EHR has a clearinghouse integration you are not using |
| Notes take clinicians into the evening | Burnout, late notes, late claims | Partly, with templates; rarely if the note editor itself is the problem |
| No behavioral health templates or scales | Clinicians build workarounds in free text | Rarely, if the vendor serves mostly medical practices |
| Controlled substance prescribing runs in a second system | Two logins, two records of the same patient | Only if the vendor adds certified EPCS |
| Intake and scheduling live outside the chart | Double entry at the front desk | Sometimes, through an integration |
| Reporting needs an export to a spreadsheet | Owners decide on stale numbers | Sometimes, with a reporting add on |
| Support tickets take days | Problems sit open while revenue waits | No. This is the vendor |
| Price rises with every clinician you add | Growth costs more than it should | Only by renegotiating |
If three or more rows describe your practice, a switch usually pays back. If one row does, fix that row first. For a side by side of the systems built for this work, see our mental health EHR comparison.
What data moves when you switch EHR systems?
Structured data moves well. Documents move as files. Anything typed into an odd place moves badly or not at all. A 2020 review of EHR transitions in Applied Clinical Informatics warns about the second group. In its words, "embedded content can cause data inconsistencies and compromise patient safety."
| Data | Usually arrives as | What to check |
|---|---|---|
| Patient demographics | Structured fields | Duplicates, missing date of birth, guarantor for minors |
| Insurance and coverage | Structured fields | Primary and secondary order, member IDs, termed plans |
| Appointments | Structured, future and past | Timezone, recurring series, provider mapping |
| Visit notes | Documents, sometimes text | Date of service, signing clinician, the right chart |
| Psychotherapy notes | Often excluded or mixed in | Kept separate from the medical record |
| Diagnoses and problem list | Structured codes | Active versus resolved, ICD-10 version |
| Medications | Structured list | Active list is current; prescription history is reference only |
| Questionnaire scores (PHQ-9, GAD-7) | Often PDF documents | Whether score history can be trended in the new system |
| Uploaded files and scans | Files | Count per patient matches the source |
| Memos, phone notes, messages | Often not in the export | Ask whether they are included before you pay |
| Consents and releases | Documents | Expiry dates, 42 CFR Part 2 consents |
| Charges, payments, balances | Reports or a ledger file | Open A/R by patient and payer ties out |
| Claims history | Reports or 837 files | Whether open claims can be worked after cutover |
Two rows cause most of the trouble: items the export never contained, and financial history. Ask about both in writing before you sign anything.
What file formats will your EHR export arrive in?
Expect a mix. Each format suits some data and fails on other data, so ask the new vendor which ones they can load before you order anything.
| Format | Usually carries | What the new vendor can do with it |
|---|---|---|
| CSV or XLS | Demographics, insurance, appointments, charges | Load as structured data after mapping |
| C-CDA (XML) | A clinical summary per patient | Load problems, medications and allergies; notes vary |
| Signed notes, letters, scanned forms | Attach to the chart as documents; not searchable as data | |
| DOC, DOCX or HTML | Note text | Attach as documents, or parse into notes if the layout is consistent |
| JPEG or other images | Scans, ID cards, insurance cards | Attach to the chart |
| 837 files | Claims as they were sent to payers | Reference for open claims; rarely loaded as history |
| Aging and ledger reports | Balances by patient and payer | Starting balances in the new system |
| ZIP archive | Any of the above, bundled | Unpack and sort before loading |
What is different when a behavioral health practice switches EHRs?
Four rules change how a behavioral health migration runs. None of them apply to a general medical practice, so a general migration checklist will miss them.
| Rule | What it means in a migration | Source |
|---|---|---|
| Psychotherapy notes are kept apart from the medical record | Map them to a separate, restricted note type. Do not load them into the general chart. | 45 CFR 164.501 |
| Substance use disorder records from a Part 2 program carry extra limits | Flag Part 2 records and their consents so the restriction travels with them. | 42 CFR 2.12, 2.32 |
| Controlled substance e-prescribing needs DEA compliant setup | Plan time for each prescriber to set up EPCS in the new system before go-live. | 21 CFR Part 1311 |
| Measurement-based care depends on score history | Check that PHQ-9 and GAD-7 history arrives as scores you can trend. | Practice standard |
| Minors have guardians, consents and sometimes split access | Map guardians, portal access and consent forms per patient. | State law |
| Record retention is set by state law | Keep read access to the old system, or an archive, for the full retention period. | State law |
HIPAA defines psychotherapy notes as notes "separated from the rest of the individual's medical record". The same definition excludes start and stop times, medications, diagnosis, the treatment plan, symptoms and progress. Those belong in the progress note. If your current system mixes the two, the migration is the moment to split them. Our guide to psychotherapy notes covers the line in detail.
We map your data, migrate it and train your team in a 4-week program
BOOK A DEMO →How do you switch EHR systems step by step?
Six steps, in this order. Each one has a single owner. Shared ownership is how migrations stall.
1. Read your exit terms
- Find the notice period and the renewal date in your current contract.
- Find the price, format and turnaround of a full data export.
- Ask how long the vendor keeps exported files and your login after you cancel.
- Do not give notice until the new system is live and checked.
- Owner: practice owner.
2. Inventory and map your data
- List every data type in the table above and mark which ones you need.
- Decide how much history to move. Some practices move two years and archive the rest.
- Map note types, appointment types, providers and locations to the new system.
- Decide where psychotherapy notes and Part 2 records will live.
- Owner: practice administrator, with the new vendor's migration lead.
3. Request the export
- Order the full export early. Some vendors take weeks.
- Certified health IT must support an export of all electronic health information for a patient population (45 CFR 170.315(b)(10)).
- Run the free reports too: demographics, open claims, A/R aging, charges.
- Store the files somewhere the whole team can reach before the vendor's retention window ends.
- Owner: practice administrator.
4. Load and check a sample
- Load the data into the new system before anyone uses it for real visits.
- Pick at least 20 patients across every type: child, couple, Part 2, high balance, long history.
- Compare each one against the old system, field by field.
- Fix the mapping and reload. Do not hand fix records one at a time.
- Owner: the new vendor, checked by your billing lead and one clinician.
5. Run both systems for a short overlap
- New visits go in the new system from day one.
- Old claims are worked to a close in the old system.
- Keep the overlap short. Two weeks is easier than two months.
- Train each role on the tasks it does daily: front desk, clinicians, billing.
- Owner: practice administrator.
6. Cut over and keep read access
- Run a final delta export for anything created during the overlap.
- Reconcile open A/R by payer between the two systems.
- Give notice only after the checks pass.
- Keep read-only access, or an archive, for your state's retention period.
- Owner: practice owner.
How much patient history should you migrate?
| Option | Good for | Trade-off |
|---|---|---|
| Active patients only | Fastest load, smallest cleanup | Returning patients need history pulled from the archive |
| Active patients plus 2 to 3 years | Group practices with steady caseloads | Older records stay in the archive |
| Everything | Practices with long treatment episodes | Largest cleanup and longest check |
| Structured data only, documents archived | Tight timelines | Clinicians open the archive for old notes |
Whichever you choose, keep the rest readable for your state's retention period.
How do you map note types when switching EHR systems?
Every note type in the old system needs a home in the new one. Decide this before the first load, because changing it later means reloading everything.
| Old note type | Where it should land | Watch for |
|---|---|---|
| Intake or diagnostic evaluation | Initial evaluation note | Linked to the first date of service |
| Progress note | Progress note | Signing clinician and date of service |
| Psychotherapy note | Restricted psychotherapy note type | Access limited to the treating clinician |
| Medication management | Psychiatric follow-up note | Prescriber mapped correctly |
| Treatment plan | Treatment plan | Active plan flagged, old versions kept as history |
| Group note | Group note, copied to each member | Other members' names kept out of each chart |
| Family or couples session | Session note under the identified patient | Filed on the identified patient's chart |
| Discharge summary | Discharge note | Episode closed in the new system |
| Phone note or memo | Communication note | Often missing from the export |
| Letters and outside records | Documents | Attached to the right patient and date |
A clean treatment plan makes this easier. Our treatment plan template shows the structure payers look for.
What should you ask your current vendor before you give notice?
- What does a full data export include, data type by data type?
- Are memos, phone notes and patient messages in the export?
- Is billing history included, or only demographics and appointments?
- What formats will the files arrive in?
- What does the export cost, and is it priced per practice or per file?
- How many business days from request to delivery?
- How long are the files kept after delivery?
- Can the files be released directly to our new vendor?
- When does our contract renew, and what notice is required?
- Can we keep read-only access after we cancel, and at what price?
How long does an EHR migration take?
For a small or mid-size behavioral health practice, plan on about a month of active work once the export is in hand. The export itself can take longer to arrive than the migration takes to run, so order it first.
| When | What happens | Who |
|---|---|---|
| Before you sign | Read exit terms, price the export, choose the new system | Owner |
| Week 1 | Export arrives, data is mapped, first load into the new system | Administrator and vendor |
| Week 2 | Templates, scheduling rules, billing codes and payers configured | Vendor and billing lead |
| Week 3 | Role based training; sample check of 20 or more patients | All staff |
| Week 4 | Go live; final delta export; old claims worked to close | Everyone |
| After go-live | A/R reconciled, notice given, archive kept | Owner and billing lead |
Larger systems take far longer. The Applied Clinical Informatics review describes hospital transitions "requiring dozens to hundreds of additional staff". A group practice is a different scale, but the same order of steps applies.
Who does what during an EHR migration?
| Task | Owner | Signs off |
|---|---|---|
| Contract, notice and export order | Practice owner | Practice owner |
| Data inventory and mapping decisions | Practice administrator | Practice owner |
| Data extraction and load | New vendor | Practice administrator |
| Note templates and scales | New vendor | Clinical lead |
| Payer setup and clearinghouse enrollment | Billing lead | Practice administrator |
| Sample patient check | Billing lead and one clinician | Practice administrator |
| EPCS setup per prescriber | Each prescriber | Clinical lead |
| Staff training | New vendor | Practice administrator |
| Open claims in the old system | Billing lead | Practice owner |
| Archive and retention | Practice administrator | Practice owner |
What goes wrong in an EHR data migration?
The same eight problems show up across migrations. Each one is cheap to catch in the sample check and expensive to find after go-live.
| Problem | How it shows up | How to catch it |
|---|---|---|
| Duplicate charts | One patient appears twice, with history split across both | Search the new system for matching name and date of birth |
| Documents on the wrong chart | A child's notes appear on a parent's record | Check families and shared guarantors in the sample |
| Dates shifted by timezone | Visits land a day early or late | Compare dates of service for evening appointments |
| Items missing from the export | Memos, phone notes or messages never arrive | Count documents per patient, old versus new |
| Financial history has no home | Open balances are missing or doubled | Tie out A/R by payer before cutover |
| Provider mapping errors | Notes signed by the wrong clinician | Check the signing clinician on sampled notes |
| Psychotherapy notes in the general chart | Restricted content visible to billing staff | Check note type and access on sampled therapy patients |
| Scores arrive as PDFs | No trend line for PHQ-9 or GAD-7 | Open one patient's score history in the new system |
How do you check migrated data before go-live?
Check a sample, fix the mapping, reload, check again. Run this list on every sampled patient.
- Demographics match, including date of birth and guarantor.
- Insurance is in the right order, with current member IDs.
- Visit count matches the old system for the history you chose to move.
- Each note has the right date of service and signing clinician.
- Document count per patient matches the export.
- Psychotherapy notes sit in the restricted note type.
- Part 2 records carry their consent and restriction.
- Active diagnoses and medications are current.
- Questionnaire score history is present and readable.
- Future appointments are on the right day and time.
- Patient balance and insurance balance match the old system.
- Open claims are listed, with a plan for who works them.
What should go-live week look like?
| Day | Focus | Done when |
|---|---|---|
| Day 1 | All new visits documented in the new system | Every clinician has signed one note |
| Day 2 | Front desk schedules and checks in from the new system only | No appointments created in the old system |
| Day 3 | First claims submitted from the new system | Clearinghouse accepts the batch |
| Day 4 | Prescribers send prescriptions from the new system | EPCS works for every prescriber |
| Day 5 | Review of issues raised during the week | Each issue has an owner and a date |
| Week 2 | Final delta export from the old system | Overlap records loaded and checked |
| Week 3 to 6 | Old claims worked to close; A/R reconciled | Old system holds no open work |
Signs a migration is off track
- The export has not arrived and go-live is two weeks away.
- Nobody has checked a sampled patient field by field.
- Staff are still documenting in the old system after go-live.
- Claims from the new system are rejected for payer setup reasons.
- A prescriber cannot send controlled substance prescriptions.
- Open A/R in the two systems does not tie out.
- Duplicate charts keep appearing in search.
- Notice has been given before the checks passed.
See how mdhub migrates your patient records and clinical history
BOOK A DEMO →What does it cost to leave your current EHR?
The new subscription is the visible cost. The exit costs are easy to miss, so price each one before you give notice.
| Cost | What to ask |
|---|---|
| Data export fee | Is a full export included, or priced per data type or per file? |
| Export turnaround | How many business days from signed request to files? |
| Retention of exported files | How long can you download them after delivery? |
| Notice period and renewal | When does the contract renew, and how much notice is required? |
| Overlap licence | Can you keep the old system for open claims, and at what price? |
| Read-only archive | Is read access available after cancellation, and for how long? |
| Staff time | How many hours will the administrator and billing lead spend? |
| Data cleanup | Who fixes duplicates and mapping errors, and is it included? |
Tebra is one example. Its Data Services export page, updated December 4, 2025, prices a billing export at USD 1,000 and a clinical export at USD 250. A notes and documents export is USD 2,000 for up to 20,000 files. Tebra quotes completion within 30 business days and keeps exported data for 3 months. Check your own vendor's current terms.
Should you keep your old EHR after switching?
Keep read access for a while. Long legacy access changes the plan. The Applied Clinical Informatics review says practices then "may choose to migrate less data, and postpone decisions on a patient-by-patient basis." That trades a smaller migration for a longer overlap.
- Keep the old system until every open claim from before cutover is paid or written off.
- Keep read access, or a full archive, for your state's record retention period.
- Remove write access on cutover day, so nobody documents in the wrong place.
- Write down where the archive lives and who can open it.
What should you ask a new EHR vendor about migration?
- Which source systems have you migrated from, and what did you move?
- Who does the extraction, mapping and load: you or us?
- Is migration included in the onboarding fee?
- How many years of history do you recommend moving?
- Do psychotherapy notes land in a separate, restricted note type?
- How are 42 CFR Part 2 records and consents flagged?
- Do questionnaire scores arrive as data we can trend?
- How are open balances and claims history handled?
- Can we check a sample before go-live?
- How do you find and merge duplicate charts?
- How long does EPCS setup take per prescriber?
- Who is our contact after go-live, and for how long?
EHR migration checklist
The whole guide on one screen. Copy it into your project tracker.
- Contract renewal date and notice period found.
- Export price, format and turnaround confirmed in writing.
- Memos, phone notes and billing history confirmed in or out of the export.
- Amount of history to migrate decided.
- Note types, providers, locations and payers mapped.
- Psychotherapy notes and Part 2 records given a restricted home.
- Business associate agreement signed with the new vendor.
- Export ordered and stored where the team can reach it.
- First load done and 20 or more patients checked field by field.
- EPCS set up for every prescriber.
- Staff trained by role.
- Go-live date set, overlap period agreed.
- Final delta export loaded after the overlap.
- Open A/R reconciled by payer.
- Notice given and read-only archive arranged.
How does mdhub handle an EHR migration?
mdhub runs migration as part of a structured 4-week program. Our implementation team migrates your patient data, configures your workflows and trains your staff.
| Week | What happens |
|---|---|
| Week 1: Discovery and data migration | We audit your existing EHR, map your data structure and begin migrating patient records and clinical history |
| Week 2: Configuration and workflow setup | Clinical templates, scheduling rules, billing codes and AI agent settings are configured to how your clinic operates |
| Week 3: Staff training | Role based sessions for providers, front desk and billing teams |
| Week 4: Go live with dedicated support | Your clinic goes live with a dedicated implementation manager on call |
Details are on our behavioral health EHR page. For the wider category, see our guide to behavioral health software.
Switching EHR systems FAQ
How long does it take to switch EHR systems?
For a small or mid-size behavioral health practice, about a month of active work once the data export is in hand. The export can take several weeks to arrive, so order it first.
What data transfers when you switch EHRs?
Demographics, insurance, appointments, diagnoses and medications usually move as structured data. Notes and uploads move as documents. Memos, phone notes and billing history often need a separate export or report.
Can you migrate psychotherapy notes to a new EHR?
Yes. Map them to a separate, restricted note type. HIPAA defines psychotherapy notes as kept separate from the rest of the medical record.
What happens to unpaid claims when you switch EHRs?
Work claims from before cutover to a close in the old system, then reconcile open balances by payer before you cancel it.
Do I need to keep my old EHR after switching?
Keep read access or an archive for your state's record retention period, and until old claims are closed. Remove write access on cutover day.
Does my current EHR have to give me my data?
Certified health IT must support an export of all electronic health information for a patient population, under 45 CFR 170.315(b)(10). Vendors may still charge for the export service.
How much does it cost to export data from an EHR?
It varies by vendor. Tebra, for example, lists exports from USD 250 to USD 2,000 on its help center. Ask for the price, format and turnaround in writing.
What is the biggest risk when switching EHR systems?
Records on the wrong chart and data the export never contained. A field by field check of at least 20 sampled patients before go-live catches most of it.
How do 42 CFR Part 2 records move to a new EHR?
Flag them during mapping so the consent and restriction travel with the record. Disclosures made with consent must carry the notice set out in 42 CFR 2.32.
When is the best time to switch EHR systems?
After you have priced the export and before your contract renews. Avoid the first weeks of January, when insurance changes are heaviest.
Do patients need to sign new consent forms when we switch EHRs?
For HIPAA purposes the practice remains the covered entity, so routine treatment consents usually carry over. Sign a business associate agreement with the new vendor. Portal or telehealth consents tied to the old vendor may need re-signing.
Will patients need a new portal login?
Usually yes. Patients get an invitation to the new portal. Tell them before go-live so the invite does not look like spam.
Can we migrate only active patients?
Yes. A common approach is to move active patients and a set number of years of history, and keep the rest in a read-only archive for the retention period.
Who should own an EHR migration in a group practice?
One person, usually the practice administrator, with the owner signing off on the contract and the cutover date. Shared ownership is how migrations stall.
Streamline Your Practice
Switching EHR systems goes well with three habits. Read the exit terms first, check the data on a sample, and keep the old system readable. mdhub runs that as a 4-week program with your team. Book a demo to see the plan for your practice, or start a free trial to try the product first.
