Migrate from AgentLocator to Odoo CRM

AgentLocator leads map directly to Odoo crm.lead records. The crm.lead model handles both raw leads and opportunities — Odoo determines type by stage (unqualified = Lead; qualified with probability > 0 = Opportunity). We preserve the original create date as create_date and write the AgentLocator source system ID into a custom x_source_id char field for traceability.

AgentLocator contacts map to Odoo res.partner with partner_type='contact'. Odoo combines contacts and companies in one model; we set the contact as an individual (is_company=False) and attach it to a parent company partner record when AgentLocator provides a company association. During migration, we also transfer phone numbers, email addresses, job titles, and any custom fields defined on the contact object to corresponding res.partner fields.

AgentLocator company records map to res.partner with is_company=True. Odoo stores company-level fields (industry, website, employee count) on the partner record directly rather than a separate object. We map company name to partner_id.name, domain to website, and industry to industry_id lookup.

Each AgentLocator pipeline stage value maps to a corresponding crm.stage name within the target crm.team. Odoo stages are scoped per team and have a sequence order, probability, and is_won/is_lost flags. We map stage names value-by-value and set probability and stage-type flags from Odoo's default conventions unless your team specifies otherwise.

AgentLocator deals with a closedate and amount map to Odoo crm.lead records in opportunity mode. We set the lead_id to the migrated opportunity, write the deal name as crm.lead name, amount as planned_revenue, and closedate as date_deadline. Stage maps via the pipeline-stage value_mapping described above.

AgentLocator logged tasks (calls, emails, follow-ups) map to Odoo crm.activity records linked to the crm.lead. The activity type (call, email, meeting) maps to crm.activity.activity_type_id (phonecall, email, meeting). Original timestamps and owner email are preserved for audit continuity. We also transfer any task descriptions or notes attached to the activity record into the crm.activity note field.

AgentLocator notes on leads or contacts map to Odoo mail.message records with message_type='comment'. The note body populates the body field. Odoo renders mail.message records inline in the crm.lead and res.partner chatter views so notes appear alongside other activities. This ensures that historical note content remains accessible within the migrated records and maintains the full context of prior communications.

AgentLocator custom fields on leads and contacts require Odoo custom fields created via Settings > Technical > Models > Fields before migration. We create ir.model.fields with matching field types (char, selection, text, float, date, datetime) and then populate the data during migration. The field__c naming convention applies in Odoo Community; Odoo Studio uses a GUI label.

AgentLocator file attachments on leads or contacts re-upload to Odoo ir.attachment records. We download the file from AgentLocator's export, then POST it to Odoo's /web/binary/attachment API with the res_model and res_id linking to the migrated crm.lead or res.partner record. The original filename, MIME type, and file size are preserved in Odoo's ir.attachment fields to maintain document integrity and facilitate later retrieval.

AgentLocator owner assignments resolve by email match to Odoo res.users records. We query res.users for matching login email; unmatched owners are flagged pre-migration and either invited to Odoo first or assigned to a fallback Odoo user (admin by default). No record lands without a valid Odoo user owner_id.

AgentLocator tags on leads map to Odoo crm.tag records. Tags are stored as a many2many relation on crm.lead (tag_ids). We map tag names verbatim and create any missing tags in Odoo during migration. Each tag record includes the tag name and an optional color index for visual distinction in Odoo's kanban view.

AgentLocator saved filters for lead segmentation do not have a direct Odoo equivalent. Odoo's ir.filters model stores saved filter definitions, but AgentLocator's filter logic (e.g., by lead source, tag, pipeline stage combinations) must be manually recreated as Odoo filters or domain expressions after migration.