Migrate from MetroLeads to Odoo CRM

MetroLeads Lead records map to Odoo crm.lead. Leads with terminal MetroLeads state values (e.g., won, customer) map directly to crm.lead with type=opportunity. Leads in intermediate states map to crm.lead with type=lead, and the customer decides whether to run Odoo's lead-to-opportunity wizard manually post-migration or batch-convert at migration time. We preserve MetroLeads state values in a custom Char field x_metro_state on crm.lead so the customer admin can map them to Odoo stage names during pipeline configuration.

MetroLeads Company records map to Odoo res.partner with is_company=True. The MetroLeads company UUID is stored in x_metro_company_id as a Char field for audit. Each MetroLeads Lead linked to that Company gets the res.partner record as its partner_id on the Odoo crm.lead. Companies with no associated Leads still migrate as standalone Partners to preserve the organizational structure.

MetroLeads phones are an embedded array on each Lead with type metadata (Work, Mobile, etc.). We extract the phone array, resolve the type, and map Work phones to res.partner.phone and Mobile phones to res.partner.mobile. Multiple phones of the same type are appended with a separator for the Odoo Char field. The original type metadata is preserved in x_metro_phone_type on the partner record.

MetroLeads emails are an embedded array with type metadata. We extract and map Work email to res.partner.email and Personal email to x_metro_email_personal for the custom field we create during schema setup. The original type metadata is stored in x_metro_email_type.

MetroLeads Events (call logs, meeting records, email tracking) map to Odoo mail.activity records. event_type maps to activity_type_id (Call, Meeting, Email, etc.) via the Odoo activity type configuration. event_timestamp maps to date_deadline and create_date preserves the original event creation time. The related crm.lead is set as res_id with model=crm.lead so activities appear in the Odoo lead chatter.

MetroLeads Users (sales reps, admins) map to Odoo res.users by email match. assigned_to on MetroLeads Leads becomes user_id on Odoo crm.lead. Any MetroLeads User without a matching Odoo User goes to a reconciliation queue for the customer's Odoo admin to provision before record import resumes.

MetroLeads state is a tenant-configured string field with arbitrary values. We extract all unique state values during the export scan, present them to the customer for lifecycle-stage mapping, and configure corresponding crm.stage records in Odoo before migration. Each stage is assigned to the relevant sales team via team_id. Unmapped state values are flagged and default to the first stage in the pipeline.

MetroLeads source_tags are string arrays on Lead records. We create crm.tag records in Odoo for each unique tag value before migration, then link tags to crm.lead records via crm.lead.tag_rel. Tags used for lead disposition (disposition_answered, etc.) are preserved as tags for filtering in Odoo's CRM pipeline view.

MetroLeads custom property values are keyed by internal property IDs (customer_id_070). We fetch the MetroLeads property schema first, build an ID-to-name mapping, create the corresponding custom fields in Odoo via Studio or metadata (x_fieldname__c naming convention), and populate them during import. Property types (text, number, date, dropdown) map to appropriate Odoo field types (char, float, date, selection).

MetroLeads Intellisearch is a scoring and saved-search layer that does not map 1:1 to Odoo. We export the raw Intellisearch configuration (saved search criteria, score weights) as a JSON file delivered alongside the migration. If the customer uses lead scoring, we map the score value to a custom integer field x_metro_intelliscore on crm.lead and recommend Odoo's Smart Search or a third-party scoring module for ongoing scoring.

MetroLeads Advanced Data Modules are tenant-specific data structures with per-organization field definitions. We export the module schema alongside records, create the corresponding custom models in Odoo (ir.model and ir.model.fields via XML-RPC), and map records to the new model. This step requires Odoo Developer mode or Studio access and is scoped as a separate configuration phase in the migration plan.

MetroLeads lead_group is a UUID reference grouping related leads across the platform. We export the UUID and map grouped leads to an Odoo crm.team (for sales team groupings) or a tag applied across all members of the group. The customer chooses the strategy during scoping based on whether lead_group represented a sales territory, campaign, or internal grouping.