Migrate from Manta Business Management Software to Odoo CRM

Manta Contact records map to Odoo res.partner, but Manta uses a flat contact model with no explicit individual-company distinction. We apply a split heuristic at migration time: contacts with a non-empty company_name field or with a website domain present in the email address become res.partner with partner_type = company; all others become partner_type = individual. The split rule is validated during the sandbox phase. Email, phone, street, city, state, zip, country, and title fields map to their Odoo equivalents via the XML-RPC partner write method.

Manta Company records map directly to Odoo res.partner with partner_type = company. Industry, employee count, annual revenue, and website fields map to industry_id, employee_size, revenue, and website respectively on the res.partner record. Company-contact linkage in Manta (which associates a contact with a company) maps to the child_partner_ids relationship in Odoo: we create the company partner first, then link individual contacts as children of that partner record. This dependency means Company records must migrate before Contact records.

Manta Lead records map to Odoo crm.lead with type = lead. Lead status, source, assigned owner, and any lead scoring values map to stage_id, source_id, user_id, and priority respectively. The Odoo crm.lead model stores leads and opportunities in the same table with a type field distinguishing them, so Lead records are created with type = lead and stage set to the appropriate Manta lead stage equivalent. Tags from Manta migrate to Odoo tag_ids using the crm.lead.tag model.

Manta Deal records map to Odoo crm.lead with type = opportunity. Deal name, value, expected close date, and stage map to name, planned_revenue, date_deadline, and stage_id. The linked company from Manta's deal-company association becomes partner_id on the Odoo opportunity; the linked contact becomes the opportunity's Contact Name. If a Manta deal has no associated company, the opportunity is created without a partner_id and the customer's Odoo admin assigns it after migration.

Manta deal stage names map to Odoo crm.stage records within the applicable sales team. We create stage records with the same names and assign probabilities matching Manta's stage percentages. Odoo stage records are ordered using the sequence field to preserve the pipeline order. Stages must be created in Odoo before opportunity records referencing them are imported.

Manta tags associated with contacts, companies, leads, or deals migrate to Odoo crm.tag records. Each tag is created once in the tag master table, then assigned to crm.lead records via the tag_ids many-to-many relationship. Tags used on multiple object types in Manta are preserved as shared tags in Odoo rather than duplicated per object type.

Manta User records map to Odoo res.users. We match by email address and map name, email, and role to the Odoo user record. Inactive or archived users in Manta are mapped to inactive res.users records in Odoo so that historical owner assignments on leads, deals, and activities resolve correctly. Active users are assigned to the appropriate Odoo access rights group (Sales / User or Sales / Manager) based on the role field. User provisioning must be validated before record migration because OwnerId references on crm.lead records are required.

Manta call records migrate to Odoo mail.activity records linked to the parent crm.lead (Lead or Opportunity). Activity type maps to activity_type_id, subject to the call title, date to activity_date_deadline, and notes to note. Odoo's CRM app displays activities on the lead and opportunity form view under the Activities smart button. If the customer's Odoo instance uses the calendar module, calls with scheduled times also create calendar.event records.

Manta email activity records migrate to Odoo mail.message records linked to the parent crm.lead. The email subject becomes the message subject, body becomes the message body stored as HTML, and date maps to message_date. Odoo's mail.thread mechanism on crm.lead displays email history in the communication history tab. If the customer uses Odoo's email gateway (Incoming Mail Server), emails with matching email_from addresses link to the correct partner on the lead.

Manta meeting records migrate to Odoo calendar.event records. Meeting title, start datetime, end datetime, location, and attendee list map to name, start, stop, location, and partner_ids respectively. Partner attendee resolution uses email matching against res.partner. Calendar events display on the Odoo CRM pipeline view and in the Sales app's calendar dashboard. The customer must have the calendar module installed and active for event records to render correctly.

Manta task records migrate to Odoo project.task if the customer uses Odoo's project management module, or to mail.activity if the project module is not active. Task title, due date, status, and assigned owner map to name, date_deadline, stage_id, and user_id respectively. Manta's task notes field becomes the task description. We determine the correct target model during scoping based on the customer's Odoo module configuration.

Manta note records (standalone notes not tied to a specific activity type) migrate to Odoo note.note records. We link each note to the parent crm.lead (Lead or Opportunity) using the res_model = crm.lead and res_id reference. If the note has a linked contact or company in Manta, we also link it to the corresponding res.partner record. Note content migrates as plain text or HTML depending on the Manta export format. Odoo displays notes on the CRM lead form under the Notes smart button.

Manta custom fields on Contact, Company, Lead, and Deal records are not migratable. Custom field definitions are not exposed via any documented API or export format, and we cannot reliably identify which fields are custom versus standard from a flat CSV export. We document every unmapped field found in the Manta export during scoping so the customer's Odoo admin knows which data will not carry forward. Standard Odoo field creation via Settings / Technical / Database Structure / Models is the rebuild path.

Manta file attachments associated with contacts, companies, or deals do not migrate. The platform does not expose a documented file storage API, and binary file handling falls outside standard CRM migration scope. We flag any attachment references found in the Manta export and deliver a written list of file names and their parent record types for the customer to re-upload manually in Odoo after go-live.

If Manta Deals contain product line items or if product records are present in the Manta export, they map to Odoo product.product. Product name, SKU, list price, and cost map to name, default_code, list_price, and standard_price respectively. Products must be created before OpportunityLineItem records that reference them, so product migration runs before opportunity import. Odoo requires the product variant management setting to be configured if the customer uses product attributes.