Migrate from EverPro to Odoo CRM

EverPro contacts map directly to Odoo res.partner records. The partner_id on each crm.lead resolves to this res.partner. If the EverPro contact has no company association, it lands as an individual partner with partner_latitude and partner_longitude preserved as custom fields in the Odoo database for future reference.

EverPro business accounts map to res.partner with company_type set to 'company'. Individual contacts associated with the company link via child_ids on the parent partner record. Odoo's commercial_partner_id field resolves the top-level commercial entity for reporting, and enables proper hierarchy traversal in Odoo.

EverPro service jobs do not have a direct Odoo CRM equivalent — they map to crm.lead with lead_type = 'opportunity' so the record enters the Odoo pipeline. The job name becomes crm.lead.name, and the job status maps to crm.lead.stage_id using a value_map per pipeline stage defined in Odoo.

EverPro loyalty data (points balance, tier name, enrollment date) has no native Odoo CRM equivalent. We create custom fields on res.partner — x_loyalty_tier, x_loyalty_points, x_loyalty_enrolled_date — and preserve the values as reference data. The loyalty program logic itself must be rebuilt in Odoo using the Loyalty app if Enterprise is the target.

EverPro logged service calls map to Odoo crm.phonecall records. The phonecall is linked to the corresponding crm.lead (the service job) via the crm_lead_id field. Call duration, subject, and outcome notes all map directly to crm.phonecall fields, including internal notes and call disposition codes.

EverPro technician assignments map to Odoo res.users records matched by email. The assigned technician becomes crm.lead.user_id (the lead owner). If the EverPro technician email has no matching Odoo user, the lead is assigned to a fallback owner flagged for admin review.

EverPro physical addresses map to Odoo res.partner street, street2, city, state_id, zip, and country_id fields. Odoo uses state_id as a many2one to res.country.state, so the EverPro state value is resolved by name match. Multi-address contacts are stored as child res.partner records.

EverPro equipment serial numbers and model references stored on service jobs migrate as custom_char fields on crm.lead (x_equipment_serial, x_equipment_model). If equipment should be tracked as a product in Odoo Inventory, we create product.product records and link them via x_equipment_product_id on the lead.

EverPro email logs on a service job migrate as crm.lead.message_ids in Odoo, preserving the original sender, timestamp, and body text. Odoo stores these as mail.message records with a many2one relation to crm.lead. These messages also retain any attachments and are searchable through Odoo's mail gateway.

EverPro contact owners resolve by email match to Odoo res.users. Unmatched owners are flagged in the pre-migration audit. The matched user becomes crm.lead.user_id — the record owner who controls access under Odoo's record rules, and determines visibility for downstream modules like Sales, Project, and Helpdesk.

EverPro ticket priority (Low, Normal, High, Urgent) maps to Odoo crm.lead.priority using a value_map. Odoo's priority field uses 1–3 stars by default, so the four EverPro values collapse to three Odoo levels: Urgent maps to 1 (highest), High to 2, Normal to 3, and Low is dropped or treated as stage-sequence priority.

EverPro referral source stored on a contact or job maps to crm.lead.source_id — a many2one to utm.source if Odoo's CRM UTMs are installed. Source name is matched by string lookup. Unknown sources are created as new utm.source records during migration.

EverPro scheduled service dates map to crm.lead.date_deadline. Odoo uses this field for pipeline甘特图 display and for automation triggers. If the EverPro job has both a scheduled date and a completed date, the completed date becomes a custom field x_service_completed_date on the lead.

EverPro internal notes attached to a service job that are not structured as calls or emails migrate to a custom_text field on crm.lead (x_internal_notes). Odoo's mail.message system handles threaded comments, but non-structured notes that predate Odoo adoption are consolidated into this field for audit continuity.

Any EverPro contact property not represented in the standard res.partner schema (preferred service window, referral code, anniversary date) migrates to custom fields on res.partner. We create each as a custom_char, custom_date, or custom_selection field depending on the EverPro field type, using Odoo Studio in Odoo Enterprise or direct PostgreSQL column addition in Odoo Community.