Migrate from Wishpond to Odoo CRM

Wishpond Leads map to Odoo CRM Lead records. The primary fields (name, email, phone, company) migrate directly. We flag records missing phone numbers during extraction and flag them as enrichment candidates in Odoo using a custom field wishpond_phone_missing__c boolean. Source attribution (landing page URL, form name, campaign name) migrates as Odoo Tag records linked to the Lead so that the customer's sales team can report pipeline by acquisition channel. HubSpot-style lifecycle stage data is not natively supported in Odoo CRM and is stored as a custom field wishpond_lifecycle_stage__c if present in Wishpond.

Wishpond does not have a standalone Company/Account object; company name is stored as a property on the Lead record. We extract distinct company names from Wishpond Leads, deduplicate them, and create Odoo CRM Partner records (res.partner with customer_rank > 0) before importing Leads. This resolves the Partner-Lead relationship so that Odoo Lead conversion creates a Contact attached to the correct Partner.

Wishpond Forms with custom field names and types (text, email, phone, dropdown) map to Odoo CRM custom fields created via Odoo Studio before migration. Dropdown options in Wishpond Forms map to Odoo Selection fields with matching selection values. We document every custom form field with its API name, data type, and options so that the customer's Odoo admin can verify field labels in the destination system.

Wishpond Landing Pages have metadata (page name, URL slug, creation date, traffic source) that does not have a native Odoo CRM equivalent. We extract landing page metadata and associate it with the Leads captured from each page using Odoo Tags (one tag per landing page name). The visual layout of landing pages cannot be migrated; we deliver a written inventory of every Wishpond Landing Page with its URL, associated form, and captured lead count so that the customer can decide which pages to rebuild using Odoo Website or a third-party tool.

Wishpond Email Campaigns with drip sequences and A/B variants export as campaign records with metadata (campaign name, start date, status, open rate, click rate). We map each Wishpond campaign to an Odoo Tag on the Leads that were part of that campaign, preserving the acquisition channel attribution. Campaign-level metrics (open rates, click rates) are stored as a CSV attachment and as custom fields on a Master Campaign record in Odoo for reference. Odoo Email Marketing app replaces the active campaign execution capability.

Wishpond Workflows (trigger-action sequences such as 'if form submitted, add to drip sequence') export as a JSON schema document. We do not migrate them as code because Wishpond Workflows and Odoo Studio automated actions use different data models, triggers, and conditions. We deliver a written inventory of every Wishpond Workflow with its trigger, conditions, actions, and a recommended Odoo Studio equivalent, plus the sequence order for the customer's Odoo administrator to rebuild.

Wishpond Popups (exit-intent and embedded) with targeting rules and associated forms export as campaign assets. We capture popup configuration including trigger conditions and display rules in a written inventory document. Popup rendering is not migrated; Odoo does not include a native popup builder in its standard CRM module. The customer rebuilds popup functionality using Odoo Website or a third-party integration if needed.

Wishpond Referral Campaigns with reward mechanics and participant lists export as campaign records. Referral tracking codes and participant contact records migrate as Odoo Leads tagged with the referral campaign name. The reward mechanics (discount tiers, referral codes) are documented in the handoff inventory for the customer to configure in Odoo if they use Odoo Loyalty or a third-party referral tool.

Wishpond Contest entries export as Lead records tagged with contest metadata (contest name, entry date, entry status). We merge contest participants into the unified Lead export and preserve the contest attribution as Odoo Tags so that the sales team can see which Leads came from which contest promotion.

Wishpond A/B Test configurations export with variant metadata, traffic allocation percentages, and winner criteria. We capture these as a structured notes document associated with the relevant Wishpond Landing Page or Email Campaign records. Odoo CRM does not have native A/B testing; this functionality requires Odoo A/B Testing apps or third-party tools.

Wishpond User accounts (name, email, role) export as records. We map Wishpond role names to Odoo User access rights (Inventory User, Sales User, Administrator) based on the customer's Odoo edition and installed apps. Active vs. inactive status is preserved. Users without a matching Odoo User go to a reconciliation queue for the customer's admin to provision before the Lead import proceeds.

Historical open rates, click rates, conversion rates, and lead attribution time-series data export as monthly CSV segments. We chunk large analytics exports to respect Wishpond's 60-second API rate-limit blocking window. The CSV files are attached to a Master Campaign record in Odoo CRM for reference by the customer's reporting team. These metrics are not used to populate Odoo's native reporting because Odoo uses its own reporting model.