Migrate from Lucep to Mailchimp

Lucep Lead records map to Mailchimp contacts in the primary audience. We extract first name, last name, email address, phone number, and lead source channel (web widget, Facebook Lead Ads, manual entry) from Lucep and map them to Mailchimp FNAME, LNAME, EMAIL, PHONE merge fields and a custom LUCEP_SOURCE merge field. Email address serves as the dedupe key. We flag any Lucep leads without a valid email address for the customer's review before import; Mailchimp requires a valid email for audience membership.

Lucep Callback Request records (timestamp, originating channel, assigned agent, outcome) do not have a native Mailchimp equivalent because Mailchimp tracks email engagement, not call activity. We map the callback outcome (answered, missed, voicemailed) to a LUCEP_CALLBACK_STATUS merge field, and the assigned agent name to a LUCEP_AGENT tag on the contact record. The customer should treat callback data as contact enrichment rather than a timeline of activities.

Lucep stores qualification scores and qualification status per lead across AI voice, WhatsApp, and SMS channels. We extract these as LUCEP_QUAL_STATUS and LUCEP_QUAL_SCORE custom merge fields on the Mailchimp contact. Mailchimp does not have a scoring model, so these values are informational for the customer's sales team to reference during outreach sequencing; they do not trigger automations.

Lucep tags and lead segments map directly to Mailchimp tags on the contact record. Tags are flat label strings in Lucep and map to Mailchimp tags without transformation. We preserve the full tag set per contact so that the customer can rebuild Mailchimp segments from the imported tag inventory post-migration.

Lucep user-to-lead assignment relationships map to a LUCEP_OWNER merge field on the Mailchimp contact. Lucep user records may not carry full profile information (name, email) depending on how the account is configured. We flag any Lucep leads assigned to users that cannot be resolved to a name or email for manual assignment review.

Lucep ingests leads from Facebook Lead Ads via integration, mapping Facebook form field names to Lucep's lead object fields. We trace the field chain from the original Facebook form through Lucep to Mailchimp merge fields, preserving the Facebook ad name, campaign name, and form name in LUCEP_FB_AD, LUCEP_FB_CAMPAIGN, and LUCEP_FB_FORM merge fields. Custom Facebook form fields that have no Lucep equivalent are flagged as unmapped and documented for the customer to evaluate whether they should be added as merge fields.

Lucep routing rules are platform configuration, not contact data, and cannot be exported as records. We document every active routing rule during discovery (queue assignment logic, SLA thresholds, Ringing No Response retry settings) and produce a routing-rebuild specification so the customer can replicate the logic in Mailchimp using tags, segments, and automation triggers if the underlying business process requires it.

AI Voice Agent call transcripts and disposition data may not be fully accessible via the Lucep public API. We test API access during scoping. If transcript endpoints are gated or unavailable, we advise the customer to export transcripts manually from the Lucep dashboard before cutover. The transcript file can be attached to the contact record as a note or stored externally for reference; Mailchimp does not have a native transcript storage object.