Migrate from Delta Sales CRM to Odoo CRM

Delta's unified contact records map to both Odoo CRM Lead and Contact objects. We apply a status-based split rule during scoping: contacts with Delta status of Prospect or New map to Odoo Lead; contacts with status of Customer or Active map to Odoo Contact attached to a Partner record. The original Delta status is preserved in a custom field x_delta_contact_status on both the Lead and Contact for audit and reporting continuity.

Delta Company records map to Odoo res.partner records with company_type = 'company'. The Partner record is created before any Contact or Lead import so that the parent_id lookup is satisfied at insert time. Delta's company address fields (street, city, state, zip, country) map to Odoo's address field format using the standard street, street2, city, state_id, zip, country_id field layout.

Delta Lead records with their current status, source attribution, and owner assignment map directly to Odoo CRM Lead. The lead_id from Delta is preserved in x_delta_lead_id as a custom reference field. If Delta's Lead has been converted to a Deal, we flag the original Lead as converted and link it to the migrated Opportunity in Odoo.

Delta Deal records map to Odoo crm.lead with type = 'opportunity'. Delta deal stage maps to Odoo stage_id within the configured sales team pipeline. Deal amount, probability, expected close date, and description migrate directly. The partner_id (Customer) and contact_id (primary contact) are resolved from the already-migrated Partner and Contact records using Delta's company_id and contact_id foreign keys.

Delta's multiple customizable pipelines become Odoo CRM Sales Teams (crm.team). Each Delta pipeline name and stage sequence is recreated as a crm.team record with its own stage_ids ordered to match Delta's stage sequence. Stage probability percentages from Delta are stored as Odoo stage probability values. Teams that use Delta's multi-pipeline feature for separate business lines map each pipeline to its own crm.team in Odoo so that stage values remain scoped per line of business.

Delta Activities (tasks, meetings, calls, reminders, follow-ups) map to Odoo's mail.activity model. Activity type from Delta maps to Odoo activity_type_id. The assigned user maps by email match to the Odoo User. Activity date, summary, and notes migrate. Odoo's mail.activity model is linked to the parent crm.lead record via res_model and res_id fields. Note that Odoo Activities are calendar-linked rather than timeline-linked, so call disposition and call duration require custom fields.

Delta Products map to Odoo product.template records with type = 'product' or 'service' based on Delta's product type. Product name, default_code (SKU), list_price, standard_price, and description migrate. UoM (unit of measure) is mapped from Delta's unit field to the closest Odoo uom.uom match. Product categories from Delta map to Odoo product.category records.

Delta Invoice records map to Odoo account.move with move_type = 'out_invoice'. Invoice header fields (number, date, due date, partner_id) migrate directly. Line items require the product_id to be resolved from the already-migrated product.template records. Payment state from Delta maps to Odoo's payment_state field. We confirm Odoo Accounting is installed before this mapping applies — if only CRM is deployed, invoices cannot be imported.

Delta Payment records map to Odoo account.payment linked to the corresponding account.move invoice via the reconciled_move_line_ids relationship. Payment amount, date, and payment method migrate. The payment must be reconciled with the invoice after both records are created, which requires processing payments after the invoice import phase.

Delta's Beat Plans have no native equivalent in Odoo CRM. Beat Plan route sequences (which customers a rep visits and in what order) are reconstructed as a series of custom fields on the crm.team (x_beat_route_sequence, x_beat_route_json) and as notes or tasks on the related Partner records. We export the beat plan assignment, route order, and customer sequence from Delta and represent them as a structured custom object in Odoo. The customer's admin decides whether to rebuild beat planning using Odoo Project tasks with planned dates or maintain the route sequence as a reference document.

Delta Custom Fields across all objects are recreated as Odoo custom fields via the Settings > Technical > Custom Fields interface or the ir.model.fields API before data import. We export Delta's custom field definitions (name, type, required flag) during discovery and pre-create the equivalent Odoo field with the same technical name and field type. Custom field values migrate as part of the standard record import using the custom field's API name.

Delta file attachments migrate to Odoo ir.attachment records linked to the parent record (res.partner, crm.lead) via res_model and res_id. File binary data, filename, and mimetype preserve. We flag large attachment batches (>5,000 files or total volume >10 GB) during scoping because they require batch processing and may extend the timeline by one to two weeks. Attachment migration does not include Delta's document-level access controls; Odoo's record-level access is configured post-migration.

Delta Users (owners assigned to contacts, companies, deals, and activities) map to Odoo res.users records by email match. Owners without a matching Odoo User are held in a reconciliation queue for the customer's admin to provision before record import resumes. Active/inactive status from Delta is preserved in a custom field x_delta_user_active on the Odoo User record.