Migrate from Phreesia to Twenty CRM

Phreesia Patient records map directly to Twenty People records. Core demographics (name, date of birth, address, phone, email) migrate as standard Twenty fields. Medical record number (MRN) and Phreesia patient ID are stored as custom fields for traceability and delta-run de-duplication.

Phreesia Insurance is a linked object on Patient — carrier name, policy number, group number, subscriber ID, and relationship to subscriber do not map to any standard Twenty field. FlitStack creates a custom object with these fields and links each Insurance Record to the corresponding People record via a relation field.

Phreesia consent records (HIPAA, treatment consent, financial policy) contain e-signature timestamps and document metadata. We migrate the consent type, capture date, and signer name as a Twenty Note on the People record, and attach the original PDF as a file linked to that Note.

Phreesia captures clinical screening responses (PHQ-9, blood pressure, glucose, allergies, medications) as structured or free-text data. We create a custom Clinical Screening object with relevant fields and link it to the People record; raw response text migrates as a Note attachment for audit continuity.

Phreesia Appointment records include date, time, provider name, appointment type, and status. These map to Twenty Tasks: Task.name becomes the appointment type, Task.dueAt maps to the appointment datetime, and the provider name migrates as a custom field on the Task record.

Phreesia Payment records (amount, date, method, status, description) do not map to any standard Twenty object. We create a Payment custom object linked to the People record, storing amount as currency, date as a date field, and payment method as a select field.

Phreesia provider and staff records are resolved by email against Twenty WorkspaceMembers. Unmatched providers are flagged before migration — your team either invites them to Twenty first or assigns records to a fallback member. Provider specialty and credentials migrate as custom fields on the WorkspaceMember record.

Phreesia intake forms generate structured responses (demographic updates, insurance corrections, social history). We extract key field values into custom fields on the People record and attach the completed form as a Note for reference. Highly structured responses may warrant a custom intake-response object.

Phreesia Enterprise setups may include custom intake objects for specialty programs, site-specific workflows, or organization-defined data structures. These custom Phreesia objects map 1:1 to Twenty custom objects, preserving field types and pick-list values where possible. If a custom Phreesia object uses N:N relationships (such as a patient enrolled in multiple programs), FlitStack creates the corresponding junction records and relation fields in Twenty during migration to maintain the relationship graph.

Phreesia files attached to patient records include insurance cards, ID scans, signed consent forms, and clinical documents. These files re-upload to Twenty as file attachments linked to the corresponding Note or People record, preserving original file names and upload timestamps where available. Your Twenty hosting configuration determines applicable file size limits — we verify compatibility during the pre-migration audit and flag any files that exceed your hosting tier's constraints.

Phreesia's revenue-cycle management, eligibility verification logic, and payment collection workflows are platform-native constructs that cannot be extracted via CSV or API. We export all available workflow definitions, rule configurations, and automation sequences as reference documents for your team to evaluate. These exports serve as blueprints for rebuilding critical revenue-cycle processes in Twenty's workflow builder or integrating a dedicated billing tool such as Stripe, Chargebee, or a specialized medical billing platform.