Migrate from Sentian Solutions to Odoo CRM

Sentian contacts migrate to Odoo res.partner records with contact_type='contact'. The Sentian contact's associated company becomes a separate res.partner record with type='company'; the contact record references it via parent_id. This resolves Sentian's contact-to-company 1:N relationship into Odoo's parent-child partner model. Additional Sentian fields such as job title, phone, and email map directly to Odoo res.partner.function, phone, and email. Extra phone numbers per contact are stored in custom fields to preserve detail.

Sentian companies map 1:1 to Odoo res.partner records with type='company'. The company name populates res.partner.name; domain maps to website. Industry, employee count, and annual revenue populate their Odoo counterparts or custom fields if Sentian uses extended pick-list values not present in Odoo's default industry list.

Sentian deals migrate as Odoo crm.lead records with type='opportunity'. The Sentian deal name populates crm.lead.name, amount populates planned_revenue, and close date populates date_closed. The pipeline maps to an Odoo sales_team via team_id; each pipeline in Sentian becomes one Odoo sales team with its own crm.stage records.

Sentian pipeline stages are pick-list values on the deal; Odoo stages are records in crm.stage grouped by sales team. We pre-create Odoo stages matching each Sentian pipeline stage name, preserving the sequence order. Probability values from Sentian are stored as sequence integers and as custom probability fields on the stage records for reporting continuity.

Sentian leads with a lifecycle stage property route to Odoo crm.lead as type='lead'. The lifecycle stage value is stored in a custom Char or Selection field on crm.lead (x_lifecycle_stage__c or similar) since Odoo has no native lifecycle field. Customers upgrading to Odoo's lead-scoring module can then build stage-based automation on top of that field.

Sentian logged calls map to Odoo crm.phonecall records. Subject, description, duration, call date, and partner_id (the related contact) are mapped directly. Owner is resolved by email match to Odoo res.users records; unmatched owners are flagged for admin assignment before migration commits.

Sentian email records migrate as Odoo mail.message entries linked to the crm.lead or res.partner record. Subject, body (plain text), date, and author_id are preserved. Odoo's mail.thread model associates messages with records automatically based on model and res_id. HTML email bodies are sanitized to plain text during import to avoid rendering issues in Odoo's message composer.

Sentian meeting records become Odoo calendar.event entries. Title, start datetime, stop datetime, duration, location, and attendee list (partner_ids) are mapped. Sentian meeting descriptions migrate as body text. Recurring meetings are flattened into individual event records since Odoo's calendar module handles recurrence on the event itself.

Sentian notes attached to contacts, companies, or deals become Odoo mail.message records on the target res.partner or crm.lead. Odoo distinguishes internal notes (mail.message with subtype=note) from emails; we flag Sentian notes as internal notes so they do not send to contacts. HTML formatting is stripped to Odoo's note-compatible subset.

Sentian custom objects with their own fields and relationships require Odoo custom module development or Odoo Studio configuration. We map the custom object to a new Odoo model and translate each custom field type to the closest Odoo field type (Char, Integer, Float, Selection, Many2one). N:N relationships in Sentian require Odoo Many2many fields in the custom model.

Sentian owner IDs on deals and activities resolve by email match against Odoo res.users. Unmatched owners are flagged in the pre-migration report; the customer either creates Odoo user accounts before migration or assigns records to a designated fallback user. This prevents orphaned records in Odoo that have no assigned sales rep.