Migrate from eSalesTrack to Odoo CRM

eSalesTrack Contacts map to Odoo CRM Contacts. The eSalesTrack company name field maps to the partner_id Many2one relationship pointing to the Odoo Contact record representing the company, and eSalesTrack contact name fields map to Odoo's name field split into firstname and lastname if Odoo name strips are enabled. We pre-create the Account records from eSalesTrack Companies before importing Contacts so that the partner_id foreign key is satisfied at insert time. Any eSalesTrack Contact without a matching Company record lands as an individual Contact without a parent company.

eSalesTrack Company records map to Odoo Contacts with is_company=True. The Company name becomes the Contact name field, domain and industry properties map to Odoo's website and industry fields, and address fields map via Odoo's contact address fields (street, city, state, country, zip). We use a company dedupe key on the domain field to avoid creating duplicate Account records when eSalesTrack has multiple Contacts from the same Company.

eSalesTrack Leads map to Odoo CRM Leads (crm.lead model). The lead name, email, phone, source, and medium properties map to Odoo's name, email_from, phone, source_id, and medium_id fields respectively. Any eSalesTrack custom lead fields migrate to Odoo custom fields created via Odoo Studio before migration. Lead status from eSalesTrack maps to a Odoo Stage value that we pre-configure in the CRM pipeline settings.

eSalesTrack Deal records with a pipeline stage map to Odoo CRM Opportunities (crm.lead records with type=opportunity). The Deal name becomes the Opportunity name, the eSalesTrack deal amount maps to Odoo's expected_revenue, and the pipeline stage maps to the crm_stage_id with probability recalculated per Odoo's stage settings. We configure the Odoo pipeline stages and their sequence before migration so that stage names align with eSalesTrack's pipeline columns.

Each eSalesTrack pipeline becomes an Odoo CRM Pipeline with corresponding Stage records. Stage names, sequence order, and probability percentages migrate to Odoo Stage records within that pipeline. Odoo enforces a 1-100 probability range per stage, so any eSalesTrack probabilities outside that range are rounded to the nearest valid integer during the transform step.

eSalesTrack Owner records map to Odoo CRM Users by email address match. We extract every distinct owner_id referenced on Contact, Company, Lead, and Opportunity records and match against the destination Odoo instance's res.users table. Any eSalesTrack Owner without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignments migrate as user_id on the crm.lead and res.partner records.

eSalesTrack email engagements map to Odoo Mail Message records linked to the parent Contact or Lead via model and res_id. The email body and subject migrate to mail.message body and subject fields. Odoo stores message threading via parent_id for replies. Without an Odoo mail gateway migration, incoming email addresses do not auto-link to existing records; we manually set the res_id on each message to the correct Contact or Lead record during staging.

eSalesTrack call engagements map to Odoo CRM Phonecall records (crm.phonecall model). Call duration, disposition, and outcome map to Odoo's duration, state, and partner_phone_mobile fields. If crm_phonecall is not installed in the destination Odoo instance, calls migrate as Note records on the Contact or Lead instead. Activity timeline ordering is preserved by setting the create_date to the original eSalesTrack timestamp.

eSalesTrack meeting engagements map to Odoo Calendar Event records (calendar.event model). Meeting title, start datetime, end datetime, and location map to Odoo's name, start_datetime, stop_datetime, and location fields. Attendee relationships are created as calendar.attendee records linked to the Contact or Lead.

eSalesTrack Note engagements map to Odoo Note records (note.note model) attached to the relevant Contact, Lead, or Account. The note body migrates as the note field with create_date preserving the original timestamp. If the destination Odoo instance uses the Discuss module for notes instead, notes migrate as mail.message records with no email_partner_ids.

eSalesTrack task engagements map to Odoo Project Task records (project.task model) if the Project module is installed, or to CRM Activity records (crm.activity) if only the CRM module is active. Task name, due date, priority, and status migrate to the chosen destination model. Owner mapping links the task to the correct Odoo User record via user_id.

eSalesTrack Products map to Odoo Product Templates (product.template model). The product name, SKU, and price fields migrate to name, default_code, and list_price respectively. If eSalesTrack tracks cost price, it maps to standard_price on the product.template.

Any eSalesTrack custom fields on Contact, Company, Lead, or Opportunity records migrate to Odoo custom fields created via the Settings > Technical > Database Structure > Fields menu or via Odoo Studio. We map eSalesTrack field data types to Odoo field types: text to char, dropdown to selection, checkbox to boolean, number to float or integer, date to date. Custom fields are created in the destination Odoo instance before any data import begins.