Migrate from Leadfwd to Odoo CRM

Leadfwd Contacts sync from Salesforce as Contact records. They map to Odoo crm.lead in Lead status. We extract Contact fields (name, email, phone, title, company) and stage them for Odoo's CSV import using contact_name for the lead name and email from the Salesforce email field. Any Salesforce Contact ID is preserved in a custom Odoo field for audit. Contacts that should qualify directly to opportunity are flagged for the Create Opportunity step in the migration run rather than bulk-imported as leads.

Leadfwd Lead records (distinct from Contacts) sync from Salesforce Lead objects and map directly to Odoo crm.lead. We preserve Lead_Status from Salesforce as a custom field on the Odoo lead so the customer's admin can filter by original lead source during the Odoo adoption window. Country, state, and industry fields from Salesforce map to Odoo's standard country_id and industry_id references.

Leadfwd Company records (synced from Salesforce Account) map to Odoo res.partner in company mode. The Company ID is preserved as a custom field for cross-reference. Address fields (street, city, state, zip, country) map to Odoo's partner address fields. Any custom Company properties (industry classification, employee count) map to Odoo custom res.partner fields created before import. Parent-company hierarchies from Salesforce Account structures migrate as Odoo Contact sub-relations on the parent partner.

Leadfwd Deals synced from Salesforce map to Odoo crm.lead records in the Won or Lost stage bucket. We map the Leadfwd Deal stage name to the nearest Odoo CRM stage using the customer's provided stage equivalence table during scoping. Expected close date migrates to Odoo's expected_revenue date field. Deal amount maps to Odoo's planned_revenue. The customer's pipeline layout is configured in Odoo CRM before migration so stages are aligned and leads land in the correct pipeline column.

Leadfwd Sequences (multi-step outreach cadences across email, LinkedIn, SMS) define the outreach journey but are not transferable as automation. We export the sequence name, step count, step order, and channel per step into a custom field sequence_outreach_plan__c on the Odoo crm.lead record as a plain-text reference for the admin. Active enrollments are flagged as custom status tags on the crm.lead so the admin can replay the sequence manually or set up Odoo Automated Actions to reproduce the cadence.

Enrollment records (which Contact is in which Sequence at what step) are exported with enrollment status, current step index, and last activity timestamp. These do not activate in Odoo because Odoo has no equivalent sequence execution engine. We set custom tags on the crm.lead record (e.g., sequence_active, step_3, last_activity_2025-03-15) so the admin can see the outreach state at migration and manually re-enroll or configure an Odoo Automated Action to resume. Every enrollment is flagged as requiring manual re-enrollment in the migration deliverable document.

Leadfwd Icebreakers are AI-generated personalized conversation openers per Contact using LinkedIn profile data. We export the generated text and the source LinkedIn URL into a custom field icebreaker_text__c on the Odoo crm.lead record. The AI-generated variants are Leadfwd-specific and cannot be regenerated automatically in Odoo; the field is informational so the sales rep can reference the original opener during outreach.

Leadfwd email engagement events (opens, clicks, replies, bounces) logged in Salesforce Activity records map to Odoo mail.message records attached to the crm.lead via Odoo's mail.thread mechanism. We preserve the engagement type, timestamp, and channel metadata as message metadata. Full email body content migrates as the mail.message body. The Partner (recipient) is resolved via email match against the imported res.partner record.

Leadfwd call engagements map to Odoo Note records attached to the related crm.lead. Call duration, disposition, and recording URL are stored in the Note body as structured text. Odoo does not have a native call engagement object; Notes provide the closest visible timeline artifact. The Note creation date is set to the original engagement timestamp to preserve the activity sequence.

Leadfwd meeting engagements (calendar events synced from Salesforce) migrate as Note records on the crm.lead with meeting details in the body (date, title, location, attendees). Odoo's calendar module can be used post-migration to recreate meetings, but the historical meeting record migrates as a Note for audit continuity.

Leadfwd Tasks linked to Sequence steps migrate as Note records on the crm.lead. Task status, due date, and assignee are embedded in the Note body. Automated task creation logic does not transfer because Odoo Automated Actions follow a different trigger model. The task assignment (assignee) is stored as a text reference to the original HubSpot Owner name for the admin to reassign in Odoo.

Leadfwd engagement events (opens, clicks, replies, bounces, LinkedIn profile views) map to Odoo mail.message records with the channel type stored as a custom field on the message. Each engagement event gets a tag (e.g., email_open, linkedin_click) on the crm.lead for filtering. Deep event details (exact email body content of a click, device used) are not available for import from Salesforce Activity records and are scoped out.

Leadfwd custom fields sync through the Salesforce API pipeline. We map them field-by-field to Odoo custom res.partner fields created before import. Fields referencing Leadfwd-specific picklist values (e.g., enrollment_status values) require manual value mapping to Odoo equivalent selections. Fields hidden by Salesforce field-level security (per Leadfwd's platform gotcha) may not appear in the export; we audit the Salesforce field accessibility list during scoping and flag any excluded properties.