Migrate from Essential MD Software Suite to HighLevel

Essential MD API export is not a full medical record pull

Essential MD Software Suite exposes a limited API export — appointment records, patient demographics, and basic treatment fields are retrievable, but some data (detailed clinical notes, scanned charts, imaging attachments) may only be available as PDF exports or not at all via API. FlitStack AI audits the exportable field set during discovery and flags any data that requires manual extraction. Chart PDFs are re-uploaded as file attachments to the contact record, but structured field data that cannot be exported via API must be either manually keyed or accepted as not migratable.

ICD and diagnosis codes have no native home in HighLevel

Essential MD stores ICD-10 diagnosis codes and CPT procedure codes as structured fields on patient records. HighLevel has no native medical coding schema — those codes must be stored as custom text fields on the contact record. This means diagnosis data is visible in HighLevel but is not queryable by code (you cannot filter contacts by ICD-10 range using HighLevel's native search). FlitStack migrates the codes as custom text fields and optionally creates a separate custom object for diagnosis code lookups if the client needs structured querying post-migration.

HighLevel's workflow automations must be rebuilt from scratch

Essential MD embeds clinical workflow rules — appointment reminder sequences, clinical note templates, insurance verification triggers, and recall reminders — into the practice management logic. HighLevel's workflow builder is a blank canvas. The logic for appointment reminders, recall campaigns, and patient follow-up sequences needs to be re-implemented in HighLevel's workflow triggers (pipeline stage change, tag added, form submission). FlitStack AI exports the workflow definitions as a rebuild reference document, but the automation logic itself is not transferred. Budget and timeline for the workflow rebuild should be estimated separately from the data migration.

Medical billing and insurance data is reference-only post-migration

Essential MD integrates with medical billing clearinghouses and tracks claim status, payments received, and patient responsibility balances. HighLevel has no medical billing module — Stripe payment links and invoicing are available for service businesses but do not support insurance claim workflows or ERA/EFT remittance. Insurance carrier, policy number, group number, and coverage status are migrated as reference fields on the contact record, but active claims, outstanding balances, and billing history cannot be tracked in HighLevel. Practices with active billing cycles should plan a parallel billing system or a transition window before the Essential MD account is closed.

HighLevel's sub-account model affects data isolation post-migration

HighLevel's agency-tier plans use sub-accounts to isolate client data — each sub-account has its own contacts, pipelines, and workflows. If the migration involves a multi-location practice or an agency managing multiple client practices, sub-account architecture must be designed before data lands. FlitStack AI delivers a sub-account architecture plan as part of the migration scoping: which locations map to separate sub-accounts, which share a single sub-account, and how cross-sub-account reporting is handled. Data imported into the wrong sub-account structure requires a re-import.