Migrate from Lucep to Nutshell

Lucep Lead records map to Nutshell People. The lead's name, email, phone, source channel (website, Facebook, form), routing assignment, and response timestamp migrate as fields on the Person record. We use email as the dedupe key. If Lucep stores a company name on the lead, we create or match a corresponding Nutshell Company record and link it to the Person via the People-Company relationship before inserting the Person.

Lucep Callback records (click-to-call interactions) map to Nutshell Task records with call-log metadata. We populate Task fields: Subject (callback from website, Facebook, etc.), Description (originating channel and lead source), Status (Completed for answered, Not Started for missed), and custom fields for disposition (answered, missed, voicemailed, Ringing No Response). ActivityDate is set to the original callback timestamp to preserve the timing chain. Parent Person lookup is resolved by email match.

Lucep Lead records that carry a company name or domain are exported as Lucep Company records if the customer has configured company capture. These map directly to Nutshell Company records using company name as the dedupe key. If a lead has no company data, we create the Person record first and flag any leads with company-like name fields that may warrant a separate Company record in Nutshell for the customer's admin to review.

Lucep stores qualification scores and qualification status (e.g., hot, warm, cold, unqualified) as custom lead properties. These map to Nutshell custom fields on the Person record (text or number type depending on the source field type). We create the custom field in Nutshell before migration, populate it from Lucep's qualification property, and document the original Lucep field name so the customer's admin can interpret the values post-migration.

Lucep's routing engine assigns inbound leads to specific agents or queues based on custom algorithms. The assigned agent and queue names are stored per lead. We extract these as custom fields on the Person record in Nutshell (routed_to_agent__c, routed_to_queue__c). Because routing rules are Lucep configuration and not data, we document the full routing rule set separately as a written specification for the customer's admin to reimplement in Nutshell workflows or assignment rules post-migration.

Lucep User records (agents and team members) map to Nutshell User records by email match. We export the user-to-lead assignment relationship from Lucep and resolve it to the corresponding Nutshell User. If a Lucep user has no matching Nutshell User at migration time, we hold those assignments in a reconciliation queue and flag them for manual provisioning before the Person import phase completes.

Lucep allows tagging and segmentation of leads. Tags migrate as flat string labels and are stored in Nutshell's Tag field on the Person record. If the customer used Lucep tags for lead scoring tiers or source attribution, we document the tag taxonomy separately so the admin can decide whether to recreate these as Nutshell custom fields, lists, or a combination of both.

AI Voice Agent interactions generate call disposition and qualification outcome data per lead. The disposition (qualified, not interested, callback requested, no answer) and any structured data extracted during the AI voice call migrate as custom fields on the linked Nutshell Person record. Call transcripts may not be fully accessible via the Lucep public API — we test API access during scoping, and if transcripts are gated, we advise the customer to export them manually from the Lucep dashboard before cutover and handle the file as a supplemental data load.