Migrate from Lucep to Odoo CRM

Lucep Lead records map directly to Odoo CRM Lead. Lucep fields including lead source channel, routing assignment, assigned agent, response timestamp, and qualification score migrate to Odoo Lead custom fields. Lucep's source-channel tracking (website form, Facebook Lead Ad, click-to-call) maps to Odoo's lead_medium_id. The response timestamp from Lucep's click-to-call interaction is preserved as a custom datetime field on the Odoo Lead for SLA audit. Email deduplication uses Lucep's email field as the match key.

Lucep Leads that represent established customer relationships or have been contacted more than twice split into Odoo CRM Contact records. The split rule is defined during scoping based on Lucep's qualification stage or callback count. Odoo Contact records are created with partner_id linked to an Account. The original Lucep lead identifier is preserved in a custom field lucep_lead_id__c for traceability.

Lucep Callback records — representing click-to-call interactions — map to Odoo CRM Phone Call records. The callback timestamp, originating channel (web, Facebook, SMS), assigned agent, and outcome (answered, missed, voicemailed) migrate to crm.phonecall fields. If the destination Odoo instance does not have the crm.phonecall model enabled, we create a custom activity type to store the same fields. Call disposition values from Lucep migrate as tags or a dedicated picklist field on the activity.

Lucep stores AI Voice Agent qualification scores and disposition status as per-lead custom properties. These migrate to Odoo custom fields on the CRM Lead object (x_lucep_score, x_lucep_disposition). Qualification status maps to a stage-based automation in Odoo CRM that advances the Lead from New to Qualified based on the imported score threshold. The customer defines the threshold value during scoping.

AI Voice Agent call outcomes (disposition, duration, outcome) from Lucep migrate to Odoo Phone Call records linked to the Lead or Contact. Call transcripts may not be fully accessible via the Lucep API; we test transcript endpoint availability during scoping. If transcripts are gated, we advise the customer to export them manually from the Lucep dashboard and we load them as Note records attached to the corresponding Phone Call or Lead.

Lucep ingests Facebook Lead Ads form submissions, mapping Facebook field names to Lucep's lead object. When migrating, we trace the field chain from Facebook form → Lucep → Odoo and flag any fields that lose meaning in translation, particularly custom Facebook form fields with no Lucep equivalent. Standard Facebook fields (name, email, phone, ad name, form name) map to Odoo Lead fields. The original Facebook ad name and form name are stored as custom fields on the Odoo Lead for attribution.

Lucep assigns leads to team members or queues. We export the user-to-lead assignment relationship and map it to Odoo Res Users via email match. Lucep team assignments map to Odoo Sales Teams (crm.team). Any Lucep user without a matching Odoo Res User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Lucep's routing rules assign leads to agents or queues based on custom algorithms. These are stored as platform configuration and do not export as structured records. We extract every active routing rule during discovery and produce a routing-rebuild specification that maps each Lucep rule to an Odoo Assign Round Robin, Load Balancer, or Odoo Studio automated action. The customer's admin or Odoo partner implements the routing logic in Odoo post-migration.

Lucep tags and lead segments are stored as flat string labels per lead. We extract all unique tag values from Lucep and map them to Odoo's mailing.tag model. Tags are attached to Leads and Contacts via ir.attachment records. If Odoo is using a different tagging model (Project tags, UTMs), the customer selects the target during scoping and we apply the chosen model during migration.

Lucep webhook endpoints and payload configurations are settings, not records. We document every active webhook endpoint (URL, HTTP method, payload fields) during discovery and deliver a webhook-rebuild specification so the customer's developer can reconfigure them in Odoo's Webhook module or via a custom Odoo Studio server action triggered on Lead creation.

Lucep tracks the number of callback requests per lead. We aggregate the callback count per lead and store it as a custom integer field (x_lucep_callback_count) on the Odoo CRM Lead. This field is used by the customer's admin to identify high-intent leads that may warrant priority routing in Odoo.

Lucep tracks the originating channel for each lead (website click-to-call, Facebook Lead Ad, SMS, WhatsApp, direct form). These map to Odoo UTM medium values, which Odoo creates automatically during migration if they do not already exist. The UTM source (Facebook, Google Ads, specific landing page) maps to utm.source. This preserves multi-channel attribution in Odoo's native reporting.