Migrate from AgileCase to Odoo CRM

Every AgileCase Case maps to an Odoo crm.lead record. The Case title becomes the crm.lead name field. The Case description maps to crm.lead description. Original create dates are preserved in a custom field (Original_Create_Date__c) because Odoo's create_date reflects migration time.

AgileCase workflow stages map value-by-value to Odoo crm.stage records. Each AgileCase stage name creates or matches a corresponding Odoo stage in the target pipeline. Stage ordering and probability values are mapped from Odoo stage configuration. If AgileCase uses custom stage labels, they map 1:1 with explicit value mapping.

AgileCase stores client contact details inside the Case record. FlitStack extracts unique contact data to res.partner first (name, email, phone, address), then links the new partner to the crm.lead via the partner_id field. If the same client appears across multiple Cases, Odoo deduplicates by email match to avoid duplicate res.partner records.

AgileCase user email addresses are matched against Odoo res.users by email. Unmatched owners are flagged before migration — your team either creates the Odoo user first or assigns a fallback owner. This ensures every crm.lead lands with a valid user_id and appears in the correct Odoo sales team.

Every AgileCase custom field definition (text, number, date, pick-list, checkbox) is recreated as an Odoo custom field on the crm.lead model before migration. Pick-list fields in AgileCase create Odoo selection fields with the same options. Boolean fields map to Odoo boolean fields. Text fields with length limits map to Odoo char or text fields depending on content length.

AgileCase file attachments are downloaded, then uploaded to Odoo ir.attachment records linked to the parent crm.lead via res_model='crm.lead' and res_id set to the migrated lead ID. File names, MIME types, and binary content are preserved. Inline images in Case notes are extracted and rehosted as attachments.

AgileCase activity log entries (internal notes, status changes) are migrated as Odoo mail.message records on the crm.lead, with message_type='comment'. Original timestamps and author email are preserved. This gives Odoo a full historical timeline on the lead without requiring the OdooDiscuss or inbox modules.

AgileCase emails and SMS records linked to a Case migrate as mail.message records on the crm.lead. Email threads are reconstructed using subject-line grouping where AgileCase preserves thread context. Odoo's mail.message model supports email headers natively for thread reconstruction, including attachments.

AgileCase automations (task creation, email triggers, stage-change scripts) do not transfer. FlitStack exports your AgileCase workflow definitions as a JSON document — each rule's trigger, condition, and action is documented — which your Odoo admin uses as a rebuild reference for Odoo automated actions (Enterprise) or server actions (Community).

AgileCase client portal entries (shared documents, case status views) have no Odoo CRM equivalent. Odoo Website portal module must be installed for contact-facing case/opportunity visibility. Portal access rules, document sharing, and customer-facing status pages need to be rebuilt in Odoo Website after migration.

AgileCase audit trail entries (field name, old value, new value, changed by, timestamp) are serialized into a long-text custom field on each crm.lead. Odoo Community does not have a native audit log UI, so this custom field provides reference-level history for compliance review without requiring Odoo Enterprise.

AgileCase case categories or tags map to Odoo crm.tag records. A many2many relation (crm_lead_tag_rel) links each crm.lead to its tags. Tag names are preserved exactly. If AgileCase uses hierarchical tags, Odoo's tag model is flat — nested tag structures collapse to the leaf label.