Migrate from Upvio to Microsoft Dynamics 365 Sales

Upvio clients map directly to Dynamics 365 Contacts. Each client record carries a name, email, phone, and address. We preserve the original client ID as Source_System_ID__c for delta‑run deduplication and audit traceability. The Source_System_ID__c field also facilitates incremental syncs after the initial migration, allowing you to capture new or updated clients without re‑processing the entire dataset.

When Upvio clients represent organizations (clinics, practice groups) rather than individuals, the client name and domain map to a Dynamics 365 Account, with the individual contact linked via the Primary Contact lookup. Your team defines which clients are person-level vs. organization-level before migration.

Upvio practitioners are the user actors who own appointments and FaceScan records. They map to Dynamics 365 Users when the practitioner will log in to Dynamics; otherwise they migrate as Contact records. We match by email to resolve existing Dynamics users first.

Upvio appointments map to Dynamics 365 Appointment activities. The scheduled start/end time, practitioner owner, and linked client contact are preserved. Upvio's video-session links (Zoom, Teams) do not transfer — they must be regenerated in Dynamics 365 or shared via Teams integration post-migration.

Upvio FaceScan vital-sign data (heart rate, HRV, blood-pressure trends) has no native equivalent in Dynamics 365 Sales. We create a custom Dataverse table (FaceScanResult) with columns for vital_type, value, unit, measured_at timestamp, and a lookup to the source Contact. Sales Enterprise or Dynamics CE is required for unlimited custom tables.

Upvio intake forms generate custom field sets per form. These map to a custom Dataverse table (IntakeFormResponse) with columns for form_name, field_label, field_value, and submitted_at. Each response links to the submitting Contact. Standard Dynamics fields cannot hold unstructured form field sets.

Upvio client grouping and tagging (e.g., 'New Patient', 'Follow‑up', 'Chronic Care') migrates as a custom multi‑select pick‑list field or as tags on the Contact record. We map each Upvio tag value to a corresponding pick‑list value in Dynamics 365. If the number of distinct tags exceeds the pick‑list limit, we switch to a text field to avoid truncation and preserve the full tag set.

Upvio billing records (if exported via API) map to Dynamics 365 Invoice records. Amount, status, payer contact, and line items transfer. Dynamics 365 Invoice requires the Account to exist first — we sequence Account migration before Invoice migration. We also validate that each invoice's currency matches the target organization's default currency to prevent pricing mismatches during import.

Payment records from Upvio's Stripe or PayPal integrations have no native Dynamics 365 equivalent. We preserve them as a custom PaymentRecord table linked to the Contact or Invoice. Financial reconciliation is handled outside Dynamics 365. Each PaymentRecord entry captures transaction ID, amount, currency, payment method, and timestamp, enabling downstream reporting via Power BI if required.

Upvio's calendar sync with Google Calendar and Office 365 Calendar does not migrate. After cutover, the Dynamics 365 Outlook integration and server‑side synchronization must be reconfigured for the same calendar connections. We recommend scheduling a brief walkthrough with your Microsoft partner to test OAuth permissions and verify that calendar events appear correctly in the Dynamics 365 timeline after reconfiguration.