Migrate from Espresso Agent to Mailchimp

Every Espresso Agent contact maps to one Mailchimp audience member. The contact's email address is the primary key for de-duplication. FlitStack uses scoped read access to export the full contact record including all custom property fields before writing to Mailchimp.

Espresso Agent stores property address as a linked object with multiple components. Mailchimp contacts have no native property object — FlitStack decomposes the address into four individual merge fields (PROPADDR, PROPCITY, PROPSTATE, PROPZIP) so each can be used independently in segments and personalization tokens.

Lead type is Espresso Agent's most differentiating field. FlitStack maps each type to a corresponding Mailchimp tag within a 'LeadSource' tag category: FSBO → 'Lead: FSBO', Expired → 'Lead: Expired', Preforeclosure → 'Lead: Preforeclosure', FRBO → 'Lead: FRBO'. Tag category structure is preserved for segment filtering.

Mailchimp has no native lead-status concept. FlitStack creates a Lead_Status__c merge field on the audience and populates it with the original Espresso Agent status value so teams can segment by pipeline position in Mailchimp campaigns. This allows marketing teams to filter contacts by their CRM pipeline stage (Prospect, Active, Follow-up, Converted) without requiring a separate CRM integration. The merge field stores the raw status text and can be used in segment conditions.

Espresso Agent owner IDs map to Mailchimp tags under an 'AgentAssignment' category. Mailchimp does not have a native owner or assignment field — tags serve as the proxy so campaigns can be filtered by agent territory if needed. Each agent in Espresso Agent receives a corresponding tag in Mailchimp, allowing teams to send agent-specific communications or filter campaigns by territory. The tag format follows 'AgentAssignment: [Agent Name]' for clear identification.

Call logs are activity records, not contact properties. FlitStack aggregates the most recent call date and total call count per contact and writes them to merge fields. Call outcome notes are stored as a third merge field. This preserves a summary of engagement history without replicating full activity logs.

Espresso Agent's email consent and unsubscribe flags transfer directly to Mailchimp's audience status. Subscribed contacts import as active, unsubscribed import with their status preserved, and bounced contacts are held for manual review before activation. This direct mapping ensures that contact preferences established in Espresso Agent are honored in Mailchimp without requiring manual re-entry. Teams should verify that all unsubscribe requests are correctly reflected in Mailchimp before launching campaigns to avoid compliance issues.

Espresso Agent's neighborhood search feature stores filter criteria (targeting parameters like equity range, owner type, property characteristics) per contact. Mailchimp has no equivalent — FlitStack creates a Neighborhood_Search__c merge field and stores the criteria as a pipe-delimited text string for reference.

Espresso Agent workflow sequences — task assignments, follow-up reminders, dialer cadences — have no Mailchimp counterpart. FlitStack exports the workflow definitions as a structured JSON reference document that the team uses to rebuild sequences as Mailchimp Customer Journeys. The exported JSON includes trigger conditions, time delays, action steps, and branch logic so developers can map each Espresso Agent workflow to equivalent Mailchimp journey triggers. This reference document serves as a blueprint for rebuilding automated sequences without losing the original workflow design.

Any Espresso Agent custom property fields beyond the standard set (e.g., equity estimate, listing motivation score, referral source) are created as Mailchimp merge fields. Field type is inferred from data (text → text merge field, number → number merge field, date → date merge field) before migration runs.

Files attached to Espresso Agent contact records (e.g., property PDFs, client documents) are not Mailchimp objects. FlitStack exports the file URLs to a reference CSV so the team can host files externally and link to them in campaigns if needed.

The original Espresso Agent contact ID is stored in a Source_System_ID__c merge field on each Mailchimp audience member. This enables de-duplication in delta runs and cross-referencing if the team ever syncs back to Espresso Agent or another CRM. During subsequent migration runs, FlitStack uses this ID to match existing Mailchimp contacts with updated Espresso Agent records, ensuring that contact data remains synchronized without creating duplicates. The Source_System_ID__c field is indexed for fast lookup in Mailchimp's merge field system.