Migrate from Propeller CRM to Odoo CRM

Propeller Contacts map to Odoo CRM Lead records. The Propeller Contact's name, email, phone, and company association migrate as Lead fields (partner_name maps to the related res.partner record created from the Company mapping). Propeller's contact record ID is preserved in a custom field x_propeller_id for audit. If the archived export includes contact status flags, we map them to Lead stage or priority in Odoo. The email field serves as the dedupe key.

Propeller Company records map to Odoo res.partner records with is_company=True. Company name becomes the partner name, domain becomes website, and any industry or employee-count fields map to Odoo custom partner fields. We resolve duplicates by company name during import scoping. Partner records are created before Contact import so that the many2one relationship to res.partner is satisfied at Lead insert time.

Propeller Deals map to Odoo CRM Opportunity (crm.lead records with type='opportunity'). Deal name becomes opportunity name, deal amount maps to Odoo's expected_revenue and a custom float field, and the Propeller contact association links to the corresponding Odoo Lead/Contact. Deal stage names are mapped to Odoo stage IDs during import (see Stage mapping object). Lost/won status from Propeller carries to Odoo's probability=0 (lost) or probability=100 (won) states.

Propeller pipeline stages are fully custom per team. We map each Propeller stage name to an Odoo stage within the target pipeline, setting the probability percentage to match Propeller's stage order as closely as possible. Stages with no clear Odoo equivalent (e.g., 'verbal yes', 'awaiting finance') are flagged in the mapping document for customer confirmation before import. Stage ordering is preserved in Odoo by setting the sequence integer.

Propeller supported a single deal pipeline. This maps to one Odoo crm.team record. If the archived export references pipeline-level settings (e.g., stage count, pipeline name), these configure the target team's name and stage sequence. Teams needing multiple Odoo pipelines for different business lines configure additional crm.team records as a post-migration step.

Propeller Email Campaigns migrate to Odoo utm.campaign records as historical reference notes. Campaign name, associated contacts, and send date are preserved. The utm.campaign record links to the Odoo Contacts/Leads that were part of the campaign, but Odoo's mass mailing app (email marketing) is not migrated as a running system — only the historical campaign names and membership survive the migration.

Propeller email templates with merge fields migrate to Odoo mail.template records. We map template body content to the Odoo template body field and resolve merge field names to Odoo's QWeb or Jinja2-style field interpolation syntax (e.g., {{object.partner_id.name}}). Customers review rendered output in Odoo before activating templates.

Propeller Owner records map by email address to Odoo res.users. We extract every distinct owner email referenced on Contact, Deal, and Campaign records in the archive. If a matching Odoo user exists (active or inactive), we link the record to that user. If no match exists, we create a placeholder user record flagged for the customer admin to activate and assign. Orphaned assignments — where the Propeller owner email has no corresponding Odoo user — are listed in the reconciliation report.

Activity logs tracked by Propeller's Gmail extension — email opens, link clicks, reply events, and meeting scheduling — were not included in Propeller's standard shutdown data export. We flag this gap during scoping. We do not reconstruct per-contact activity timelines from external sources. The migration delivers no activity records. Customers who rely on historical engagement data for reporting or compliance must note this limitation before approving scope.

Propeller allowed custom field names on Contacts and Deals. We create matching custom fields in Odoo on the crm.lead (Lead/Opportunity) and res.partner models before migration. Field types are inferred from Propeller data (text fields, dates, numbers, picklists) and mapped to equivalent Odoo field types. Any picklist values in Propeller are created as selection options on the Odoo custom field. Customers confirm field type mapping during the scoping review.

Propeller tracked deal stage progression over time, but the archived export typically contains only the current stage per deal, not the full history log. We preserve the current stage name and last-modified date. The Odoo stage_id is set to the mapped current stage. If the archived export includes historical stage entries per deal, we create them as stage change log entries via a custom Odoo model or activity note.

Any file attachments exported from Propeller (e.g., contact photos, deal documents) are imported as Odoo ir.attachment records linked to the corresponding Lead, Contact, or Opportunity record via res_model and res_id. We resolve the parent record ID at migration time and preserve the original filename and file type. Attachments without a resolvable parent record are listed in the orphaned attachments report.