Migrate from Lucep to Freshsales

Lucep Leads carry the full lead capture chain: source channel, routing assignment, response timestamp, qualification score, and any Facebook form field data. We map these to Freshsales Contacts. If the customer maintains a distinction between inbound prospects (unqualified) and qualified contacts, we map Lucep Leads with qualification_status = unqualified to Freshsales Lead and qualified Leads to Contact, using Freshsales's native conversion workflow to create the Account relationship. All Lucep custom lead fields require pre-created Freshsales custom fields before import.

Lucep Callback Request records capture the click-to-call interaction: originating channel (website widget, Facebook Lead Ad, SMS), assigned agent, callback timestamp, and outcome (answered, missed, voicemailed). We map these to Freshsales Task records with TaskSubtype set to Call. Call duration, disposition, and recording URL preserve in custom Task fields. The original callback timestamp becomes ActivityDate so the Freshsales activity timeline shows the full lead-response timing chain.

Lucep routing rules assign leads to team members or queues based on custom algorithms and qualification outcomes. These are platform configuration, not data records, and cannot be exported as structured rows. We document every active routing rule during discovery, capture its conditions and assignments, and produce a routing-rebuild specification that maps each rule to a Freshsales Workflow or auto-assignment rule. The customer's Freshsales admin implements these post-migration.

AI Voice Agent calls generate call transcripts and disposition data in Lucep. Transcript availability via API is not confirmed in Lucep's public documentation. During scoping, we test API access to transcript endpoints. If accessible, transcripts migrate as Freshsales Note records linked to the corresponding call Task. If gated, we advise the customer to export transcripts from the Lucep dashboard manually before cutover and handle the file as a supplemental data load.

Lucep ingests leads from Facebook Lead Ads via integration guides, mapping Facebook form field names to Lucep's internal lead fields. These Facebook field names are often non-intuitive (e.g., fdform_1234567_data_first_name). We trace the field chain from Facebook form through Lucep to Freshsales, flag any Lucep custom fields with no Freshsales equivalent, and recommend Freshsales custom field creation for any Facebook-sourced data that must be preserved.

Lucep stores a qualification score per lead from AI voice, WhatsApp, and SMS qualification interactions. We map this as a custom integer field on Freshsales Contact. If the customer's Freshsales plan includes Freddy AI, we configure Freddy Contact Scoring separately post-migration rather than carrying over Lucep's proprietary scoring model, since scoring algorithms are configuration and not transferable data.

Lucep assigns leads to users or teams. We export the user-to-lead assignment relationship and map it to Freshsales User via email match. Lucep user records may not carry full profile data (role, department). Any Lucep user without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Lucep supports tagging and segmentation of leads. Tags export as flat label strings. We map them to Freshsales Contact tags if the customer uses the Tags feature on their plan, or to a multi-select picklist custom field if the tagging model requires structured segmentation. The choice between tags and custom field is made during scoping based on the customer's segmentation use case.