Migrate from Phreesia to Nutshell

Phreesia patient records map directly to Nutshell People. Demographic fields (name, date of birth, address, phone, email) transfer as standard Nutshell People fields. Primary email and phone serve as required identifiers for Nutshell People creation and are mandatory for successful record migration.

Phreesia stores insurance carrier, member ID, group number, and eligibility status with no native Nutshell equivalent. FlitStack creates custom text fields (Insurance_Carrier__c, Member_ID__c, Group_Number__c) on the Person record. Real-time eligibility verification requires a separate integration as Nutshell does not support live eligibility checks natively.

Phreesia appointments with datetime, provider name, location, and type transform into Nutshell Activities. The appointment datetime becomes the task due date, provider maps to the assigned user (or a custom field if unresolved), and status determines whether the task is open or completed in Nutshell.

Phreesia captures clinical screening results (PHQ-9, social determinants, health risks) as discrete intake responses. These migrate to custom fields on the Person record — nut shell's custom field types (text, pick-list, number, date) determine how each screening maps. Multi-select screenings become multi-select custom fields if available, otherwise comma-separated text.

Phreesia consent signatures with timestamps map to Nutshell as PDF attachments on the Person record (consent forms) plus a custom datetime field (Last_Consent_Signed__c) for renewal tracking. Nutshell does not have native consent management — renewal reminders require manual workflow setup.

Phreesia payment amounts, dates, and methods (card on file, time-of-service) migrate as completed Activities with descriptions capturing the payment details. A custom number field (Total_Payments__c) on the Person record provides a running balance for accounts receivable tracking across all historical payments.

Phreesia provider and staff names resolve to Nutshell Users by email match. Unmatched staff are flagged as contacts on Person records with a custom field (Phreesia_Staff__c). Nutshell's user model does not support healthcare-specific roles (provider, nurse, front desk) — these map to Nutshell's standard user role system.

Phreesia custom intake questions become Nutshell custom fields on the Person record. Free-text responses migrate as custom text fields; structured responses map to pick-list or number fields based on response type. Long-form text responses can also attach as Notes for reference.

Referral source, referring provider, and referral date stored in Phreesia migrate to custom fields on the Person record (Referral_Source__c, Referring_Provider__c, Referral_Date__c). Referral status tracking requires a separate Nutshell workflow or external tool to manage ongoing referral pipeline visibility.

Phreesia recall automation and campaign messaging have no Nutshell equivalent. These workflows must be rebuilt in Nutshell email sequences (Pro tier) or a separate marketing automation tool. FlitStack exports Phreesia campaign configuration as a detailed rebuild reference to guide the reconstruction process.

Phreesia bidirectional EHR and PM integrations with Epic, eClinicalWorks, NextGen, and other systems do not migrate to Nutshell. Since Nutshell has no native healthcare integration, teams must re-establish connectivity through third-party middleware using HL7 FHIR connectors, Zapier, or custom API development after cutover.