Migrate from Wired Plus to Odoo CRM

Wired Plus Contacts map to Odoo Contact records (res.partner with customer_rank applied). The contact's email, name, phone, and custom fields migrate directly. We query the opt_in and source fields explicitly during extraction to set Odoo's opt_out and email_cohort_ids fields. UK and EU data residency preferences from Wired Plus custom fields map to Odoo partner properties. The res.partner record serves as both the Contact and Company parent in Odoo's party model.

Wired Plus Company records map to Odoo Contact records where company_name is populated from the Company_Name field. Address fields (street, city, postcode, country) from the Wired Plus Company record merge into the corresponding Odoo Contact address fields. Domain-based deduplication uses the Wired Plus company domain as a lookup key. Multiple Wired Plus contacts belonging to the same Company are linked to the same Odoo Contact record via parent_id.

Wired Plus Deals map to Odoo CRM Opportunities (crm.lead with type='opportunity'). The dealstage property maps to Odoo stage_id with stage name matching. Closed-Won and Closed-Lost outcomes map to Odoo's won/lost stage states. Deal amount, expected closing date (close_date), and probability percentage migrate to amount revenue, date_deadline, and priority fields.

Wired Plus per-account pipeline stage sequences map to Odoo CRM stage sequences. We extract the full stage sequence with probability percentages and recreate them in Odoo via the crm.stage model. Stage sequence order and probability values are preserved. Stages with no Odoo equivalent are flagged during scoping and presented to the customer for consolidation decisions.

Wired Plus Campaigns contain email send history, open rates, and click data. Odoo CRM does not have a native campaign object equivalent to HubSpot or Mailchimp-style email campaigns. We export campaign metadata (name, send date, open rate, click rate, unsubscribe count) and attach it as structured notes to the relevant Contact records, or store it in a custom Odoo model created during schema setup. Customers planning to run email campaigns in Odoo should install Odoo Email Marketing or a third-party app post-migration.

Wired Plus account-specific custom fields require resolution to Odoo field definitions before import. We pull the Wired Plus field schema via API during scoping to map field labels to internal identifiers, then create equivalent Odoo fields via the interface or XML data file. Field types are matched: text fields to char or text, picklist fields to selection fields, date fields to date. Label changes since the last export require manual correction during scoping.

Wired Plus tags are flat string labels applied to contacts and companies. We export all tag assignments and reapply them as Odoo CRM tags linked via crm.tag.rel. Odoo tags are shared across Leads and Opportunities. If the customer uses tags for segmentation, we preserve the full tag set and map them to crm.tag records before contact import.

Wired Plus automation workflows define trigger-action sequences including conditional branches and time delays. We export workflow definitions as structured JSON metadata, but trigger event IDs, delay values, and condition logic require complete manual reconfiguration in Odoo Studio or via Python code. We provide a written workflow audit log covering every active workflow with trigger type, conditions, actions, and recommended Odoo Automated Action or Server Action equivalent. This is a rebuild task, not a migration.

Wired Plus landing pages are stored with HTML content and form configurations. We export page HTML, asset URLs, and form field definitions. Landing page HTML does not transfer to Odoo because Odoo has no native landing page builder. We flag pages with embedded forms requiring a new form handler. The customer should plan to rebuild landing pages in a dedicated landing page tool (Unbounce, HubSpot, WordPress) post-migration.

Wired Plus form submissions capture subscriber data and are linked to campaigns or landing pages. We export submission logs (field names, values, timestamp, source landing page). Since landing pages and form handlers do not migrate, we attach submission data as structured notes on the corresponding Contact record in Odoo. Field names and values are preserved; the form-to-field mapping logic requires manual rebuild in the new form tool.

Wired Plus Owners map to Odoo Users. We resolve owners by email match against the Odoo destination res.users table. Any Wired Plus Owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Wired Plus owners map to Odoo Users with active=False.

Wired Plus campaign email send events (open, click, bounce, unsubscribe) migrate as Odoo mail.message records attached to the relevant Contact. Engagement timestamp preserves the original activity date. Because Odoo CRM does not have a native campaign engagement timeline, these messages appear in the Contact's chatter. Customers requiring campaign attribution reports should implement Odoo Marketing Automation or a BI reporting layer post-migration.

Wired Plus notes attached to contacts migrate to Odoo mail.message records with note=True on the parent Contact. Note body migrates as plain text. Attachments migrate as ir.attachment records linked via mail.thread.documents.

Wired Plus file attachments stored within contact or deal records are accessible via direct download when the standard export interface supports it. We extract attachments and link them to the corresponding Odoo Contact or Opportunity via ir.attachment with res_model=res.partner or crm.lead and res_id set to the destination record ID. Attachments inaccessible via standard export require manual download before migration.