Migrate your Phreesia data

Patient demographics in Phreesia map directly to patient records in destination PM/EHR systems. We export full name, contact information, date of birth, and address fields and write them to the destination's patient object with a 1:1 mapping.

Insurance capture and eligibility/benefits verification results are stored per patient visit. We export the payer name, plan details, group number, and E&B check timestamp and write them to the patient's insurance tab in the destination system.

Phreesia captures electronic signatures for HIPAA agreements, financial policies, and clinical consents. Custom consent templates vary by organization and appointment type. We export consent type, capture date, signature method, and expiration date, then map to the destination's equivalent consent or authorization object, flagging any custom consent types that lack a standard counterpart.

Phreesia administers patient-reported screenings including social risk, behavioral health, and clinical intake questionnaires. These screening results are structured by visit and question logic. We export the screening type, question text, response value, and visit linkage, noting that screening question banks differ by organization configuration.

Visits in Phreesia are linked to intake records, screenings, and payments but are not the authoritative appointment record—that lives in the PM/EHR. We export the visit date, provider, appointment type, and intake completion status, then link these to the destination appointment record using the external ID.

Payment records include the amount, payment method, transaction status, and PM posting status. We export transaction details and reconcile against the destination's payment or ledger object, noting that some payment plan configurations require manual review due to Phreesia's internal payment schedule logic.

Referral records include referring provider, referral type, status, and notes. We export referral data and map to the destination's referral or order object, flagging any referral sources that are not recognized in the destination system.

Custom intake forms and the fields within them are configured per organization. We export the form schema, field labels, and patient responses, then map each custom field to a destination field using the organization's field mapping documentation. Custom fields that cannot be mapped to standard destination fields are flagged for manual review.

Phreesia stores time-of-service collections, outstanding balances, and card-on-file configurations. We export balance amounts, payment plan terms, and collection status, mapping to the destination's accounts receivable or billing record, noting that closed balances may need to be reconciled differently from open balances.

Phreesia does not serve as the authoritative system for staff accounts—provider and staff credentials live in the PM/EHR. We do not migrate staff accounts from Phreesia. If the destination is not the PM/EHR, staff account provisioning is handled separately by the customer's IT team.