Migrate your Upvio data

Patient records are the central object in Upvio's data model. We map standard fields (name, contact, date of birth, medical history notes) directly to the destination CRM's contact or patient object. Custom properties on patient records require field-level mapping before transfer.

Practitioner profiles include credentials, specialty, and availability settings. We transfer practitioner records as users or staff records in the destination system, preserving role and department assignments where supported.

Appointment records include datetime, duration, practitioner, patient, status, and type. We map appointment records to the destination's calendar or bookings object, preserving the original scheduling data. Recurring appointment series are exported as individual records and rebuilt as recurring patterns on the destination if that feature is supported.

FaceScan records store the biometric image capture and associated metadata. These are proprietary Upvio objects tied to the Vitals AI pipeline. We export FaceScan metadata and preserve scan timestamps and session IDs, but the raw image data and AI-processed results must be treated as structured JSON blobs requiring destination-specific parsing.

Vitals AI generates health marker results (heart rate, blood pressure trends, HRV, stress indicators) as AI-processed output. These live in a proprietary JSON schema unique to Upvio's computer-vision pipeline. We extract and flatten the key health metrics into standard fields where possible, but AI confidence scores and raw signal data require manual review post-migration.

Forms are used for intake, intake history, and patient questionnaires. We export form structure and response data. Complex conditional logic, branching rules, and custom validation settings may not transfer automatically and must be rebuilt on the destination platform.

Secure messaging between practitioners and patients is stored as threaded conversations. We export message content, timestamps, sender, and recipient. Attachments and inline media must be exported separately and re-linked in the destination.

Video consultation records track session metadata (participant, duration, start/end time) rather than the recording itself. Where a recording exists, we flag it for separate file export. Session links and Zoom/Meet integration tokens are not portable.

Client portal configurations define what patients can access and how. We export the portal configuration as structured data. White-label settings, custom branding, and domain configurations require manual reconstruction on the destination.

Billing records include invoice amounts, payment status, and transaction history linked to appointments. We export billing records as line items or invoice objects. Integration-linked payment records (Stripe, PayPal) may not transfer with payment status intact and should be reconciled post-migration.

Customized workflows and automations within Upvio are platform-specific configurations that do not export via API. We document the existing workflow logic during discovery so it can be manually rebuilt on the destination platform.

White label functionality including custom domain, branding, and subdomain settings are stored in Upvio's infrastructure and cannot be exported. These must be manually reconfigured on the destination platform.