Migrate from Odoo CRM to Freshsales

Odoo stores both individual contacts and company records in the same res.partner table, with the commercial partner linked via parent_id. We split this into Freshsales Contacts (individual) and Accounts (organization). Where parent_id is set in Odoo, we create the parent as a Freshsales Account and link the child records as Contacts under it. The commercial partner_id field becomes the Account link for individual contact records. Email serves as the dedupe key during import. Odoo's partner fields (phone, street, city, country) map to Freshsales Contact and Account address fields with a rule applied: if the Odoo record has child partners, it lands as an Account; standalone partners with no children land as Contacts.

Odoo Leads are crm.lead records where type='lead'. These map directly to Freshsales Contacts without an associated Account or Deal. The lead's contact_name, email_from, phone, source_id (lead source), and any custom fields migrate. We set the Lead Status in Freshsales to New and preserve Odoo's stage_id as a custom field crm_original_stage__c so the customer's admin can re-stage leads after migration if needed.

Odoo Opportunities are crm.lead records where type='opportunity', linked to res.partner via partner_id and to crm.stage via stage_id. We create a Freshsales Account from the Odoo partner_id, link a Contact to that Account, then create a Freshsales Deal tied to the Contact and Account. The Odoo expected_revenue maps to Freshsales Deal amount, probability migrates as a custom field deal_probability__c (Freshsales does not use Odoo's float probability natively), and date_closed maps to the Deal's close date. Odoo's lost reasons stored in the crm.lead write_date and stage_id transitions become Freshsales Deal stage notes.

Odoo pipeline stages are stored in crm.stage and ordered per team via crm.team.stage.rel. We extract the full stage list per team and configure Freshsales pipeline stages in the same sequence. Each Odoo stage name becomes a Freshsales stage name, and the probability values stored in crm.stage.on_change_state migrate to the corresponding Freshsales stage probability. Custom stages added by the customer via Studio or custom addons are included in the export. We sequence stage creation before Deal migration so that Deals can reference valid stage IDs at import time.

Odoo Sales Teams map to Freshsales Teams. We extract team members from crm.team.member_ids and map each Odoo team member (res.users) to a Freshsales User by email match. Odoo's team-level stage configurations map to Freshsales pipeline assignments per team. If Odoo's team structure is flat (no separate teams), we create a single Freshsales team and assign all Deals to the default pipeline.

Odoo Activities linked to crm.lead records migrate to Freshsales Tasks. Activity type (call, email, meeting, todo, reminder) maps to Freshsales Task type. date_deadline migrates to the Task due date, user_id resolves to the Freshsales User by email, and the activity note (mail.message body) becomes the Task description. Activity history is high-volume and loosely coupled via activity_ids on crm.lead; we resolve the parent Odoo crm.lead record to its Freshsales Contact or Deal counterpart before inserting each Task so no orphaned activity records appear in Freshsales.

Odoo Tags are stored in crm.tag and applied to crm.lead via a many2many field. We export the full tag list as flat name values and create matching tags in Freshsales before record import. During Contact and Deal import, we resolve each tag name and attach it via Freshsales' tag API. Custom tags added by the customer are included in the export. Note that Freshsales uses a separate tagging system for Contacts and Deals; Odoo's shared tag pool is preserved but customers may choose to maintain separate tag lists per object post-migration.

Odoo custom fields defined via Studio or custom addons are stored as columns in crm.lead. We export field definitions alongside data, then pre-create matching custom fields in Freshsales before import. Selection fields map to Freshsales dropdown; many2one fields to Freshsales lookup relationships (where the related Odoo model has a corresponding destination object); many2many to Freshsales multi-select. Float and integer fields map directly. HTML-formatted custom fields are stripped to plain text because Freshsales custom fields do not support rich-text storage. If the Odoo custom field references an Enterprise-only addon, we flag it as unmigratable and document the data loss for the customer's admin.