Migrate from Divalto weavy to Odoo CRM

Divalto weavy Companies map to Odoo res.partner records with company_type set to 'company'. The company name, industry, billing address, and shipping address fields map to Odoo's name, industry_id, and address fields (street, city, zip, country). Odoo's partner model supports multiple addresses per company via the child_ids relationship, which we use to represent Divalto weavy's separate billing and shipping addresses as distinct res.partner records of type 'contact' linked to the parent company.

Divalto weavy Contacts map to Odoo res.partner records with company_type set to 'person' and a parent_id linking to the corresponding company partner. Standard fields (name, email, phone, mobile, job title) map directly. Any custom fields created in the Development Studio are audited during discovery, created as custom res.partner.fields, and mapped explicitly during import. Contact records without a Divalto weavy company association are created as standalone individual partners.

Divalto weavy Leads migrate to Odoo crm.lead records in the Lead stage. Odoo's crm.lead model serves both unqualified prospects and qualified opportunities; the customer chooses at migration time whether to convert immediately to Opportunity or keep in Lead. Lead status and source fields from Divalto weavy map to Odoo's stage_id and source_id (utm.source). The original Divalto weavy lead status is preserved in a custom field for reporting continuity.

Divalto weavy Deals map to Odoo crm.lead records with type set to 'opportunity'. Deal name becomes crm.lead name, deal value maps to planned_revenue, expected close date maps to date_deadline, and stage maps to stage_id (see Pipeline Stage configuration below). Owner resolution is by email match to Odoo res.users.

Divalto weavy pipeline stages are extracted during discovery and mapped one-to-one to Odoo crm.stage records within the appropriate crm.team. Stage probability percentages from Divalto weavy migrate to stage_sequence values in Odoo. Custom stage names (beyond the standard Divalto weavy lifecycle) are created as new crm.stage records in the destination. The Odoo stage IDs are captured and used as the stage_id foreign key in the Deal-to-Opportunity mapping.

Divalto weavy Activity records map to Odoo's mail.activity for tasks and calendar.event for meetings and calls. Activity type, date, description, and linked owner migrate directly. Calls optionally map to crm.phone.call if the Odoo CRM Telephony module is installed; otherwise they land as mail.activity with a call-type subtype. The parent record reference (contact, company, or deal) is resolved via the partner_id or opportunity_id foreign key at migration time.

Divalto weavy user records (Standard, Sales, Technician, Full profiles) are mapped to Odoo res.users by email match. Profile assignment from Divalto weavy is stored in a custom field user_profile__c on the Odoo res.users record. Any Divalto weavy user without a matching Odoo user email is placed in a reconciliation queue; the customer's Odoo admin provisions the missing user before record import continues because OwnerId references are required on Opportunity and Activity records.

Every custom object defined in Divalto weavy's Development Studio is audited during discovery. We create the equivalent custom model in Odoo using res.config.settings-based schema creation or a custom Python module, then map all custom fields (with correct field types: char, text, float, integer, date, many2one, many2many) before importing any data that references those objects. Custom objects that represent lookup relationships (e.g., ProductCategory) are mapped to existing Odoo res.partner categories or custom many2one fields to preserve referential integrity.

Development Studio custom fields on Companies, Contacts, Leads, and Deals are created as custom ir.model.fields in Odoo before any record import. We capture the field type, required flag, picklist values, and any validation logic during the schema audit, and reproduce equivalent Odoo field definitions. If a Development Studio field has a picklist of values, we create a corresponding selection field or many2one in Odoo with the same options.

Document attachments linked to Companies, Contacts, and Deals in Divalto weavy are extracted as files and imported into Odoo ir.attachment. Each ir.attachment record receives res_model set to the target model (res.partner or crm.lead) and res_id set to the migrated record's Odoo ID. File names and original timestamps are preserved in the attachment's name and create_date fields.

Free-form notes from Divalto weavy migrate to Odoo mail.message records with a note subtype on the parent record, or to note.note records if the Odoo Notes app is active. Note body migrates as HTML with attachments preserved separately.

Divalto weavy route planning and itinerary data are mobile-first features specific to its field workforce management capabilities. Odoo CRM does not have a native route or itinerary object. If the customer activates the Odoo Field Service Management app (Enterprise tier), route and planning data can be reconstructed manually after migration. We do not include route data in the standard migration package and flag the gap during scoping.