Migrate from Lucep to Microsoft Dynamics 365 Sales

Lucep Lead records represent the primary data object — capture event, source channel, routing assignment, response timestamp, and qualification score are all stored per lead. We map unqualified Lucep Leads (where qualification status is pending or initial) to Dynamics 365 Lead. Qualified Leads with a confirmed contact name, company, and email map to Dynamics 365 Contact, with Account resolved by domain lookup or manual matching. The original Lucep lead ID and response SLA timestamp migrate as custom fields on both Lead and Contact for audit trail and reporting continuity.

Callback records store the click-to-call interaction: originating channel (website widget, Facebook Lead Ad, SMS, WhatsApp), assigned agent, callback timestamp, and outcome (answered, missed, voicemailed). We map these to Dynamics 365 Task records with TaskSubtype=Call. Call duration, disposition, and originating URL migrate to custom Task fields. ActivityDate is set to the original Lucep callback timestamp to preserve the response-time chain that Lucep customers track as a core SLA metric.

Lucep qualifies leads across AI voice, WhatsApp, and SMS channels, storing a qualification score and status per lead. These migrate as custom fields on Dynamics 365 Lead (leadscore__c, qualificationstatus__c). If the destination is Sales Enterprise or Premium, we map to the native msdyn_leadhealthscore field where available. Custom Lucep field names are preserved as Dynamics custom fields with API names matched to the source field label.

Lucep's routing rules assign inbound leads to team members or queues based on custom algorithms. These are platform configuration, not record data, and cannot be exported via API. During discovery we document every active routing rule (trigger condition, assignment target, priority, fallback behavior) and produce a routing-rebuild specification so the customer's Dynamics 365 admin can implement equivalent assignment rules in Power Automate or Dynamics native assignment rule sets post-migration.

AI Voice Agent conversations generate call transcripts and disposition data stored in Lucep. These may not be fully accessible via the public API. We test API access during scoping. Where transcript endpoints are gated or unavailable, we advise the customer to export transcripts manually from the Lucep dashboard before cutover and handle the file import as a supplemental data load. Disposition data that is API-accessible migrates to a custom field on the related Task record.

Lucep integrates bidirectionally with Dynamics 365 Sales, Salesforce, Zoho, and LeadSquared. Where Lucep has been used as an overlay on top of an existing Dynamics 365 deployment, some records may already exist in the destination. We de-duplicate based on email address and external CRM ID, keeping the most recently updated version. Records unique to Lucep migrate in full. Records that exist in both systems are merged with Lucep's additional data fields overlaid.

Lucep ingests leads from Facebook Lead Ads, mapping Facebook form field names to Lucep's internal lead object. The Facebook field names are often non-standard and the Lucep intermediate mapping may obscure meaning. We trace the chain from Facebook form field to Lucep field to Dynamics 365 target field, flagging any Lucep fields that have no Dynamics equivalent, particularly custom Facebook form fields. The original Facebook form ID and ad ID are preserved as custom fields for attribution reporting.

Lucep assigns leads to users or teams. We export the user-to-lead assignment relationship and map it to Dynamics 365 OwnerId on the Lead or Contact. Lucep user records may not carry full profile data (title, department, phone), so we match by email against the destination Dynamics 365 User table and flag any Lucep assignee without a matching User for admin provisioning before migration.

Lucep allows tagging and segmentation of leads. Tags migrate as flat label strings to a Dynamics 365 custom field. If the customer uses Lucep's segment feature for lead routing or qualification routing, we map segments to a custom Option Set on Lead with the Lucep segment label preserved as the Option Set label and the API value preserved as the integer value.

Lucep supports webhook-based lead distribution to external systems. These webhook configurations are platform settings, not record data. We document each webhook endpoint URL, HTTP method, payload structure, and trigger condition during discovery and deliver the specification for reconfiguration in Dynamics 365 Power Automate or Azure Logic Apps post-migration. Webhook payloads that reference Lucep-specific field IDs are re-mapped to Dynamics 365 field logical names.