Migrate from Wavity CRM to Odoo CRM

Wavity Contact records map directly to Odoo res.partner with partner_type='contact'. Standard fields (name, email, phone, mobile) migrate 1:1. Custom fields on Wavity Contact are identified during schema discovery and created as ir.model.fields in Odoo before import. The Wavity Contact-to-Company relationship (linked via the Company field on Contact) maps to partner_id on res.partner for child contacts. We set type='contact' and parent_id to the mapped Company partner record.

Wavity Company/Account records map to Odoo res.partner with partner_type='company'. The company flag is set to True. Website, street, city, country, industry, and revenue fields map to Odoo standard fields. Account is created before Contact import so that the parent_id foreign key is satisfied at Contact insert time. We use the domain or company name as the dedupe key during import to prevent duplicate Account records.

Wavity Lead records map to Odoo crm.lead with type='lead'. Lead status, source attribution, and scoring values from Wavity custom fields migrate to Odoo stage_id, source_id, and priority. The lead_name field maps to Odoo's contact_name. We flag any Wavity Lead that has a closed-won status to be migrated as a crm.lead that will be manually converted to an Opportunity by the customer's admin post-migration, since automated lead-to-opportunity conversion is an Odoo workflow decision.

Wavity Opportunity records map to Odoo crm.lead with type='opportunity'. Deal value migrates to planned_revenue; stage name maps to stage_id by lookup; probability migrates to probability as an override if the customer wants manual probability control rather than stage-based defaults. Owner/assigned user maps via email resolution to Odoo res.users. The linked Account (Company) resolves to the mapped res.partner id before Opportunity insert.

Wavity's customizable pipeline stages (name, order, probability) map to Odoo crm.stage records scoped to crm.team via team_id. Each Wavity pipeline becomes an Odoo crm.team with its own stage sequence. We extract the full stage schema during discovery and create stages in order before any Opportunity records are imported. Stage probability percentages transfer as Odoo probability values; the customer chooses at scoping whether to use stage-based or manual probability.

Wavity Tasks with due dates, assignees, and linked Contacts or Opportunities map to Odoo project.task (type='task'). Linked Opportunities resolve to crm.lead ids. Assignee maps by email to res.users. For tasks without a project association in Wavity, we create a default migration project in Odoo to host them. Completion status, priority, and description migrate as Task fields.

Wavity Calendar Appointments map to Odoo calendar.event. Start datetime, end datetime, duration, location, and attendees transfer directly. Attendees resolve by email to res.partner records. For appointments linked to a Wavity Contact or Opportunity, we create calendar.event records with res.partner attendees and link via the event's opportunity_id or partner_id fields. Timezone handling is preserved to avoid scheduling offset errors.

Wavity Help Desk Tickets migrate to Odoo helpdesk.ticket. Ticket subject, description, priority, status, and assignee map to Odoo standard fields. Wavity's ticket conversation thread (customer and agent messages) migrates as helpdesk.ticket.message_ids (mail.message records linked to the ticket). Attachments from the Wavity ticket attach to Odoo ir.attachment records linked via res_id/res_model to the ticket. Custom ticket fields identified during schema discovery are created in Odoo's helpdesk.ticket model before import.

Wavity custom objects built with the Zero Code Application Designer have no standard schema and no export format. We schedule a schema discovery session to document every custom object, field type, validation rule, and inter-object relationship before migration. Each custom object is then reimplemented as an Odoo ir.model inheriting from mail.thread, with all custom fields created as ir.model.fields before data import. Relationship fields between custom objects and standard objects (Contact, Account, Opportunity) are mapped as many2one or one2many Odoo fields. This is the highest-risk phase of any Wavity migration and requires customer validation before proceeding.

Wavity User records map to Odoo res.users by email match. We extract every distinct user referenced on Contacts, Opportunities, Tasks, and Tickets and reconcile them against the destination Odoo instance's user list. Inactive Wavity users are flagged to the customer's admin for decision (do not provision vs provision as inactive). Login and password are not migrated; Odoo sends a welcome email to each provisioned user at migration cutover. User roles and permissions are documented and handed off as a configuration guide for the customer's Odoo admin.

File attachments stored in Wavity are exported as binary files and re-uploaded to Odoo as ir.attachment records. The attachment-to-record linkage is preserved by storing the original Wavity record type and ID in ir.attachment.res_id and res_model fields so that each document remains associated with the correct Contact, Account, Opportunity, or Ticket. We normalize file names and deduplicate by content hash during ingestion.

Wavity's lead scoring values are stored as custom numeric or selection fields on the Lead object. These migrate as custom fields on crm.lead in Odoo. Odoo does not include a native lead scoring engine in the base CRM module, so the scoring values are preserved as data for the customer's admin to use in Odoo Studio reports or to integrate with a third-party scoring tool. We document the original scoring formula and field names for reference.

Wavity's pre-built sales dashboards and custom analytics built in the Zero Code Analytics Designer are not exportable in structured form. We do not migrate them. The underlying data (Contacts, Opportunities, Activities) is migrated so that equivalent reports can be rebuilt in Odoo using the Pivot, Graph, and Kanban views or Odoo Studio. We deliver a written inventory of every Wavity dashboard, its constituent charts, and the underlying data objects it references, so the customer's admin has a rebuild guide.