Migrate from Market Maker to Odoo CRM

Odoo uses a single res.partner model for contacts and companies. Market Maker contacts migrate as res.partner records with partner_latitude/longitude, function (jobtitle), and category_id preserved. The primary company from Market Maker attaches as parent_id on the partner record; additional company associations require Account Contact Relation records in Odoo.

Market Maker companies become res.partner records with is_company=True. The company name maps to name, domain to website, industry to industry_id via value_mapping, and annual_revenue to property_account_receivable_id for financial reporting. Child contacts from Market Maker link via parent_id to the migrated company partner.

Market Maker leads map directly to Odoo crm.lead records. The type field is set to lead by default. Market Maker lead properties (source, score, status) migrate to crm.lead fields using value_mapping where pick-list values differ between platforms. The original lead create_date is preserved as create_date for reporting continuity.

Market Maker deals become Odoo crm.lead records with type=opportunity. The deal amount maps to planned_revenue, deal name becomes name, and the close date maps to date_deadline. Pipeline stage from Market Maker translates to stage_id by looking up the matching crm.stage record by name within the target pipeline_id.

Market Maker deal pipelines map to Odoo crm.team (sales team) records. Each pipeline requires a corresponding crm.team to be created in Odoo before migration, with team_member assignments resolved by email matching to res.users. The crm.team's alias_name handles inbound email-to-lead routing.

Stage names from Market Maker require value-by-value mapping to existing Odoo crm.stage records. If a Market Maker stage name does not match an Odoo stage, the closest stage is selected and the original name is preserved in a custom Char field (x_original_stage_name__c) for audit purposes. Stage sequence order is preserved.

Market Maker call records migrate to Odoo mail.activity with activity_type_id set to call. The original call date maps to date_deadline and create_date, user_id maps to the matched owner, and the call outcome or notes map to activity note body. Activity records are linked to the parent res.partner or crm.lead via res_model and res_id.

Market Maker email engagement records become Odoo mail.activity with activity_type_id=email. The subject line maps to activity note body, sender/recipient preserved in description, and original timestamp maps to create_date. Email threads do not migrate as Odoo mail.message records because thread reconstruction requires access to raw MIME content not typically exported from Market Maker.

Market Maker meetings map to mail.activity with activity_type_id=meeting, preserving original start and end timestamps as date_deadline and x_meeting_end_date__c custom fields. Notes map to mail.activity with activity_type_id=note, with the note body stored in the activity's note field. Both activity types inherit the create_date and user_id from the source record to maintain accurate audit trails and ownership attribution within Odoo's activity timeline view.

Market Maker custom fields on any object require Odoo-side ir.model.fields creation before migration. We deliver a schema setup plan listing each custom field name, Odoo field type (Char, Selection, Float, etc.), and target model. Fields are created via FlitStack's Odoo setup module or provided as a guide for your admin to create before the migration run.

Market Maker file attachments on records migrate as Odoo ir.attachment records with res_model pointing to the migrated model and res_id pointing to the migrated record's Odoo ID. Files are re-uploaded to Odoo's filestore. Large files (>25MB) may require Odoo filestore configuration adjustment before migration.

Market Maker owner_id values are resolved by email match against Odoo res.users. Matched owners map to crm.lead user_id and res.partner user_id. Unmatched owners are assigned to a designated fallback user (created as a placeholder res.users record) and flagged in the migration report for admin review and reassignment.

Market Maker contact-to-company association labels (like 'Decision Maker' or 'Technical Contact') have no direct Odoo equivalent. Labels are preserved as a Selection field on the contact's res.partner record (x_association_label__c) for reference. Role-based relationship labeling requires rebuilding using Odoo's Contact / Company relationship settings post-migration.

Market Maker's built-in sales activity reports do not migrate. Historical data underlying the reports transfers as crm.lead and mail.activity records, which can be queried via Odoo's reporting interface or via direct PostgreSQL access for custom BI tools. FlitStack can deliver a sample SQL query set for Odoo reporting continuity.