Migrate from Sentia to Odoo CRM

Sentia Contact records map directly to Odoo CRM Partner records with the Internal Partner type set to True, which exposes the Contact subtab within the Partner form. The Sentia contact's name, email, phone, job title, and address fields map to the equivalent Partner fields. Custom Contact-level properties on Sentia migrate to Odoo custom fields on res.partner. The Sentia Contact-to-Company association is preserved by linking the Contact's parent_id to the mapped Partner representing the Company.

Sentia Company records map to Odoo CRM Partner with the Company type checkbox enabled, which suppresses the Contact subtab and presents the organization as a top-level entity. Company names serve as the dedupe key on Partner import; we match by normalized company name and domain for duplicate detection. Company address and industry data map to Partner address fields and a custom industry tag field.

Sentia's separate Lead and Contact objects require a consolidation step for Odoo CRM. Sentia Leads with status = Unqualified merge into Odoo CRM crm.lead records carrying the original lead source and status as tags. Sentia Leads with status = Qualified merge into Odoo CRM Partners (with Internal = False, i.e., external contacts). The original Sentia lead_id is preserved in a custom field x_sentia_lead_id for audit trail and cross-reference. This merge approach avoids creating duplicate Partner records for prospects that already exist as Contacts in Sentia.

Sentia Deal records map to Odoo CRM crm.lead with type = Opportunity. The Deal name becomes the Opportunity name; deal value maps to Odoo's Expected Revenue field. Closed-won and closed-lost status from Sentia map to Odoo's Stage field using the Lost or Won stage values. The Sentia Deal-to-Contact and Deal-to-Company associations resolve to the mapped Partner contact and Partner company via the partner_id and partner_id.contact_id fields on crm.lead.

Sentia pipeline stages map to Odoo CRM Stage records within the Sales app. Each Sentia stage name becomes a Stage name in Odoo with the corresponding sequence order preserved. Sentia's stage probability percentages map to Odoo's Stage probability field, rounded to the nearest integer. If Sentia has multiple pipelines, we create separate Sales Teams in Odoo CRM and configure stage sets per team so that stage values are scoped to the relevant pipeline.

Custom fields on Sentia Contacts, Companies, Leads, and Deals migrate to Odoo custom fields on the equivalent model (res.partner for Contacts and Companies, crm.lead for Leads and Opportunities). The Ultimate tier exposes more API-accessible custom field types than Basic; we query the Sentia metadata API during discovery to enumerate all available custom fields and match them to Odoo field types (Char, Selection, Float, Date, Many2one, etc.) using Studio. Any custom field not available on the active Sentia tier is flagged before migration begins.

Sentia activity records (calls, emails, meetings, notes) attach to Odoo CRM via mail.message records on the parent Partner or CRM Lead. Call records map to mail.activity with activity_type_id = Call and the duration stored in a custom field. Meeting records map to mail.activity with activity_type_id = Meeting and start/end preserved. Email records map to mail.message with mail_message_type = email and the email body preserved. Notes map to mail.message with mail_message_type = comment and author attribution. Activity timestamps from Sentia are preserved as write_date and create_date on the Odoo records.

Sentia Users who own records map to Odoo Users by email match. We extract every distinct owner_id referenced on Contacts, Companies, Deals, and Activities and match by email against the destination Odoo User table. Any Sentia User without a matching Odoo User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Odoo Users can receive historical records if the customer wants to preserve assignment history without activating the user.

File attachments associated with Sentia Contacts, Companies, Deals, or Activities migrate as ir.attachment records linked to the equivalent Odoo Partner or CRM Lead via res_model and res_id. Files are re-uploaded via Odoo's /web/binary/attachment API with the original filename and MIME type preserved. Attachments larger than 25MB are flagged as a separate migration step because Odoo's base attachment field has a configurable size limit that may require ir.config_parameter adjustment.

Sentia Tags migrate to Odoo CRM crm.tag records created on the fly during import and associated with crm.lead via the tag_ids many2many field. Company-level tags from Sentia migrate to Partner tags if the customer chooses to enable the partner.tags module. Duplicate tag names are deduplicated by normalized lowercase name before insertion.

Sentia voice workflow configurations reference internal record IDs and CRM object references that are not transferable to Odoo. We export a JSON representation of the voice workflow definitions (trigger conditions, action steps, and field updates) for the customer's admin to review and manually reconfigure in Odoo Studio or as server actions. This step is documented in the automation handoff inventory.

Sentia automations and workflow rules are platform-specific logic with no portable schema. We export the automation rules as a JSON document listing each rule's name, trigger type, condition fields, and action steps. The customer receives this as a written inventory with recommended equivalents in Odoo Studio (Automated Actions, Server Actions, or Base Action Rules). Rebuilding these in Odoo is outside standard migration scope.