Migrate from LeadManaging to Mailchimp

LeadManaging contact records (name, email, phone, address) map directly to Mailchimp audience members. Email address serves as the primary key for deduplication. If a LeadManaging contact has no email address, it is flagged for review before migration because Mailchimp requires an email address for every subscriber.

LeadManaging stages (New, Touring, Applying, Leased, Lost) cannot map to a native Mailchimp field because Mailchimp has no lifecycle stage object. We create a LEAD_STAGE tag per contact with the stage value, then build Mailchimp segments filtering by that tag. Segments can be used in automation triggers for stage-appropriate campaigns.

LeadManaging stores desired property name, unit type preference, and rent range per lead. Mailchimp has no property object — this data migrates as custom merge fields (PROPERTY_NAME, UNIT_TYPE, RENT_MIN, RENT_MAX, MOVE_IN_DATE) created in the Mailchimp audience before contacts are imported. Merge fields must be created manually in Mailchimp or via the Mailchimp API prior to data load.

LeadManaging lead source fields (Website Inquiry, ILS, Referral, Walk-in, etc.) migrate as tags on each contact in Mailchimp. Tags preserve attribution data for source-based segmentation and campaign performance reporting. Multiple source tags per contact are supported. These tags can be combined with other contact attributes to build highly targeted re-engagement campaigns.

Any LeadManaging custom property not covered by standard fields maps to a Mailchimp merge field. We read the LeadManaging field schema during discovery and create a corresponding merge field in Mailchimp for each custom property before importing contacts. Merge field type (text, number, date, phone) is inferred from the source data type.

LeadManaging contact notes and activity timestamps (last contacted date, last tour date, last email open) migrate as Mailchimp notes on each contact. Note content preserves the original timestamp and activity type label. Mailchimp displays notes in the contact profile sidebar for reference by the marketing team.

LeadManaging email opt-in flag maps to Mailchimp member status: opted-in contacts become 'subscribed', explicitly opted-out contacts become 'unsubscribed', bounced or cleaned contacts from LeadManaging become 'cleaned' in Mailchimp. This ensures Mailchimp's compliance model is respected and prevents sending to non-consenting addresses.

LeadManaging lease application records (application status, screening result, approved amount) have no Mailchimp equivalent. We preserve this data as a structured tag (APPLICATION_STATUS: Approved / Pending / Denied) and a custom merge field (APPLICATION_DATE, SCREENING_SCORE) for reference. The actual leasing workflow must be managed outside Mailchimp.

LeadManaging owner assignment (the leasing team member assigned to a prospect) migrates as an OWNER tag on the Mailchimp contact. This enables segmentation by assigned leasing agent for team-specific campaigns or routing follow-ups. If Mailchimp is used by multiple agents, tags can be used to filter the audience for agent-dashboard views.

LeadManaging contact tags (property-specific labels, demographic tags, preference tags) migrate 1:1 as Mailchimp tags. Tag names are preserved exactly as stored in LeadManaging. Tag-based segmentation in Mailchimp replicates the audience filtering logic from LeadManaging. After migration, you can use Mailchimp's tag management interface to merge, rename, or retire tags as your marketing strategy evolves.