Migrate from Flash Lead Sales to Mailchimp

Flash Lead Sales Leads migrate as Members in a Mailchimp Audience. Email address serves as the primary key for deduplication. Standard merge fields (FNAME, LNAME, EMAIL, PHONE, COMPANY) map from Flash Lead Sales lead fields directly. The Mailchimp Member status is set to subscribed by default; if the customer has unsubscribed records in Flash Lead Sales, we import those as unsubscribed in Mailchimp to preserve suppression status and protect deliverability.

Flash Lead Sales Contacts merge into the same Mailchimp Audience as Leads using email address as the dedupe key. Where a Contact and a Lead share the same email (indicating a converted lead), we update the existing Member rather than create a duplicate. Contact-specific fields like purchase history and location migrate as custom Merge Fields in Mailchimp (e.g., PURCHHIST, LOCATION).

Flash Lead Sales tags (applied without limit to Lead and Contact records) migrate to Mailchimp Tags. Tags are preserved as comma-separated values on each record during export and applied as Mailchimp Tags during import via the Mailchimp API tag endpoint. Mailchimp's tag model is flat (no hierarchical tag groups), so nested Flash Lead Sales tag categories are flattened and prefixed with the original group name for disambiguation.

Flash Lead Sales Lead Source (Facebook, Instagram, Referral, Purchased List, etc.) has two migration paths depending on the customer's segmentation strategy. We create a MAILSOURCE merge field and set the source label as its value for all Members from that source. Alternatively, if the customer prefers tag-based segmentation, we create a Mailchimp Tag for each source value (e.g., Tag: Source-Facebook). The customer chooses during scoping; both approaches are documented.

Flash Lead Sales Company records (company name, domain, location) map to the standard Mailchimp COMPANY merge field on each Member. Where a Lead or Contact is associated with a Company record, we resolve the company name at migration time and populate the COMPANY field. Flash Lead Sales does not store a formal Account object, so company-level data is denormalized per contact; we do not create a separate Mailchimp entity for Company records.

Flash Lead Sales Team Members (with role-based hierarchy) do not have a direct Mailchimp equivalent because Mailchimp has no per-record ownership model. We extract team member names and emails for two purposes: if the team member email matches a contact email, they appear as a Member in the Audience; if the customer wants to assign responsibility for Audience management, we document Mailchimp Admin role assignments as a manual post-migration step. Role hierarchy (manager, owner, rep) is noted in the migration report for the customer's admin to translate into Mailchimp permission settings.

Flash Lead Sales custom pipeline stages (Lead, Qualified, Proposal, Negotiation, etc.) have no Mailchimp equivalent because Mailchimp is not a CRM and does not track deal stage progression. We capture the current pipeline stage on each Lead as a Mailchimp Tag (e.g., Tag: Stage-Proposal) or as a custom merge field STAGE__C for informational purposes only. The customer should understand this represents a snapshot at migration time and does not constitute active pipeline tracking in Mailchimp.

Flash Lead Sales stores custom lead and contact properties beyond the standard fields. We extract all custom properties during discovery and create equivalent Merge Fields in Mailchimp (up to Mailchimp's 40-merge-field limit per Audience). Field types are mapped: text properties to text merge fields, date properties to date merge fields, numeric properties to number merge fields. Properties exceeding the merge field limit are flagged during scoping and migrated as Tags or noted for the customer to evaluate for prioritization.

Flash Lead Sales Pro invoice records (amount, status, related deal) have no Mailchimp equivalent. Mailchimp does not store transactional or financial records. We export invoice data as a supplementary CSV and attach it to the migration report for the customer's finance or operations team to handle separately, either in an accounting system or as a manual reference document.

Flash Lead Sales Facebook Messenger and Instagram DM threads export as flat text conversation logs attached to the contact record. Mailchimp has no conversation or messaging object model. We attach the full conversation log text as a note within the Member record (stored as a plain-text string in a custom Merge Field MESSAGELOG__C) so that the conversation context is present on the contact record even though it cannot be structured as threaded messages. Thread metadata (timestamps, branching, read status) is not preserved in the export.