Can I Transfer Years of Client Records to a New EHR?

Yes, in most cases. What migrates as structured data, what moves as documents or stays archived, how retention and export rules apply, and cutover order.

Yes. A behavioral health organization can bring years of client history into a new EHR, but the history does not all travel the same way. Active clinical and financial data moves as structured fields the new system can use. Older notes and signed forms usually move as documents attached to the chart. The rest stays in a read-only archive that you keep for as long as the retention rules in your state call for.

The real work is deciding which records go where, then proving afterward that nothing was lost. Ease is the unified platform where migrated records land in one system covering clinical, admissions, and billing history, so switching does not scatter your data across tools.

This guide covers what typically migrates, what stays behind, the rules that shape those choices, validation, and cutover order across several sites.

Can I transfer years of client records to a new EHR?

In most cases, yes. What decides it is how the old system stores the records, what it can export, and what the new system can import into a usable field. Age matters less.

Sort the history into three tiers:

1. Structured data. Fields the new EHR reads and acts on: demographics, diagnoses, medications, allergies, active treatment plans, and open balances.
2. Documents. Historical notes, assessments, and signed forms carried over as files, often PDFs, attached to the right client.
3. Archive. Everything else, kept read-only in the old system or in an export, searchable when someone asks for it.

A good migration plan puts every record type in one of the three tiers before any data moves. Without that decision, teams default to bringing everything, which makes field mapping and validation the slowest part of the project. Our implementation timeline guide explains why migration usually takes the most calendar time.

What usually migrates as structured data

Structured migration is for the information staff need on day one, in a form the new system can sort, alert on, and bill from. For most behavioral health organizations that list includes:

• Demographics and contacts. Name, date of birth, identifiers, addresses, guarantors, emergency contacts, and insurance policies.
• Diagnoses. Active and historical diagnosis codes, mapped to the code set the new system uses.
• Medications and allergies. Current medication lists and allergy records, so prescribers and nurses see them before the first visit in the new system.
• Active treatment plans. Problems, goals, objectives, and interventions for clients currently in care, so the next progress note has a plan to attach to.
• Upcoming appointments and care teams. Who is seeing whom, where, and when.
• Open balances. Patient balances and, when the plan calls for it, open insurance receivables at the claim level.

Each of these needs a map from the old field to the new one. Code sets are the usual trouble spots: payer lists, location and program codes, staff identifiers, and custom picklists that one system stores as free text and the other stores as a fixed list of values.

What usually moves as documents instead of data

Years of closed episodes rarely justify field-by-field mapping. Historical progress notes, completed assessments, discharge summaries, scanned intake packets, and signed releases usually move as documents. The common format is a PDF per note or per episode, filed under the right client and dated so clinicians can find it.

That keeps the clinical story available without forcing old templates into today's note structure. The tradeoff is that a PDF cannot drive reports or outcome measures, so decide which historical scores need to come over as data.

Plan separately for psychotherapy notes that clinicians keep apart from the main record. ONC's certification guide for the export criterion states that "EHI does not include psychotherapy notes as defined in 45 CFR 164.501" (healthit.gov). If your clinicians keep them, a standard export may leave them out, so ask the old vendor how to retrieve them and decide where they will live.

Billing history follows the same split. Closed claims, remittances, and payment history usually stay as reports or in the archive, since few teams need to rebill a claim from years ago. Open receivables are a separate decision, covered in the section on parallel systems below.

What usually stays in a read-only archive

The archive holds what you are obligated to keep but rarely use: full audit trails, superseded document versions, old messages, claim-level detail for closed years, and the records of clients discharged before the cutoff date you choose for migration.

An archive is only useful if it still works when someone needs it. Before the old contract ends, confirm four things:

• Authorized staff can search it by client and date and produce a complete record.
• Access is limited to the people who need it, and that access is logged.
• It will last at least as long as your longest retention period.
• A named person owns it and handles record requests after the old vendor is gone.

If the old vendor will not host a read-only copy, a full patient-population export plus a documented way to read it can serve as the archive.

How long you have to keep the old records

Retention periods come from more than one rule, and they vary by state and by record type, so check the rules in each state where you deliver care.

At the federal level, the CMS fact sheet on 42 CFR 424.516(f) tells Medicare providers and suppliers covered by that rule to "maintain medical records for 7 years from the date of service" (CMS). State law can set longer periods, and the longest period that applies is the one your archive has to cover. Our mental health record retention guide walks through state-by-state periods.

Substance use disorder treatment records can carry extra federal rules under 42 CFR Part 2. SAMHSA's laws and regulations page says Part 2 sets "restrictions concerning the disclosure and use of patient records" for substance use treatment records that federal programs maintain (SAMHSA). Read the HHS guidance that page links to, and bring your privacy officer into migration planning before those records move.

The EHI export your current EHR should already support

You are not starting from a locked box. ONC's certification criterion for electronic health information export, 45 CFR 170.315(b)(10), covers two kinds of export: all of a single patient's EHI, and all the EHI for a patient population, in each case limited to EHI the product can store at the time of certification (healthit.gov).

Under that criterion, export files are electronic and in a computable format, with a link to the format documentation included. The same guide notes that the criterion "does not specify a predefined data set," so what an export includes differs by developer and product (healthit.gov). Ask your current vendor for the format documentation early, because it is the starting point for every field map.

Two cautions apply. A computable file still has to be mapped field by field before the new system can use it. And the export covers the EHI the product could store at the time it was certified, so check custom forms and later customizations separately.

If a vendor slows or conditions access to your data, the information blocking rules may come into play. ONC describes information blocking as a practice "likely to interfere with the access, exchange, or use" of EHI, subject to listed exceptions, and the 21st Century Cures Act applies those rules to developers of certified health IT as well as to providers (healthit.gov).

Ease Health's EHR is ONC Health IT certified (CHPL listing 11073), and its EHI export instructions are published on a public page.

Data mapping and validation steps

A migration is finished when the people who use the data sign off on it. A workable sequence:

1. Inventory every source. The EHR, plus spreadsheets, a separate billing system, the admissions tracker, and scanned files on shared drives.
2. Set scope and cutoffs. Decide which tier each record type lands in, and pick the cutoff date that separates active clients from archived ones.
3. Map fields and code sets. Build the crosswalk for payers, locations, programs, levels of care, staff, diagnosis codes, and note types. Flag anything without a clean match for a person to decide.
4. Run a test load. Load a copy into a test environment and look for orphaned records, duplicates, and cut-off text.
5. Reconcile counts and totals. Client counts by status, appointment counts by location, document counts per client, and AR totals by payer should tie out between old and new, with every difference explained.
6. Spot-check charts. Have clinicians compare a sample of real charts side by side, including the hard ones: clients with several episodes, guardians, or more than one payer.
7. Repeat at the final load. Run the same checks on the production load at cutover and record the sign-off.

Give each check an owner. Clinical leads own chart accuracy, finance owns AR totals, and IT owns counts and access.

Running the old and new systems in parallel

Most organizations keep the old system running for a period after go-live, in a limited role. Agree on that role in writing before cutover:

• Read-only for clinical history. Staff look things up in the old system but document only in the new one, so no client has notes split across two live charts.
• Old receivables worked to completion. Many teams finish claims for dates of service before cutover in the old system and bill everything after cutover from the new one. Migrating open AR is the alternative, and it works best when balances reconcile cleanly at the claim level.
• One cutoff for new data. A single date after which new admissions, appointments, and charges exist only in the new system.
• An end date for the old contract. Set it after AR is worked down and the archive is confirmed usable, and pull a final patient-population export before access ends.

Parallel running costs license fees and staff attention, so keep it narrow. Our guide to switching behavioral health EHRs covers the vendor side.

Cutover order for multi-site organizations

Organizations with several locations rarely move every site on the same day. A phased cutover lets the team learn on one site and carry the fixes to the rest. Common ordering rules:

• Start with a site that is typical and stable. It should run your most common level of care and payer mix, with a manager who can absorb some disruption.
• Group sites that share clients. If clients step down from residential to outpatient across two locations, move those locations together so one episode is not split across systems.
• Keep billing entities together. Sites that bill under the same tax ID or billing provider are easier to reconcile when they move in the same wave.
• Reuse the validation checklist. Each wave gets the same counts, totals, and chart spot-checks as the first.

Within Ease, a multi-state or multi-location group runs every site on one instance, with each location carrying its own state, time zone, NPI, and billing provider, so a site that moves in a later wave is added as another location on the same instance. Our multi-location overview covers what to look for when one record has to serve many sites.

How Ease handles a move from another EHR

Ease's in-house implementation team runs configuration, data migration, setup, and training. Migrated records land in one system, because CRM, EHR, and RCM are one product with one login and one patient record. Admissions history, the chart, and the billing ledger share one destination.

Before signing with any vendor, settle these questions in writing:

• Which record types come over as structured data, which as documents, and which stay in the archive.
• Who builds and approves the field map, and who signs off on validation.
• How open AR will be handled at cutover.
• What the new vendor needs from your current vendor's export, and by when.

Frequently Asked Questions

Can I transfer years of client records to a new EHR?

Usually, yes. Active data such as demographics, diagnoses, medications, allergies, treatment plans, and open balances typically migrates as structured data. Older notes and signed forms usually move as documents, and the rest stays in a read-only archive kept for the retention period that applies in each state where you deliver care.

Are psychotherapy notes included in an EHI export?

Not necessarily. ONC's certification guidance for the EHI export criterion says EHI does not include psychotherapy notes as defined in the HIPAA Privacy Rule at 45 CFR 164.501. If clinicians keep separate psychotherapy notes, ask the current vendor how to retrieve them and decide where they will be stored.

What happens to open claims when we switch EHRs?

Organizations either finish working claims for dates of service before cutover in the old system, or migrate open balances at the claim level into the new one. Running them out in the old system is simpler when balances do not reconcile cleanly. Either way, finance should tie AR totals out between the two systems before signing off.

How long do we need to keep the old EHR's records?

It depends on the state and the record type, and the longest period that applies sets how long the archive has to last. For Medicare, a CMS fact sheet on 42 CFR 424.516(f) tells providers and suppliers covered by that rule to keep medical records for 7 years from the date of service. State law can set longer periods.

Can our current EHR vendor hold our data back?

A product certified to ONC's EHI export criterion, 45 CFR 170.315(b)(10), supports an export of a single patient's EHI and an export of the whole patient population's EHI, in a computable format with format documentation. Under the 21st Century Cures Act, the information blocking rules also apply to developers of certified health IT.

Does Ease migrate data from a previous EHR?

Yes. Ease's in-house implementation team runs configuration, data migration, setup, and training, and migrated records land in one system, since CRM, EHR, and RCM are one product with one login and one patient record.