Migrate from Friday CRM to Odoo CRM

Friday CRM Company records map to Odoo res.partner with is_company set to True. We map company_name to name, address fields to street, street2, city, state_id, zip, country_id, and preserve any custom field values as Odoo custom fields on the partner record. Company-contact relationships are preserved by resolving the Friday company_id on each Contact and setting the parent_id on the Odoo res.partner record. Friday URL fields migrate to website on the partner record.

Friday CRM Contact records map to Odoo res.partner with is_company set to False. We map first_name and last_name to firstname and lastname respectively (or combined to name if firstname is not installed), email to email, phone to phone, and address fields to the standard Odoo address block. The parent_id field on the Odoo partner is set to the migrated Friday Company res.partner record to preserve the company-contact relationship. Custom contact fields migrate as Odoo custom fields.

Friday CRM Deals map to Odoo crm.lead records with type = opportunity. The deal name maps to name, deal value maps to expected_revenue, stage maps to stage_id after pipeline stage configuration, and expected close date maps to date_deadline. Partner_id is resolved to the Odoo res.partner record representing the linked Contact or Company. Closed-Lost and Closed-Won status migrate as stage_id transitions to the corresponding Odoo CRM stage.

Friday CRM pipeline stages map to Odoo CRM stages. We extract stage names and display order from the Friday CSV export and configure matching stages in Odoo CRM settings before deal import. Probability percentages from Friday custom fields migrate as Odoo stage probability values. If Friday uses stage-specific probability overrides, these map to custom probability fields on the crm.lead record. Odoo's stage-onchange and sequence ordering replicate the Friday Kanban ordering behavior.

Friday CRM custom fields of type text, number, single-line text, URL, and date map to Odoo ir.model.fields with types char, float, integer, char, and date respectively. We pre-create each custom field definition in Odoo through Settings > Technical > Custom Fields or via data file before migration. Field labels from Friday become Odoo field descriptions. Fields are defined on the correct model (res.partner for Company/Contact fields, crm.lead for Deal fields) before any data loads.

Friday CRM radio select and dropdown fields map to Odoo selection fields. We extract all distinct option values from the Friday export, construct the Odoo selection tuple, and define the field as selection with the value list before migration. If the Friday field uses a default value, we set the default on the Odoo field definition. Selection field migration preserves the exact enumerated values from Friday without re-keying.

Friday CRM single checkbox fields map to Odoo boolean fields. We create the boolean field definition on the correct Odoo model (res.partner or crm.lead) before migration. The migrated boolean value is True or False based on the Friday checkbox state. Odoo's boolean fields display as checkboxes in the form view, matching the Friday CRM interaction model.

Friday CRM multiple checkbox fields have no direct Odoo equivalent because Odoo does not support multi-checkbox widgets. We split each multiple-checkbox field into separate boolean fields in Odoo, one per option value from Friday. The field labels concatenate the Friday field name with the option label for clarity. An alternative approach using a char field with comma-separated values is available if boolean explosion is not desired.

Friday CRM tags on Contacts and Deals map to Odoo CRM Tags. We extract all distinct tag values from the Friday export, create corresponding crm.tag records, and attach them to crm.lead records via the tag_ids many2many relationship. If Friday uses the same tag on both Contacts and Deals, we apply the tag to both crm.lead records and res.partner records in Odoo. Tag deduplication (case normalization, whitespace trimming) happens during the extract phase.

Friday CRM notes attached to Contacts and Deals migrate to Odoo CRM chatter as mail.message records with message_type = notification. We preserve the note body as the message body, the creation timestamp as write_date, and link the message to the crm.lead or res.partner record via the res_id and model fields. The author is set to the migrating user or a system user if the Friday note has no attributed owner. Chatter visibility in Odoo is native and requires no additional configuration.

Friday CRM owners referenced on Deals and Contacts map to Odoo res.users by email address match. We extract every distinct owner email from the Friday export and match against Odoo destination User records. Owners without a matching Odoo User are held in a reconciliation queue; the customer's Odoo admin provisions missing users before record migration proceeds. OwnerId on crm.lead migrates as user_id on the opportunity record in Odoo, controlling pipeline assignment and activity ownership.

Friday CRM does not expose file attachments via its documented CSV export or public API. We flag this limitation in the discovery phase and recommend that users export attachments manually through the Friday CRM interface before migration. We do not migrate attachment data as part of the standard migration scope. For customers with critical attachments, we provide a written inventory of attachment locations in Friday CRM so that the admin can re-upload them manually to Odoo after migration.