Migrate from MARS to Odoo CRM

MARS Contact records map to Odoo res.partner with partner_type set to 'contact'. The MARS first_name and last_name fields concatenate to the res.partner name field. Email maps to email, phone to phone, and mobile to mobile. Street, city, state, zip, country from MARS address fields map to street, city, state_id (resolved from country/state table), zip, and country_id. We create the res.partner record first so that it is available as a parent_id for any MARS Contact records that share the same company.

MARS Company records map to Odoo res.partner with partner_type set to 'company' and is_company set to True. The company name becomes res.partner name. Website, industry, employee_count, and annual_revenue map to website, industry_id, employee_count, and revenue fields respectively. We use the MARS company domain to populate website without the http prefix. The commercial partner (contact of the company contact) is created for company-level contacts that exist in MARS as Company-linked individuals.

MARS Deal records map to Odoo crm.lead with type set to 'opportunity'. The MARS deal name maps to name, expected_close_date to date_deadline, amount to planned_revenue, and probability to probability (with stage-based defaults overridden if MARS stores explicit probability). partner_id (the commercial partner lookup) is resolved from the MARS deal's linked company or contact via email domain match against res.partner. user_id maps to the Odoo res.users owner resolved by email.

Each MARS pipeline stage becomes an Odoo crm.stage record within the relevant crm.team's stage pool. Stage sequence order and name migrate directly. Probability percentages migrate to the probability field on each stage. If MARS stores won/lost as stage properties, these map to fold (archived won) and stage_type (won/lost). We configure stage before opportunity migration so that stage_id lookups resolve during import.

MARS deal pipelines map to Odoo crm.team records (one per pipeline). Each crm.team gets its own stage pool via team_use = 'multi' in the crm.team configuration. Stage assignments in MARS determine which crm.team a crm.lead belongs to via the team_id field. This mapping requires crm.team to be created before opportunities are imported.

MARS Owner records are resolved by email match against Odoo res.users. The MARS owner_id on each Contact, Company, and Deal record maps to the user_id or user_ids field in Odoo on the corresponding model. Any MARS Owner without a matching Odoo res.users is placed in a reconciliation queue for the customer's admin to provision the User before record import resumes.

MARS email engagements map to Odoo mail.message records with message_type = 'email'. The email subject maps to subject, body to body (HTML preserved), and date to date. The mail.message record is linked to its parent res.partner via res_id and model = 'res.partner'. We batch insert via XML-RPC in chunks of 100 to respect Odoo's request size limits.

MARS call engagements map to Odoo crm.activity records with activity_type_id referencing the phone call activity type. Call duration, disposition, and notes map to custom fields on crm.activity. The activity is linked to the parent res.partner (contact) via res_id and model. Activity date preserves the original MARS timestamp for timeline ordering.

MARS meeting engagements map to Odoo calendar.event records. Start datetime and end datetime migrate to start and stop. Location maps to location. Attendees are linked via calendar.attendee records pointing to the res.partner invitees. Meeting notes map to description. We create calendar.event records via XML-RPC after res.partner records are fully loaded.

MARS task engagements map to Odoo project.task if the customer requires project management capabilities, or to crm.activity if tasks are scoped to CRM activity tracking. Task title, description, due date, priority, and completion status migrate directly. Assignment resolves to res.users via email match. The customer selects the target model during scoping.

MARS tags on Deals map to Odoo crm.tag records. The tag-to-record association migrates via crm.lead.tag.rel (many-to-many). Tags stored on Contacts map via res.partner.category (which is a generic tag model in Odoo used across multiple objects). Tag names preserve exactly as stored in MARS for consistency with existing reporting.

MARS custom fields on Contact, Company, and Deal objects require pre-creation in Odoo before migration begins. We use the ir.model.fields API to create custom fields with the correct field type (char, text, integer, float, boolean, date, datetime, selection, many2one, one2many, many2many) matched from MARS field types. Custom fields are created in the Odoo target database before any data import to avoid import-time validation errors.

MARS file attachments linked to Contact, Company, or Deal records map to Odoo ir.attachment. The attachment name, mimetype, and binary content (datas as base64) migrate. Attachments are linked to their parent record via res_model (res.partner or crm.lead) and res_id. We export attachments separately as binary files referenced by URL or file path, then attach via XML-RPC after the parent record exists in Odoo.

MARS notes (free-text records separate from activities) map to Odoo mail.message with subtype = 'note' to distinguish from email-type messages. Note body preserves HTML formatting. Notes linked to Contact, Company, or Deal associate via res_model and res_id. Notes without a parent record are linked to the user's res.partner record as a general note.