Migrate from Upvio to Salesforce Sales Cloud

Upvio patient records map directly to Salesforce Contacts. Standard fields including name, email address, phone number, street address, city, state, postal code, country, and date of birth all transfer cleanly. The Upvio internal patient ID is preserved as a custom Source_System_ID__c field on each Contact for traceability and de-duplication during delta-run reconciliation.

Upvio FaceScan outputs—including heart rate, HRV scores, blood pressure wellness trends, and health markers derived from remote photoplethysmography—have no native Salesforce equivalent. FlitStack creates a Vitals_Data__c custom object linked to each Contact via a lookup relationship, storing each biometric measurement as a named custom field (Heart_Rate_BPM__c, HRV_Score__c, Blood_Pressure_Trend__c, Stress_Level_Index__c). Scan timestamps are preserved to maintain longitudinal reporting continuity.

Upvio appointments map to Salesforce Events with original StartDateTime and EndDateTime preserved. The appointment status (confirmed, cancelled, no-show), service type, and assigned practitioner are stored as custom fields on the Event record. Video-conference links are stored as a custom text field for manual recreation in Salesforce after migration.

Upvio practitioners are matched to Salesforce Users by email address lookup. Practitioners with no matching Salesforce User are flagged in a pre-migration report so the team can invite them to Salesforce or assign a fallback OwnerId before migration begins. All existing appointments are re-attributed to the resolved owner to maintain accurate Salesforce reporting from day one.

Upvio intake forms, consent forms, and health-history questionnaires map to a custom Intake_Response__c object linked to each Contact. Each individual form field becomes a corresponding custom field on this object. Response submission timestamps and completion status are preserved to maintain audit trails and compliance records.

Upvio secure chat threads have no direct Salesforce equivalent. FlitStack creates a Task per message thread with a free-text body and a custom URL field pointing to a shared note location. Teams needing full chat history should use a dedicated secure messaging migration tool alongside this CRM migration.

Upvio custom properties per patient record—including insurance status, referral source, preferred language, emergency contact name, and emergency contact phone—are mapped to custom fields on the Salesforce Contact object with the __c suffix. Pick-list values in Upvio are mapped value-by-value to Salesforce pick-lists where a match exists, or stored as text fields where no equivalent pick-list value exists.

Upvio file attachments on patient records are downloaded and re-uploaded to Salesforce Files, linked to the corresponding Contact record. Standard Salesforce file size limits apply (25MB default per file, 2GB per library). Inline images embedded in patient record notes are downloaded and re-hosted as Salesforce Files attached to the contact.

Upvio organizations associated with a patient—such as employer-sponsored clinics, insurance provider referral sources, or affiliated healthcare networks—map to Salesforce Accounts. Parent/child organization hierarchies in Upvio are preserved using the Salesforce ParentId field on the Account object, ensuring the organizational structure is maintained in the destination system.

Upvio Vitals AI trend data containing multiple biometric readings over time per patient is stored as a custom Vitals_Trend__c object keyed by Contact and scan date. Trend timestamps are preserved to maintain longitudinal reporting continuity. This enables practitioners to track patient health metrics across multiple FaceScan sessions and generate trend reports within Salesforce.

If Upvio tracks billable services or recurring care episodes, these are mapped to Salesforce Opportunities with a custom Service_Type__c field and Amount reflecting the service value. For care episodes without a monetary amount, FlitStack maps the booking to a Salesforce Task with status and description fields preserving the service details for operational tracking.

Upvio consent form completions—including HIPAA consent, telehealth consent, and treatment consent—migrate to a Consent_Record__c custom object linked to each Contact. The consent type, signature date, and form version are stored as custom fields, enabling compliance auditing and regulatory reporting within Salesforce.