Migrate from Upvio to Nutshell

Vitals AI health data has no native CRM home in Nutshell

Upvio's Vitals AI stores structured health scan results — heart rate, HRV, blood pressure, wellness trends — as discrete data points per client. Nutshell has no native health or vitals fields. We create custom number and datetime fields (Vitals_HeartRate__c, Vitals_BPSystolic__c, etc.) on the Nutshell Person record. This approach preserves the most recent scan values for reference, but Nutshell does not natively process or display these values in charts, dashboards, or workflow triggers the way Upvio's Vitals AI does. Your team must treat these as informational custom fields, not as a health monitoring system.

Appointment session history requires custom field setup before import

Upvio appointment sessions (date, practitioner, duration, session type, status, notes) do not map to any standard Nutshell object without custom field creation. Nutshell Activities support basic task and event tracking, but session type, duration in minutes, and appointment status require custom fields on the Activity object. We generate the custom field creation plan based on your Upvio appointment schema before the migration runs. If your Upvio account uses multiple appointment types with different custom properties, each type may require a distinct set of Nutshell custom fields.

Practitioner-to-Nutshell-user email resolution is required before migration

Upvio practitioners and staff are stored as user accounts linked to appointments. Nutshell Activities require an assignedTo field pointing to a Nutshell user. We resolve practitioners by email match against Nutshell users. If a practitioner has no corresponding Nutshell account, their appointments cannot be assigned during migration — these are flagged before the full run so your admin can create the user accounts or assign a fallback owner. This pre-flight check ensures that every Activity record written to Nutshell has a valid assignedTo reference and avoids orphaned activity entries that cannot be traced back to an owner.

Upvio intake form logic and conditional branching does not migrate

Upvio intake forms may include conditional logic — skip patterns, required-field rules, multi-step progressions — built into the form builder. Nutshell has no equivalent form logic engine at the CRM level. We export form field structures as a reference document, but the branching logic, conditional requirements, and step progression must be rebuilt using Nutshell Forms or a third-party form builder integrated with Nutshell. The exported reference captures field names, data types, pick-list values, and any validation rules so your admin has a complete blueprint for recreating the form experience in Nutshell's ecosystem.

Booking page configurations are not transferable to Nutshell

Upvio's booking page setup (available slots, service types, buffer times, client-facing settings) has no equivalent in Nutshell's data model. Nutshell's scheduling capabilities are configured separately from the migration. We export a summary of your current booking page structure — service types, durations, practitioner assignments, slot availability rules, buffer times, and client-facing display settings — as a structured reference document to guide your Nutshell admin through the scheduling configuration rebuild. This ensures that when you set up Nutshell's booking functionality, all the service parameters that drove your Upvio scheduling are documented for recreation.