Migrate from Upvio to Zoho CRM

Upvio practitioners map directly to Zoho CRM Contacts. Zoho Contact requires First Name and Last Name — practitioners with a single display name populate Last Name and leave First Name blank. Email and phone fields map 1:1. Practitioner type or specialty maps to a custom pick-list field (Specialty_C) on Contact.

Upvio clients split based on engagement status: prospective clients without a completed appointment route to Zoho Lead; clients with at least one completed appointment route to Zoho Contact. The split is determined by checking appointment history in Upvio before migration runs. Zoho Lead uses the standard Name, Email, Phone fields; Contact links to the mapped Practitioner Contact.

Upvio appointments map to Zoho CRM Events with Start DateTime and End DateTime preserved from the source slot. Status (confirmed, cancelled, no-show) maps to Event Status pick-list. The practitioner assignment becomes the Event Owner lookup to the Contact record created from the Practitioner object. Client assignment becomes the Related To lookup to the Contact or Lead record.

FaceScan results (heart rate, blood pressure trends, HRV, health indicators) have no native Zoho CRM equivalent. FlitStack creates a FaceScans_C custom module with fields matching the Upvio scan schema, linked to the Contact record via a lookup. Individual scan metrics can also be stored as custom fields on the Contact for quick access in Zoho's record view.

Upvio Vitals AI scan data (blood pressure wellness trends, HRV, wellness scores) migrates as a linked Vitals_C custom module in Zoho CRM. Each Vitals record links to the Contact (client) who was scanned. Timestamps from the original scan are preserved in a custom DateTime field since Zoho's standard created date reflects the migration import date, not the original measurement date.

Upvio forms and questionnaire responses are linked to a Client record. Short free-text responses migrate as Zoho Notes attached to the Contact. Structured responses (multiple choice, rating scales) map to a custom Forms_C module with lookup to Contact, capturing question text, response value, and submission timestamp.

Upvio payment records (Stripe and PayPal transactions linked to appointments) can map to a Payments_C custom module if Zoho Books is not in use. Fields include Transaction ID, Amount, Currency, Status, and Linked Appointment (Event) reference. If Zoho Books is active, FlitStack maps to Invoice and Payment objects instead — requires Zoho Books connection setup.

Upvio practitioner availability and scheduling rules have no direct Zoho CRM equivalent. We preserve the availability data as a custom Availability_Rules__c long-text field on the Contact record for reference. Scheduling logic must be rebuilt using Zoho's Blueprint or Zoho Bookings if the full scheduling workflow is needed post-migration.

Any Upvio custom field created by the practice migrates to a Zoho CRM custom field on the mapped module. Field API name in Zoho matches the Upvio label exactly or uses the _C suffix convention. Data type is matched: text to text, number to number, date to date, pick-list to pick-list. If Upvio uses a pick-list, values are created as pick-list options in Zoho before migration runs.

Upvio integrations with Zoom, Google Meet, Microsoft Teams, PayPal, Stripe, and Zapier do not migrate. Each integration must be reconnected in Zoho CRM using Zoho Flow, native connectors, or Zapier. FlitStack provides a connection audit checklist listing every active Upvio integration so the team can rebuild each one in Zoho after go-live.