Migrate from Visionary to Odoo CRM

Visionary Contact maps directly to Odoo res.partner. In Odoo, res.partner serves as both individual contacts and company records — contacts are distinguished by having a parent_id pointing to the company partner. The Visionary contact's primary company link becomes the parent_id on the Odoo partner record.

Visionary Company and Contact merge into Odoo res.partner, with Company records created as partners of type 'company' and Contact records as partners of type 'person' linked via parent_id. Visionary's company domain, industry, and employee-count fields populate corresponding res.partner fields or custom fields on the company partner.

Visionary Deal maps to Odoo crm.lead with type='opportunity'. The Visionary pipeline becomes an Odoo sales team (crm.team), and each Visionary pipeline stage maps to a crm.stage record within that team. The crm.lead.stage_id field links the opportunity to the correct stage ordered record.

Visionary Lead maps to Odoo crm.lead with type='lead'. In Odoo, a single crm.lead model holds both Leads and Opportunities differentiated by the type char field — Leads retain the Visionary lead status as a custom field or are mapped to Odoo's stage model if the values align.

Visionary Pipeline translates to an Odoo crm.team record. Within each team, Visionary stage names become crm.stage records ordered by sequence integer. Each stage record belongs to a team_id, so pipeline isolation is preserved at the team level in Odoo. The mapping also carries over stage probabilities and fold (won/lost) flags, ensuring that deal progress reflects the original pipeline logic.

Visionary stage pick-list values map value-by-value to Odoo crm.stage records. The mapping plan includes sequence ordering, probability percentages, and fold (won/lost) flags per stage. We preserve the original stage-entered timestamp as a custom datetime field on the crm.lead for historical reporting continuity.

Visionary activity records (calls, emails, meetings, notes) migrate as Odoo crm.phonecall entries and mail.message records. Original timestamps, duration minutes, and description text are preserved. The call's related partner and opportunity links are set via the res_id and model fields on the mail.message record.

Visionary file attachments download from the source storage and re-upload into Odoo ir.attachment records. Each attachment is linked to its parent record (res.partner or crm.lead) via the res_model and res_id fields. Odoo's default 25MB per-file limit is enforced; files exceeding this are flagged for manual handling.

Visionary custom objects require Odoo custom model creation via the ORM. We create the ir.model record and corresponding ir.model.fields entries for each custom object, then map the data into the new model. Many-to-many associations in Visionary become Odoo ir.model.relational fields.

Visionary owner IDs resolve to Odoo res.users by email address match. Unmatched owners are flagged before migration so your Odoo admin can either invite them as Odoo users or reassign their records to an existing user. No crm.lead lands without a valid user_id in Odoo.

Visionary tags map to Odoo crm.tag records. Tags are many-to-many on crm.lead via the tag_ids relational field. We create missing tag records in Odoo during migration and link them to the corresponding leads and opportunities, preserving the original categorization. If multiple tags share the same name, they are deduplicated to a single Odoo tag to avoid duplication.