Migrate from Upvio to Twenty CRM

Upvio user accounts with the Client role map to Twenty People records. We extract the account name, email, phone, address, and any client-specific custom properties and load them as Twenty People fields. Original account creation dates are preserved in a custom datetime field.

Upvio practitioner and staff user accounts map to Twenty Workspace Members (Settings → Members). We match by email address to link each practitioner to their correct Twenty identity. Invitations must be accepted before owner resolution can finalize. If a practitioner record lacks a valid email or no matching Twenty user exists, we flag it for manual assignment during pre-flight review to prevent incomplete ownership on migrated Tasks and FormResponse entries.

Upvio does not have a native Company object, but if your setup uses an organization or clinic name field on user accounts, we extract that into Twenty Companies. A People record is then linked via the companyId relation in Twenty.

Upvio appointments map to Twenty Tasks with the original start/end datetime preserved. The task assignee maps to the matched Twenty Workspace Member. Appointment status (completed, cancelled, no-show) becomes the Task status field. If the appointment generated a Stripe payment, a linked Opportunity record can be created for the billed amount.

Upvio form submissions contain multiple fields per response — we merge them into a single FormResponse custom object in Twenty, linked to the related People record via a relation field. Free-text responses that don't fit a structured field become Twenty Notes attached to the People record.

Upvio payment records (via Stripe or PayPal) that represent completed billable appointments can become Twenty Opportunities. The billed amount maps to the Opportunity amount, the appointment date becomes the expected close date, and the status (paid) maps to a Won stage or custom pick-list value.

Upvio secure chat threads are captured as Twenty Notes attached to the related People record. The note body contains the full thread text with timestamps. We preserve the channel label (secure-messaging, intake-chat) as a note category or tag for filtering in Twenty's view system.

Upvio client portal access data — login timestamps, last active session — has no native Twenty equivalent. We map this to custom fields on the People record (Portal_Last_Login__c, Portal_Access_Granted__c) created before import. This data serves as a reference signal for customer health scoring.

Upvio Vitals AI scan results (heart rate, blood pressure trends, HRV) are stored as structured data per scan. We create a VitalsScan custom object in Twenty linked to the People record, with fields for each biometric metric, scan date, and the session ID that generated the reading.

Any custom fields configured in Upvio intake forms that don't map to standard Twenty People fields are created as custom fields on the People or FormResponse object in Settings → Data Model before import. We document the full list during discovery so schema is ready before records land.

Upvio's native connections to Zoom, Google Calendar, Stripe, and PayPal do not have an equivalent in Twenty's data model. These connections terminate at decommissioning. We export the connection configuration as a JSON reference document so your team can rebuild them in Twenty using webhooks, Zapier, or the API.

Upvio appointment reminder and scheduling automations are platform-native and cannot be extracted. We export the automation logic (trigger events, timing rules, message templates) as a reference document for rebuilding in Twenty's workflow builder (Settings → Workflows). Scheduling workflows typically take 2–4 hours per automation to rebuild.