Migrate from folk to Odoo CRM

folk Contacts of person subtype map to Odoo CRM Contact records. Standard properties (name, email, phone, address) migrate directly. Custom fields migrate to Odoo custom fields on the res.partner model; we enumerate the per-group field schema during discovery and create equivalent custom fields in Odoo before import. The migration user must have write access to the CRM app and Contacts in Odoo. Odoo's partner model treats Contact as a res.partner record with is_company=False.

folk Contacts of company subtype map to Odoo CRM Contacts with is_company=True. This is a separate record from person-type contacts at the same organization. We preserve any manually established relationship between folk company-type contacts and their linked person-type contacts by setting the parent_id field on the person Contact to point to the company Contact in Odoo. This reconstructs folk's manual relationship field using Odoo's parent-partner structure.

folk Groups function as both organizational containers and segment lists. We offer two migration strategies: (1) Tags — each Group becomes an Odoo CRM Tag and every Contact in that Group receives the Tag via crm.tag.rel. (2) Pipeline Stages — if the Groups map to deal stages, we create Odoo CRM pipeline stages from Groups rather than Tags. The customer chooses during scoping. Multi-Group contacts receive multiple Tags in Odoo.

folk pipeline views are per-Group. We map each folk Group with a pipeline view to an Odoo CRM stage within the default Odoo sales team pipeline. Stage names, sequence order, and probability percentages transfer to Odoo stage configuration. Odoo allows multiple pipelines via sales teams if the customer needs pipeline isolation.

folk Notes attached to Contacts migrate to Odoo CRM internal notes as mail.message records on the res.partner thread. We preserve note body text, creation timestamp, and author attribution where author can be resolved to an Odoo User by email match. Notes that cannot be attributed are created under the admin User with a note indicating source.

folk Reminders carry a due date, assignee, and text. Due dates and text migrate to Odoo CRM as planned activities (calendar.event records with activity_type_id assigned). Assignee mapping requires resolving folk owner email to an Odoo User. Reminders without a resolvable assignee are attached to the Contact record as an unassigned CRM activity for the customer's admin to reallocate.

folk contact tags migrate as Odoo CRM Tags using the crm.tag model. Tags are stored as string arrays in folk CSV export. We parse each array, deduplicate within the destination, and create Odoo Tags before linking them to Contact records via crm.lead.res.partner.rel. Tag name collisions are resolved by appending a numeric suffix.

folk attachments linked to Contacts export as URLs or files via CSV. We attempt to download source files and re-upload them to Odoo as ir.attachment records linked to the res.partner. File size limits and supported formats follow Odoo's attachment configuration. Attachments that are file references (not downloadable URLs) are flagged for manual re-upload post-migration.

Activity history present in folk CSV export (calls logged, emails tracked, meetings scheduled) migrates to Odoo CRM as mail.activity records. Each activity type (call, email, meeting) maps to a corresponding Odoo activity_type_id. Activity date and duration preserve. Odoo's activity list on the partner form shows timeline history. We note gaps where folk CSV does not expose activity metadata beyond the contact level.

folk per-group custom fields require special handling because the same field name may not exist across all Groups. We enumerate every Group's custom field schema during discovery, identify fields that appear in multiple Groups with consistent types, and create Odoo module-level custom fields (ir.model.fields with custom=True) for those. Fields that exist in only one Group are created as Odoo custom fields but may be left unmapped for contacts outside their originating Group. The customer reviews the consolidated field map before migration.

Magic Fields are AI-generated values computed at query time from source data and the folk AI model. They are not stored as persistent records and cannot be exported. We do not migrate Magic Field values. Customers who rely on Magic Field outputs should regenerate them post-migration in Odoo using Odoo's built-in automation rules or a third-party AI enrichment tool of their choosing.

Enrichment data is live-fetched by folk's AI engine and not persistently stored in an accessible format. The enriched field values are not available for export. We do not migrate enrichment credits or their outputs. Post-migration, customers can connect an Odoo-compatible enrichment service (Clearbit, Apollo, or FullContact) as a replacement for folk's enrichment layer.