Migrate from Lucep to Twenty CRM

Lucep Lead records map to Twenty CRM Contact. The Lucep lead capture timestamp, source channel (website, Facebook, form), routing assignment, and response timestamps migrate as Contact fields and activity log entries. We use email address as the deduplication key. If the customer uses a primary CRM alongside Lucep, we de-duplicate against existing Contact records before insert to avoid creating duplicates when migrating from both sources simultaneously.

Lucep Callback records (the click-to-call interaction) map to Twenty CRM Task records with a call-log structure. The callback timestamp, originating channel, assigned agent, and outcome (answered, missed, voicemailed) transfer as task fields. The timing chain from first touch to first conversation is preserved as a chronological activity entry against the Contact record. Disposition notes from the callback migrate as Task body text.

Lucep qualifies leads automatically via AI voice, WhatsApp, and SMS channels, producing a qualification score and status stored per lead in Lucep's field model. These map to a custom number field on Twenty CRM's Contact object. The customer's admin names and thresholds the field during workspace setup. We document the source field names from Lucep during discovery so the admin knows exactly which Lucep property maps to which Twenty field.

Lucep's routing rules assign leads to team members or queues based on custom algorithms — this is configuration, not data, and cannot be exported as structured records. We extract the current routing configuration during discovery, document every active rule (trigger conditions, target agent or queue, priority order) in a routing-rebuild specification, and hand it to the customer's admin for manual reimplementation in Twenty CRM's workspace settings. Routing is not migrated.

Lucep AI Voice Agent call transcripts and disposition data may not be fully accessible via the public API. During scoping we test API access to transcript endpoints. Where transcripts are available via API, they migrate as Note records linked to the Contact. Where transcripts are gated, we advise the customer to export manually from the Lucep dashboard before cutover and we handle the file import as a supplemental data load. Call duration and disposition migrate as Task fields in both cases.

Lucep ingests leads from Facebook Lead Ads via integration guides, mapping Facebook form field names to Lucep's internal field names. When migrating, we trace the field chain from Facebook form → Lucep → Twenty CRM and flag any Lucep fields that have no Twenty equivalent. Custom Facebook form fields that have no standard Lucep field to map into become custom fields on Twenty Contact, named to preserve their Facebook-origin meaning. The customer approves the field naming during scoping.

Lucep supports webhook-based lead distribution to external systems. These are platform settings, not data records, and cannot be migrated as active connections. We document every active webhook endpoint, payload structure, and trigger condition during discovery so the customer's admin can reconfigure them in Twenty CRM's workspace settings or via a developer tool that supports inbound webhooks. The handoff document includes the full webhook payload schema observed in Lucep.

Lucep assigns leads to users or teams. We export the user-to-lead assignment relationship and map it to Twenty CRM's workspace member model by email address. Lucep user records may not carry full profile data (role, department, phone); we flag any missing fields and map the available fields. If the customer's Twenty workspace is new, we provide a user provisioning list with the Lucep assignments so the admin can create matching workspace members before record import begins.

Lucep allows tagging and segmentation of leads. We extract tags as flat label strings and map them to Twenty CRM's Contact tag fields. If Twenty's tag model differs from Lucep's (for example, if Twenty uses a different character limit or delimiter convention), we document the transformation rule. Tags used for lead segmentation migrate as string arrays that the customer's admin can reassign in Twenty's tag management view.

Lucep syncs lead data bidirectionally with connected CRMs. When migrating out of Lucep, we account for which records may already exist in the customer's primary CRM and de-duplicate based on email address and external ID before writing to Twenty CRM. For teams running Lucep alongside a CRM already, we use the CRM's existing Contact records as the dedupe source rather than the Lucep record, preventing duplicate creation at migration time.