Migrate from Combit CRM to Odoo CRM

Combit CRM's Address records store location data (street, city, postal code, country) as separate records linked to multiple Contact records. We extract address fields from the Anschrift table and map them to the standard address fields on res.partner in Odoo (street, street2, city, zip, country_id). Because Odoo's Contact model does not use a separate address record, we resolve the contact-to-address relationship during the transform phase and populate partner address fields directly. If a Combit contact has multiple addresses, the primary (default) address maps to res.partner and additional addresses migrate to res.partner.address_ids as a one2many relation.

Combit Contacts map to Odoo res.partner records. The mapping preserves name fields (firstname, lastname, function/title), phone, email, and website, and resolves the parent Address record reference to Odoo's inline address fields. Combit's contact type (person vs. organization) maps to Odoo's is_company flag: individual contacts set is_company=False; organization contacts set is_company=True and the name maps to the company name field. Partner lang defaults to en_US unless the customer's scoping identifies a different language preference.

Combit Companies map to Odoo res.partner records with is_company=True. Company name, industry classification, revenue range, and number of employees migrate to the corresponding Odoo partner fields. Company records serve as the parent for related Contact records; we create the Company partner first, then resolve the parent_id reference when importing the associated Contact partners. Website domain from Combit maps to partner website field and is used as the deduplication key if the customer has existing partner records in Odoo.

Combit Deals map to Odoo crm.lead records in the Opportunities view. We preserve the deal name, value (expected_revenue), expected_close date, stage name, and owner. Combit's configurable pipeline stages map to Odoo's crm.stage values, which we pre-create in the destination Odoo instance before migration to match the Combit stage names translated to English. Loss reason and win reason from Combit custom fields migrate to Odoo's lost_reason and won_reason fields. Note that Odoo uses a single crm.lead model for both inbound leads and opportunities; Combit's separate Deal concept maps to crm.lead with type='opportunity'.

Each Combit Deal pipeline stage becomes an Odoo crm.stage record. We preserve stage sequence order, probability percentage (where set in Combit), and the stage name in English. The Combit pipeline (if multiple exist) maps to Odoo crm.team, with each Combit pipeline assigned to a separate sales team in Odoo. If Combit has custom stage colors or categories, these map to Odoo's stage_color field if available or are documented as notes for the admin.

Combit Activities (calls, meetings, tasks, notes) attached to Contacts or Deals map to Odoo's crm.activity records for calendar events and to mail.message records for the chatter timeline. We preserve activity type, date, duration, description, and owner. Combit's Activity-to-Contact and Activity-to-Deal lookups resolve to the migrated Odoo partner_id and crm_lead_id references. If Combit stores email body content in activities, that migrates as a mail.message on the crm.lead or res.partner.

Combit Projects span multiple contacts and activities and may include budgets, line items, and dates. If the destination Odoo instance includes the Project module (Odoo Enterprise or a community project app), we map Combit Projects to project.project records with tasks migrated as project.task. If only the CRM module is in scope, Combit Projects with linked Deals map to crm.lead records with project name preserved in a custom field for reference, and we flag the project-object gap in the handoff documentation. Project-to-Deal relationships are preserved via a lookup field.

Combit CRM supports extensive user-defined fields across all objects. We identify every custom field definition during the discovery phase (field name in German, data type, picklist values), translate the label to English, map the Combit data type to the equivalent Odoo field type (char, text, integer, float, selection, many2one, one2many), and pre-create the fields in the destination Odoo schema via data migration or a Studio export-import round trip before the main record import begins. Multi-select picklists map to Odoo many2many tags or selection fields depending on expected cardinality.

Combit Users map to Odoo res.users records. We resolve by email match. If the customer has an existing Odoo instance with existing users, we match Combit owner email to Odoo user login. Any Combit owner without a match goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Combit owners (departed employees) map to inactive Odoo users to preserve historical assignment data.

Combit Categories used to tag Contacts, Companies, and Deals map to Odoo crm.tag records. Multi-value category assignments on a single Combit record map to multiple crm.tag records via crm.tag.rel many2many table entries. We preserve tag names in English (translated during the mapping phase) and flag any tag that appears on fewer than 5 records as a low-frequency tag that may need cleanup in Odoo.

Combit CRM file attachments on records migrate to Odoo ir.attachment records linked via res_model and res_id to the migrated parent record (res.partner or crm.lead). We extract files from the Combit database or file store, preserve original filenames and MIME types, and store them in Odoo's attachment storage (database or filestore depending on Odoo configuration). Files larger than Odoo's default attachment size limit are flagged for the admin to review before migration.

Combit's complete engagement timeline—calls, meetings, tasks, notes, and logged emails—migrates to Odoo's crm.activity records (for calendar-type entries) and mail.message records (for note-style entries and email content). The original timestamp, owner, and description are preserved. Activity type mapping: Combit 'Telefonat' maps to crm.activity with subtype='call'; 'Besprechung' maps to crm.activity with subtype='meeting'; 'Notiz' maps to mail.message; emails map to mail.message with message_type='email'. The parent record reference (contact_id, lead_id) is resolved to the migrated Odoo IDs at migration time.