Migrate your Lifeline Suite data

Patient records export cleanly in the Constituents file. We map the primary patient identifier, demographics, contact fields, and insurance metadata. Dates are normalized to ISO-8601 at import time. Soft-deleted or archived patients require a separate archive query against the export.

Encounter records carry encounter date, type, provider, and diagnosis codes. The CPT and E/M codes Lifeline stores are preserved verbatim — we do not recode them, as downstream billing may depend on exact values. Encounters without a linked patient are flagged for manual resolution before import.

Appointment slots export as part of the Encounter or schedule module. Timezone handling requires explicit confirmation at scoping — Lifeline does not always store timezone metadata alongside appointment timestamps. We apply the org's configured timezone as a default and flag ambiguous records.

Invoice and payment history lives in the Revenue Cycle Management module. Lifeline's invoice schema does not map 1:1 to most CRM invoice objects. We chunk invoice-line records and apply a transformation mapping that the customer reviews during the dry-run phase. Outstanding AR balances are preserved as read-only fields.

E-claims export with carrier ID, plan ID, status codes, and adjustment reason codes. Lifeline's proprietary status codes (such as carrier-specific rejection codes) require a customer-supplied lookup table to map into standard ANSI 835/837 codes. We flag unmapped codes and defer them for manual assignment.

Referring doctors and referring hospitals appear as distinct entity types in the Codes file. We normalize both into a single Provider/Referring Physician object in the target system, with a type flag to preserve the distinction. NPI numbers are mapped where present.

Referring hospitals are stored as institutional entities with address and contact details. Where the destination CRM does not have a separate institutional object, we merge them into Companies/Accounts and tag them with a referral-source label.

Medical inventory items in the Codes file carry item class, unit cost, and supplier references. Lifeline's internal taxonomy for item categories does not map directly to standard product catalog structures. We create a flat mapping at import time and flag items with unmapped categories for customer review.

Insurance plan associations link Patients to carriers and plan IDs. Plan names vary by employer group and contract year, so there is no stable global lookup. We import plan metadata as custom fields and do not attempt to normalize carrier names across Lifeline's naming conventions.

Binary attachments (scanned documents, imaging links, signed forms) export as a separate file bundle with no guaranteed parent-record association in the filename. The export does not include a manifest linking file names to encounter or patient IDs reliably enough for automated re-association. We extract the file bundle and deliver it alongside the migration report for manual re-association post-import.