Migrate from BenchmarkONE to Odoo CRM

BenchmarkONE Contact records map to Odoo res.partner with type='contact'. Standard fields (name, email, phone, website, street, city, state, zip, country) map 1:1 to their Odoo counterparts. The BenchmarkONE Temperature field (Cold/Warm/Hot) maps to a custom integer field temperature_score__c where 0=Cold, 1=Warm, 2=Hot. Contact Status maps to partner.state_id (custom stage field). Assigned Sales Rep maps to Odoo User (user_id) via email lookup. Tags stored as a comma-separated list in BenchmarkONE become Odoo Tags (mailing.mailing contact) or a many2many tag field on res.partner, depending on how the customer intends to use them post-migration.

BenchmarkONE Company records map to Odoo res.partner with type='company' and is_company=True. The company record is created first, then BenchmarkONE Contacts linked to that company receive the parent_id pointing to the company Partner record. Website, Industry, and custom company fields migrate as fields on the company Partner record. Address fields on Company migrate as address fields on the company Partner, and contact addresses on related Contact records reference the company as parent_id.

BenchmarkONE Deals map to Odoo crm.lead records of type='opportunity'. The Deal name becomes the Opportunity subject, the deal amount maps to Odoo's expected_revenue or amount_currency fields, and the deal probability maps to probability (with stage-based defaults). We configure an Odoo crm.team pipeline with stages that match the BenchmarkONE pipeline stages before migration, so stage names and probabilities are pre-aligned. Deal custom fields migrate as custom fields on crm.lead via Odoo Studio.

Each BenchmarkONE Deal Pipeline stage becomes an Odoo crm.stage record within the crm.lead model. Stage order, name, and probability percentage migrate directly. The Odoo pipeline uses crm.team to scope which stages are visible to which sales team, which allows multi-team setups that BenchmarkONE's single pipeline model does not support.

BenchmarkONE Tasks map to Odoo project.task records linked via project_id (a shared Project record serving as the task container). Standard fields (subject, date_deadline, user_id, stage_id, priority, description) map directly. Tasks associated with a specific Contact or Deal receive a res_model='crm.lead' and res_id pointing to the migrated Opportunity record. Tasks without a parent record are attached to the default project container.

BenchmarkONE tags are free-form string labels applied to contacts for segmentation. We implement them as Odoo mailing.contact tags (mailing.mailing contact model) if the customer intends to use Odoo's Email Marketing app for campaign audience segmentation. Alternatively, we create a custom many2many tag field (benchmarkone_tags) on res.partner. The customer chooses during scoping; tags used primarily for CRM segmentation (not email marketing) typically use the custom field approach to avoid unintended mailing list inclusion.

BenchmarkONE custom fields on Contact, Company, and Deal records map to Odoo custom fields on res.partner and crm.lead via Odoo Studio. We audit field types during scoping (text, number, date, dropdown) and create matching field types in Odoo before migration begins. Dropdown fields in BenchmarkONE become Odoo selection fields; multi-select fields become many2many fields pointing to a dedicated tag model. Date and datetime fields require timezone normalization to UTC before Odoo import. This is the highest-risk schema step because mismatched field types silently reject or corrupt imported values.

BenchmarkONE stores email campaign metadata (name, send date, audience count, template name) and aggregate stats (opens, clicks, bounces, unsubscribes). We map these to Odoo crm.activity records linked to the target Partner records, and aggregate stats migrate as mail.mail.statistics records on the Partner. Individual email event logs (per-recipient open and click timestamps) require separate extraction from BenchmarkONE and are stored as notes or activity descriptions in Odoo because Odoo's standard CRM does not include a per-event email analytics table.

BenchmarkONE stores individual email interactions logged against contacts as email activity records. These migrate as Odoo mail.message records with model='res.partner' and res_id pointing to the target Partner. Body content, timestamp, and direction (inbound/outbound) migrate directly. Odoo's Discuss app surfaces these as conversation threads on the Partner record.

BenchmarkONE stores social profile URLs (LinkedIn, Twitter, Facebook, Instagram) as fields on the Contact record. These map to Odoo res.partner social fields (social_twitter, social_linkedin, social_facebook, social_instagram). Odoo surfaces these in the Partner form view under a Social Media section.

BenchmarkONE Lead Source (website, referral, event, paid ad, organic search, other) maps to a selection field or char field source_id on Odoo crm.lead. We preserve the original label so that pipeline reports can be filtered by acquisition channel at destination. If the customer uses UTM-based attribution, we map the utm.source, utm.medium, and utm.campaign from BenchmarkONE to Odoo's utm.lead.mixin fields.

BenchmarkONE assigns users (sales reps) as owners to Contacts, Companies, Deals, and Tasks via an Assigned Sales Rep field. We resolve each distinct owner by email against the Odoo res.users table. Any BenchmarkONE Owner without a matching Odoo User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Owner ID resolution is a blocking dependency for Contacts and Deals because Odoo requires a valid user_id on crm.lead and res.partner.

BenchmarkONE automations are triggered by form submissions, link clicks, website visits, tag changes, or purchases. These are platform-specific workflow constructs that do not export as data. We audit each active automation during discovery (trigger type, conditions, actions) and deliver a written inventory mapping each automation to an Odoo ir.actions.server, base.module.record rule, or mail.activity.type configuration. The customer or an Odoo implementation partner rebuilds them in Odoo's automation framework post-migration. This is documented reconstruction, not a data migration.