Migrate from X2CRM to Odoo CRM

X2CRM Contacts map directly to Odoo Contacts using email as the deduplication key. Standard fields (name, email, phone, address) map 1:1. Custom contact fields created in X2CRM's module builder migrate to Odoo custom fields (char, text, integer, float, selection) based on schema inspection during discovery. Phone number formatting is normalized to E.164 before import to avoid Odoo validation issues with international formats.

X2CRM Accounts represent companies and organizations linked to Contacts. They map to Odoo Companies (res.partner with is_company=True). Associated tags, lifetime value, and linked Contact relationships are preserved via partner_id lookups. The X2CRM account name becomes the Company name field, and the primary contact link is established via the Contact import phase.

X2CRM Deals track sales opportunities with stage, value, probability, and expected close date. They map to Odoo CRM Opportunities (crm.lead with type='opportunity'). Pipeline stage associations map to Odoo stage_id with probability percentages transferred from X2CRM. Deal owners map to Odoo user_id via email reconciliation. Activity history attached to Deals migrates as Odoo MailMessage records linked to the Opportunity.

Each X2CRM pipeline with its deal stages maps to an Odoo Stage within the CRM app's pipeline kanban view. Stage names, sequence order, and probability percentages are recreated in Odoo. The X2CRM stage probability field becomes the Odoo stage probability value. If the customer uses multiple X2CRM pipelines, each maps to a separate Odoo sales team or pipeline view configuration.

X2CRM Services track recurring service contracts or subscriptions linked to Accounts. They map to Odoo Subscriptions (sale_subscription module, available in Odoo Enterprise or via the Odoo Marketplace for Community). Service status, renewal dates, and associated Account links transfer directly. Recurring revenue amounts map to the subscription template pricing.

X2CRM Products (catalog items with pricing, SKU, and description) map to Odoo Products (product.product). Associated price books in X2CRM become Odoo Pricelist entries attached to the Product. Line-item associations with Deals are preserved via the Opportunity mapping. Product type (service vs goods) maps to Odoo's product_type field.

X2CRM Marketing Campaigns (name, type, status, associated mailing lists) map to Odoo CRM Campaigns. Campaign history and linked contacts are preserved via partner_id lookups. Email campaign templates migrate as static HTML content where the destination supports template storage. Note that Odoo's marketing automation features require the Marketing application which is a separate license; we document the template and list structure for manual recreation.

X2CRM Activities (calls, meetings, tasks with timestamps, owners, and related Contacts or Deals) map to Odoo MailActivity records. We sequence Activities in chronological order and map related record IDs to their new Odoo IDs during the resolution phase. X2CRM activity type (call, meeting, note) maps to Odoo's activity_type_id. The activity's related Contact or Deal is resolved via the partner_id lookup after the parent record import completes.

X2CRM Tags are standalone label records that can be applied to multiple object types. They migrate to Odoo Tags (mail.template.tag or a dedicated tag model depending on usage). We reapply tag associations to their target records post-import, maintaining the many-to-many relationships. If tags number over 200, we coordinate with the customer on a tag consolidation strategy before migration to avoid Odoo tag proliferation.

X2CRM custom fields added via the module builder vary by module and require field-level mapping during scoping. We inspect the X2CRM field schema via API discovery and align each custom field to an equivalent Odoo field type (char, text, selection, many2one, etc.). Custom field labels and help text transfer as field descriptions. If the target Odoo field does not exist, we create it during schema deployment before the data import phase begins.

X2CRM User accounts include name, email, role, and assignment permissions. Role configurations (viewer, editor, admin) map to Odoo access rights (read, write, create, delete) on a per-model basis. We export user records but flag that active User provisioning in Odoo must be completed by the customer's admin before record ownership assignments are applied. Inactive X2CRM users may be migrated as portal users in Odoo if customer-facing access is required.

X2CRM Attachments are stored as file references or blobs linked to records. For cloud-hosted X2CRM instances, we download attachments and re-upload to Odoo's IrAttachment model via the ORM. For self-hosted instances with local disk storage paths, we coordinate with the customer's IT team to expose the upload directory for extraction. Attachments are linked to the parent record (Contact, Company, Opportunity) via res_model and res_id fields after parent record import completes.