Migrate from LeadSmart Channel Cloud to Mailchimp

LeadSmart Contact records map 1:1 to Mailchimp audience members. We migrate standard fields: First Name, Last Name, Email (required), Phone, Mailing Address, and Title. Email address serves as the dedupe key. Custom fields on LeadSmart Contacts migrate as Mailchimp merge fields (text, number, date, or dropdown based on field type). Email opt-in status from LeadSmart (HasOptedOutOfEmail equivalent) migrates to the Mailchimp marketing permissions fields. Contacts without email addresses are held in a reconciliation queue because Mailchimp requires a valid email for audience membership.

LeadSmart Lead records map to Mailchimp audience members using the same field mapping as Contacts. We preserve Lead Status as a text merge field on the Mailchimp contact so the customer's team can segment unconverted leads separately in Mailchimp. We do not convert Leads to Contacts in Mailchimp because Mailchimp has no lead qualification workflow.

LeadSmart Account records (representing manufacturers, distributors, and dealers) have no direct Mailchimp equivalent. We extract the Account Name and Industry and migrate them as text merge fields on each related Contact's Mailchimp audience member record. Parent-account hierarchy (manufacturer-distributor-dealer relationships) does not migrate because Mailchimp has no account object or hierarchical contact model.

LeadSmart Opportunity records have no Mailchimp equivalent. Mailchimp is an email marketing platform, not a sales pipeline tool. Opportunity stages, deal amounts, probability percentages, and close dates are CRM-specific and cannot be represented as Mailchimp contacts, tags, or merge fields without losing meaning. We document every Opportunity record in a supplemental export CSV for the customer's records.

LeadSmart Partner Portal external partner records (linking internal Accounts to reps, brokers, dealers, and distributors) represent channel relationship roles that Mailchimp cannot model natively. We offer two options during scoping: migrate partner role data as text merge fields (e.g., ROLE: Dealer, ROLE: Sales Agent) on the related Contact, or exclude partner relationship data and tag the Contact with a segmentation label for the customer's manual list segmentation in Mailchimp. The customer's team chooses the strategy before migration.

LeadSmart Marketing Campaigns map to Mailchimp Campaigns only if the campaigns include email send history. We migrate campaign name, type, and status. Actual email content (templates, body copy, images) migrates as Mailchimp templates if the customer provides export files; otherwise we document the campaign names for manual template rebuild. Campaign Member status history (subscribed, unsubscribed, bounced) migrates to Mailchimp contact activity records for attribution analysis.

LeadSmart Activity records (calls, emails, meetings, tasks) are CRM engagement history tied to Salesforce's Activity object model. Mailchimp has no activity timeline, call log, or meeting record. We do not migrate activity history. We deliver a written summary of total activity counts by type and by contact for the customer's reference. Email tracking events (opens, clicks) in LeadSmart that originate from email sends migrate to Mailchimp's contact activity record as the platform of record for email engagement data.

LeadSmart Genius Feed AI-generated customer issue and growth opportunity records are stored in a proprietary format tied to the platform's recommendation engine. Mailchimp has no equivalent AI insight object. These records do not migrate. We document the existence of Genius Feed records in the pre-migration scope report and obtain customer sign-off confirming exclusion before migration begins.

LeadSmart Genius GPT stores sales strategy recommendations in a proprietary format tied to the internal recommendation engine. These records are not portable and have no equivalent in Mailchimp's feature set. We document Genius GPT record counts in the pre-migration scope and confirm exclusion with the customer before migration.

LeadSmart User records (sales reps, admins, partner portal users) represent internal CRM users with login credentials and role assignments. Mailchimp uses a workspace and account model with roles (Admin, Manager, Author, Viewer) that does not correspond to Salesforce User records. We do not migrate User records. The customer's Mailchimp account is provisioned separately with appropriate roles assigned by the Mailchimp admin.