Migrate from Agent Legend to Odoo CRM

Agent Legend contacts map directly to Odoo res.partner records. Odoo distinguishes individuals from companies via the is_company flag — contacts without a company association in Agent Legend land as individual partner records. We set is_company=False and preserve the Agent Legend contact name split across name, firstname, and lastname fields. Partner addresses, phone numbers, and email map 1:1 to Odoo partner contact fields.

Agent Legend Lily AI lead scores (0–100 scale using 1,600+ third-party data points) have no native Odoo equivalent. FlitStack creates a float field on crm.lead called agent_legend_lily_score__c, preserving the original numeric score. Odoo admins can display this field in list views or integrate it into Odoo's built-in probability-based lead scoring for combined ranking.

Agent Legend campaigns map to Odoo crm.campaign records, preserving campaign name, description, start and end dates. Odoo campaigns support utm.source tracking, email marketing integration, and child campaigns. Campaign membership — which Agent Legend tracks as a per-contact property — maps to a many2many relation on the contact's partner record linking to crm.campaign.

Agent Legend tracks which campaigns a contact belongs to as a property on the contact record. Odoo has no per-contact campaign membership property — instead, we create a many2many relation on res.partner linking to crm.campaign. Each Agent Legend campaign a contact belongs to becomes a link in this relation. Odoo campaign reporting then aggregates partner records by campaign.

Agent Legend lead sources (Inbound Call, Referral, Zillow, Realtor.com, etc.) map to Odoo utm.source records when Odoo Marketing is installed. If only CRM is installed, we create tags on res.partner for each unique source value. We build a value map during the audit phase mapping each Agent Legend source string to its corresponding Odoo utm.source or tag name.

Agent Legend logged calls map to Odoo crm.activity records with activity_type_id set to the Call activity type. Odoo stores call notes in the activity's note field, the contact as res.partner, and the responsible user as res.users — owner resolution handled via email match. Original call date and duration preserved in activity_date_deadline and Odoo's duration field.

Agent Legend email records map to Odoo crm.activity with activity_type_id set to Email. Subject, body content, and timestamp migrate to the activity record. Odoo's mail.message threading attaches to the partner record. Original send date preserved as activity_date_deadline or a custom Created_Date__c field if the email timestamp needs to survive past the deadline field.

Agent Legend scheduled meetings map to Odoo calendar.event records. Event subject, start_datetime, stop_datetime, and location migrate directly. The meeting is linked to the relevant res.partner records as attendees. Owner attribution preserved via res.users match. If Odoo Calendar module is not installed, meetings fall back to crm.activity with a Meeting activity type.

Agent Legend notes map to Odoo ir_attachment records with res_model=res.partner and res_id pointing to the partner record. Rich-text formatting from Agent Legend converts to HTML within Odoo's note field. Original create date and author preserved as ir_attachment create_date and create_uid fields. All attachments on contact, company, and deal records migrate as ir_attachment with the appropriate res_model and res_id values.

Agent Legend custom properties (fields your team has configured beyond standard contact fields) migrate to Odoo custom fields. In Odoo, custom fields are created via Settings > Technical > Database Structure > Models, selecting the target model (res.partner, crm.lead, etc.) and field type. Agent Legend selection fields map to Odoo selection fields; multi-selection fields require a custom module using x_model_fields since Odoo does not natively support many2many tags without custom development.

Agent Legend company records map to Odoo res.partner with is_company=True, distinguishing them from individual contacts. Company name, website, industry classification, employee count, and annual revenue map to their Odoo counterparts. Agent Legend contacts linked to a company receive Odoo's parent_id pointing to the company partner record, establishing the contact hierarchy Odoo expects.

Agent Legend deals map to Odoo crm.lead records with type=opportunity. Deal name, expected revenue (amount), stage, probability, expected close date, and responsible user migrate to Odoo's crm.lead fields. Agent Legend pipeline stages map to crm.stage records within each crm.team — stage IDs must be recorded during the Odoo setup phase before migration, as stage assignment is by database ID rather than name.