Migrate from Weave to Odoo CRM

Weave patients map directly to Odoo res.partner records. Odoo stores contacts as res.partner with type='contact' — no separate Contact object like Salesforce. We preserve the Weave patient ID in a custom field (x_weave_id) for delta-run de-duplication and traceability back to the source system.

Weave company (practice/facility) records map to Odoo res.company. On Odoo, res.company represents the business entity — for multi-location practices, each Weave company maps to a separate res.company record. Contacts are linked via the partner_id field on res.partner rather than a separate junction table.

Weave text messages and email threads migrate as mail.message records linked to the res.partner record. Odoo's mail module stores messages with author_id, body (HTML), date, and message_type fields. We preserve the original Weave timestamp and direction (inbound/outbound) as custom fields since Odoo's standard mail.message does not have a native direction field.

Weave VoIP call records (duration, direction, recording URL) do not map to a native Odoo object by default. Odoo CRM includes a crm.phone.call model in some editions — if not present, we create a custom crm.phone.call model to store call duration, direction, and a link to the recording file hosted on Odoo's ir.attachment storage.

Weave appointments map to Odoo calendar.event records linked to res.partner as attendees. Odoo's calendar module stores start/datetime, stop/datetime, name, and attendee_ids. We map Weave appointment status (scheduled, completed, cancelled) to the calendar.event state field, preserving all timing and participant data for calendar view compatibility.

Weave payment records (amount, date, method, patient) map to Odoo account.move entries with type='entry' for miscellaneous transactions or linked to an invoice if Weave generated bills. Odoo's accounting module requires an active journal — we use the default company journal or create one during setup if none exists.

Weave custom properties on patient records (e.g., referral source, insurance carrier, treatment history) migrate to custom fields on res.partner. Odoo requires a custom module or Studio to add fields — we document the target field name, type (char, selection, many2one), and help text so the Odoo admin creates them before migration.

Weave custom properties on company records (e.g., practice type, accepted insurance, NPI number) migrate to custom fields on res.company. Odoo res.company supports custom fields via Studio or module development — we provide the field specification including type, label, and any selection option values.

Weave users and assigned owners resolve by email match against Odoo res.users. If a Weave owner has no Odoo user account, records are assigned to the migration fallback user (typically the admin) and flagged in the pre-migration audit report for the Odoo admin to assign manually.

Weave file attachments on patient records (insurance cards, intake forms, imaging) re-upload to Odoo's ir.attachment table linked to the corresponding res.partner. Odoo's attachment storage (file size limits depend on Odoo version and hosting configuration) handles the binary data with res_model='res.partner' and res_id pointing to the partner record.

Weave appointment reminders, patient texting sequences, and review-request triggers are platform-native automations with no direct Odoo equivalent. These do not migrate. We export the workflow definitions as a PDF reference document so the Odoo admin can rebuild equivalent automations using Odoo's server actions and calendar reminders.

Weave billing records and payment plan configurations are healthcare-specific billing constructs. Odoo's account.move handles individual transactions but not Weave's payment-plan logic. We preserve billing metadata as custom fields on res.partner and recommend rebuilding payment plan logic in Odoo's sale.subscription or recurring invoice module.