Migrate from Lucep to Salesforce Sales Cloud

Lucep Lead records map directly to Salesforce Lead. Lucep fields including first_name, last_name, email, phone, source_channel, routing_assignment, response_timestamp, qualification_score, and qualification_status map to their Salesforce Lead equivalents. Facebook Lead Ads fields that passed through Lucep are preserved with a lucep_source__c custom field recording the original channel. We de-duplicate against any existing Salesforce Leads by email address before insert.

Lucep Callback records (the click-to-call interaction) map to Salesforce Task with TaskSubtype = Call. Lucep callback_timestamp, originating_channel, assigned_agent, and outcome (answered, missed, voicemailed) migrate to Salesforce CallDurationInSeconds, custom outcome fields, and ActivityDate preserving the original timestamp chain. The Task WhoId points to the resolved Salesforce Lead.

AI Voice Agent conversations generate call transcripts and disposition data stored in Lucep. We test API access to transcript endpoints during scoping. If transcripts are accessible, they migrate as Salesforce Task records with CallDisposition populated and the transcript stored as a ContentDocument linked via ContentDocumentLink to the parent Task or Lead. If transcripts are gated, we advise the customer to export them manually from the Lucep dashboard and we handle the file import as a supplemental data load.

Lucep's qualification score and qualification status per lead migrate to custom Salesforce fields (lucep_qualification_score__c, lucep_qualification_status__c) on Lead. These are flat numeric and picklist fields — Lucep's internal qualification algorithm logic does not migrate because it is configuration, not data. We document the qualification score thresholds as a written handoff so the customer's admin can rebuild qualification rules in Salesforce Flow if needed.

Lucep's routing rules assign leads to team members or queues based on custom algorithms. These are platform settings, not records, and cannot be exported via API. We document every active routing rule during discovery (assignment criteria, target agent or queue, priority weighting, Ringing No Response retry behavior) as a written routing-rebuild specification. The customer's admin or a Salesforce partner re-implements the logic in Salesforce Omni-Channel or Flow-based assignment rules post-migration.

Lucep assigns leads to users or teams. We export the user-to-lead assignment relationship and map it to Salesforce Lead OwnerId by resolving Lucep user email to Salesforce User email. Lucep user records may not carry full profile data — we extract what is available and flag missing Salesforce User matches in a reconciliation queue. The customer's admin provisions any missing Salesforce Users before record import resumes.

Lucep tags and lead segments migrate as a custom multi-select picklist field (lucep_tags__c) on Salesforce Lead. Tags are extracted as flat label strings. If the destination org uses a different tagging model (for example, Topics or Campaign membership), the customer chooses the strategy during scoping. We do not automatically map Lucep tags to Salesforce Campaigns because that requires a business decision about campaign membership criteria.

Lucep ingests leads from Facebook Lead Ads via integration. The Facebook form field names are non-standard and map to Lucep's internal field names before reaching the destination CRM. We trace the field chain from Facebook form field name → Lucep field name → Salesforce field name during mapping design and flag any Lucep fields with no Salesforce equivalent as lucep_custom_field__c entries. Custom Facebook form fields without Lucep equivalents are documented for manual review post-migration.

Lucep supports webhook-based lead distribution to external systems. Webhook configurations are platform settings, not data, and do not migrate. We document the active webhook endpoints, payloads, and authentication method during discovery as a written specification. The customer's admin reconfigures these at the destination. If Salesforce acts as the webhook target post-migration, we recommend Salesforce Flow's HTTP action or a middleware layer (MuleSoft, Workato) rather than raw webhook endpoints.

Lucep captures the timing chain from first touch (web form submission, Facebook Lead Ad) through routing assignment to first conversation (callback answered). We preserve this as a sequence of Salesforce Task records with TaskSubtype = Log a Call, each timestamped with the original Lucep event time. The SLA metric (seconds from first touch to first response) is preserved as a custom field lucep_response_sla_seconds__c on the Lead for post-migration reporting.

Lucep syncs bidirectionally with connected CRMs. When migrating out of Lucep, we check whether records may already exist in the destination Salesforce org (for example, if Lucep was previously integrated with this Salesforce org). We de-duplicate based on email address and external_id before insert, flagging any Lucep records that find a match as updates rather than creates.

If Lucep stores company or organization data associated with a Lead (for example, via Facebook Lead Ads company_name field), those records map to Salesforce Account. The Account is created before the Lead import so that AccountId can be populated on the Lead if the customer uses Account-based lead routing. Company domain mapping to Account Website follows standard field mapping.