Inventory behavioral health EHR migration sources, data categories, exports, historical context, ownership, and acceptance evidence before scheduling cutover.
A migration source inventory should identify each data category, authoritative system, export evidence, historical context, decision owner, and acceptance test before the cutover plan is finalized. A project called EHR migration can involve much more than a single database export.
This guide describes discovery and acceptance planning for behavioral health organizations. It does not authorize data deletion, set retention periods, or promise that every historical item can be imported into a new product. Use qualified clinical, financial, privacy, legal, and technical review for the actual scope.
Behavioral health EHR migration source inventory starts with categories
List patient identity, demographics, requests, episodes, clinical records, plans, signatures, attachments, appointments, coverage, authorizations, charges, claims, payments, reporting definitions, and other relevant local data. The actual inventory depends on the organization's systems and services.
The ASTP/ONC EHI export test method provides a certification-related export reference. Export capability and a successful receiving-system migration remain separate questions, so inspect the actual files and intended use.
Do not begin by assuming every category belongs in the same destination workflow. A historical attachment, current appointment, and active balance can have different operational needs. Assign a decision owner before selecting an import method.
Identify authoritative sources and overlapping copies
The EHR may not be authoritative for every category. Intake information can live in a CRM, balances in billing, appointments in another calendar, and supporting documents in a separate repository. Identify the source actually used by staff.
Record overlapping copies and differences. A patient address in several systems may not match, and the newest timestamp may not automatically identify the correct source. Authorized owners should decide the review process rather than allowing a migration script to resolve ambiguity silently.
Use a fictional inventory walkthrough with one person represented across intake, clinical, and billing systems. Ask each department to identify the authoritative values and the evidence supporting them. That reveals assumptions before mapping begins.
Preserve identifiers and relationships
Inventory patient, request, episode, encounter, document, appointment, claim, and transaction identifiers where relevant. Relationships between records can be as important as individual fields.
The ASTP/ONC SAFER patient identification guide provides a primary safety reference. Follow the organization's approved identity process when linking source systems or reviewing possible duplicates.
Do not infer that two records belong together solely because a name matches. Likewise, a changed name or contact detail does not necessarily establish a new person. Record uncertain matches and their authorized review owner.
Inspect actual exports early
Obtain representative export evidence through approved access and agreements. Review formats, field definitions, date coverage, identifiers, attachments, signatures, amendments, and known limitations. A vendor statement that export exists does not establish its practical completeness for the intended use.
Ask who can produce the export, what assistance or commercial dependencies exist, and how long the actual process takes. Record evidence rather than assuming a generic timeline. The receiving team needs usable samples before committing to detailed mapping and acceptance.
Use fictional or appropriately authorized samples in a safe environment. Keep sensitive source data out of sales demonstrations and broad project documents. The inventory can describe categories and evidence locations without copying every record.
Define destination decisions category by category
| Inventory field | Decision it supports |
|---|---|
| Category and scope | What information is actually included? |
| Authoritative source | Which system and owner establish the value? |
| Historical context | Which dates, versions, and attribution matter? |
| Export evidence | What files and documentation are available? |
| Destination | Imported workflow, historical view, or another approved route? |
| Acceptance | How will staff verify meaning and usability? |
| Dependency | What agreement, configuration, or manual work remains? |
Have authorized leaders decide retention and access questions. This guide does not establish that a historical item can be discarded simply because it is not imported. A destination choice and an ongoing record obligation are different decisions.
Keep active operational data distinguishable from historical evidence. A current balance or future appointment needs a different validation from an older signed note retained for reference.
Include meaning and usability in acceptance
A row count can identify missing data but cannot establish that users can find and interpret it. Test identity, episode context, dates, authorship, attachments, versions, and the actual receiving workflow.
For a fictional signed note with an amendment, ask the receiving reviewer to explain the history. For a future appointment, ask the scheduler to locate and change it through the approved process. For a balance, ask finance to reconcile the supporting evidence.
Record differences and limitations explicitly. A historical document imported as a readable attachment can be useful while still differing from a native structured record. The buyer should understand the tradeoff before acceptance.
Use the inventory to build the cutover plan
Identify extraction, mapping, import, validation, final updates, and staff-readiness dependencies. A calendar date chosen before those steps are understood can conceal unresolved work rather than create certainty.
Assign clinic and vendor owners for each category. Clarify who answers source questions, who performs technical work, who validates clinical or financial meaning, and who authorizes acceptance. The importer should not approve its own output on behalf of every department.
Track source changes during the project. New records, corrected data, changed templates, or added locations can affect mappings and final updates. Define how those changes are captured and reviewed before cutover.
Put scope and exclusions in the proposal
Ask vendors to identify included categories, formats, historical representation, dependencies, manual work, and acceptance evidence. Distinguish demonstrated import capability from future development or assumptions about a source export not yet inspected.
Keep a concise unresolved list with owners and next actions. A broad promise to migrate everything is less reviewable than a category-level scope that explains what the organization will receive and how it will verify it.
Ease Health publishes this guide and offers a unified CRM, EHR, and RCM platform for behavioral health. Ask vendors to demonstrate the proposed migration scope using actual export evidence and safe test cases. Related material includes the EHR overview, CRM-to-EHR field handoff guide, and switching guide.
The useful result is an inventory that turns migration from an assumption into a set of owned, testable decisions. It gives the project a clearer basis for scope, timing, and acceptance.
Related reading
Frequently Asked Questions
Is the existing EHR the only migration source?
Not necessarily. Relevant data may also live in intake, billing, scheduling, document, reporting, or external systems. Inventory the actual sources and identify which system is authoritative for each category.
Does an available export mean the receiving system can use everything directly?
No. Export access, mapping, import capability, historical representation, validation, and workflow usability are separate questions. Test the actual source and destination.
What should a migration inventory contain?
Include category, source, owner, scope, date coverage, identifiers, format, attachments or history, export method, destination decision, acceptance evidence, and unresolved dependencies.
Should every historical item be migrated into the same active workflow?
Do not assume that. Authorized clinical, financial, privacy, legal, and operational leaders should decide what is imported, retained through another approved route, or otherwise handled under applicable obligations and agreements.
