Migrate from Force24 to Odoo CRM

Force24 Contacts map directly to Odoo Contact records (internally called Partner in Odoo). Standard fields (name, email, phone, address) migrate cleanly. We map Force24's lifecycle stage property to an Odoo custom tag or a custom Char field (lifecycle_stage__c) so that the original funnel position is preserved for reporting. Contact type (company vs individual) maps from Force24's company association to Odoo's is_company flag.

Force24 Company records map to Odoo Partner records with is_company = true. The Force24 company name becomes the Partner name; the website URL and industry properties map to custom fields on the Partner. We link the individual Contact records to the Company Partner via the parent_id field in Odoo to reproduce Force24's contact-company hierarchy. If Force24 has no explicit Company object, we derive the company from each Contact's domain and create the Odoo Company record before importing Contacts.

Force24 Lead records (Contacts with a lifecycle stage indicating unqualified prospect status) map to Odoo CRM Lead (crm.lead). The Force24 lifecycle stage value maps to the Lead's stage_id in Odoo, and any lead score property migrates to a custom Float field on the Odoo Lead. Source tracking from Force24 maps to Odoo's source_id. We preserve the original Force24 contact ID as an external ID on the Odoo Lead for reconciliation.

Force24 does not natively store Deals or Opportunities — pipeline data lives in the integrated CRM, not in Force24 itself. If the customer has Deal records from a CRM that feeds Force24, we import them as Odoo CRM Opportunity records with name, expected_revenue, partner_id (linked to the Company Partner), and stage_id. If no Deals exist in Force24, we note that the Opportunity object will be empty post-migration and flag that historical pipeline should be sourced from the original CRM before Force24 is decommissioned.

Force24 engagement events (email opens, clicks, SMS delivery, form submissions) are stored per Contact but lack a native Odoo equivalent activity object. We merge them into Odoo CRM activities linked to the Contact (Partner) record. Each engagement type gets a specific activity type in Odoo: Email Open and Click map to Email activity; SMS maps to SMS activity; form submissions map to Submission activity. Engagement timestamps become the activity's date field. If engagement volume is very high (over 100,000 records), we aggregate by contact into a summary Note rather than individual activities to avoid overwhelming the Odoo activity log.

Force24 contact tags migrate to Odoo Tags on the Contact (Partner) record using Odoo's native tagging feature (available from Odoo 14 onwards). We export the full tag set from Force24, deduplicate, and write each tag to Odoo's tag list before associating them with the migrated Contacts. Tags used for marketing segmentation are preserved so that the customer's admin can rebuild Smart Lists using Odoo's filters or the Contact Group feature.

Force24 Smart Lists define audience segments using contact property filters and behavioural rules. We export the segment criteria and the contact IDs included in each list. In Odoo, we recreate the segment membership as static Contact Groups (crm.contact.group or a custom model depending on Odoo version). The filter logic itself requires manual recreation in Odoo using the Filters and Group By feature; we document each Smart List's filter criteria in a written handoff document for the customer's admin to rebuild as Odoo saved filters.

Force24 Automated Journeys define multi-step, multi-channel workflows with conditional branching and behavioural triggers. This logic is not portable. We document every active Journey's structure — entry trigger, step sequence, branch conditions, wait steps, and exit conditions — in a written specification that the customer's admin uses to rebuild the automation in Odoo Automations (server actions) or the Marketing Automation app. We do not migrate Journey logic as code.

Force24 Custom Objects are linked-data tables attached to Contacts. We export each Custom Object definition and all associated records, then create a corresponding custom model in Odoo using Studio or developer mode. We add the necessary fields matching the Force24 schema, create a Many2one relation to the Contact (Partner) record, and import the historical data. Force24 Custom Objects require account manager activation; if this was not enabled, the data is not available via API and we flag this before export.

Force24 distinguishes between Marketing users and Sales users. We map Force24 users to Odoo User records by email match. Inactive or archived Force24 users map to Odoo Users with active=False. The marketing-vs-sales distinction maps to Odoo CRM team membership (crm.team) and access rights groups. Owners assigned to Contacts and Leads in Force24 become the responsible_user_id on the corresponding Odoo records.

Force24 lead scoring assigns numeric values to Contacts based on engagement and property data. We export the score value stored on each Contact record and write it to a custom Float field (force24_lead_score__c) on both the Odoo Contact and Lead. The scoring rules themselves (the logic that determines how scores are calculated) are Force24 configuration and do not migrate; we document the rule structure for the customer to rebuild in Odoo using automated actions or a scoring app.

Force24 email templates and dynamic content blocks are marketing assets that reference Force24-specific merge fields. We export templates as HTML for review. Because merge field syntax differs between Force24 and Odoo, we do not recommend direct template import; instead, we document the template structure (subject, body sections, dynamic blocks, and merge field mappings) so the customer's admin can recreate the templates in Odoo's Email Marketing or using the custom email templates feature. The Marketing Automation app in Odoo provides a template editor that can replicate most Force24 dynamic content patterns.