Migrate from Upvio to Odoo CRM

Upvio client records map directly to Odoo res.partner. Client name, email, phone, and address fields transfer as standard partner fields. Created_date from Upvio preserved as a custom Char field since Odoo's create_date reflects migration time. Active/inactive status maps to Odoo's active boolean.

Upvio appointments become Odoo calendar.event records. Start datetime, stop datetime, and duration transfer from Upvio booking slots. Partner_id links the event to the res.partner client record. Practitioner assignment maps to calendar event user_id — requires Odoo user creation for each practitioner before migration.

Upvio booking statuses (confirmed, cancelled, completed, no-show) transfer as a custom selection field on calendar.event since Odoo's base calendar module does not have a native status workflow. Completed appointments get a done boolean set to true. Cancelled events get active=false.

Upvio practitioner profiles map to Odoo res.users. Email and name transfer directly. Odoo user accounts must be created before calendar events can reference them via user_id. Active/inactive status on the practitioner maps to Odoo's user active flag. Access rights and groups set during Odoo configuration post-migration.

Upvio form data is stored per client as structured responses. Each unique form field becomes a custom Char, Text, or Selection field on res.partner depending on the response data type. Form name and submission timestamp preserved as metadata fields on the partner record. Multiple form types generate multiple custom fields.

Upvio FaceScan vital readings (heart rate, blood pressure trends, wellness scores) transfer as custom Float or Char fields on res.partner. Each vitals metric type gets its own field. Scan timestamp and FaceScan ID preserved in companion metadata fields for audit continuity. Odoo does not have native health-data fields — all vitals require custom field creation.

Upvio service types (consultation, follow-up, telehealth call) merge into Odoo product.product records for billing use and calendar.event description fields for scheduling context. The service name populates event description; product record enables Odoo Sales module integration if quotes or invoices are needed.

Upvio invoice and payment records do not map to Odoo CRM objects. Odoo accounting (account.move) belongs to the Odoo Accounting module, not CRM. Invoice history is preserved as a custom Text field on the partner record referencing original Upvio invoice IDs. Accounting module configuration is a post-migration step.

Upvio internal client notes and message history transfer as Odoo mail.message records linked to res.partner via res_id and model='res.partner'. Original message author mapped to Odoo res.users by email resolution. Creation datetime preserved from Upvio. Chatter thread visible on partner form in Odoo.

Upvio client categories (e.g., 'new patient', 'active treatment', 'follow-up') map to Odoo res.partner category_id (res.partner.category). Tag names transfer directly. One partner can have multiple tags in both systems — mapping preserves the many-to-many relationship via Odoo's category_id many2many field. Category assignments are applied during migration for immediate segmentation in Odoo's partner views.

Upvio video call links associated with appointments transfer to a custom Char field on calendar.event (e.g., upvio_meeting_url). Odoo's native meeting_url field can be used if the video provider is Odoo's built-in VoIP integration. External video links (Zoom, Google Meet) stored as custom URL fields per event.