Migrate from Zurple to Mailchimp

Zurple contacts map 1:1 to Mailchimp subscribers by email address. First name, last name, email, phone, and address fields migrate as standard Mailchimp merge fields. Duplicate email addresses are flagged and merged — one Mailchimp subscriber record results per unique email.

Mailchimp has no native company/account object. Zurple company name migrates as a COMPANY merge field on the subscriber. Company phone and domain are stored as additional text merge fields. Multi-contact companies result in the company name appearing on each subscriber record — Mailchimp does not deduplicate company entities across contacts.

Zurple lead status values (New, Contacted, Qualified, Dormant) map to Mailchimp tags applied at migration time. The tag names match the source values so segmentation in Mailchimp reflects the original lead stage without requiring lookup logic. These tags are applied as singular, flat labels on each subscriber record, making it straightforward to filter the audience based on historical lead status at any point after migration.

Zurple deal pipeline stages (Active, Under Contract, Closed Won, Closed Lost) have no Mailchimp equivalent — they become tags on the associated contact record. Multiple stages per contact are each applied as separate tags so agents can filter the audience by any stage the contact has passed through.

Zurple's buyer/seller classification migrates both as a tag (Buyer, Seller, or Both) and as a BUYERSELL merge field. Tags enable segment-level filtering in Mailchimp automations; the merge field preserves the raw value for reporting and filtering in campaign sends. This dual representation ensures that both visual segmentation and programmatic access to the classification are available.

Zurple property type preferences (Residential, Commercial, Land, Condo) become tags on the subscriber. Multiple property interests are each applied as individual tags. Neighborhood and area preferences migrate as AREA tags so Mailchimp campaigns can be filtered by geographic segment. These tags are applied with a consistent naming convention to facilitate straightforward selection when building audience segments in Mailchimp.

Zurple lead source (Facebook, Google Ads, Referral, IDX Website) migrates as a SOURCE tag on each subscriber. This preserves attribution data from Zurple so Mailchimp campaigns can be segmented by original acquisition channel after migration. The tag is set at migration and remains attached to the subscriber, allowing you to run channel‑specific performance reports in Mailchimp's analytics dashboard.

Mailchimp has no deal or opportunity object. Zurple deal records (amount, close date, stage) cannot map to native Mailchimp fields. FlitStack captures deal stage and estimated value as tags on the associated contact record; deal-level amounts are stored in a custom merge field for reference but do not drive Mailchimp functionality.

Zurple stores call logs, email threads, and note history on contact records. Mailchimp has no activity log per subscriber. FlitStack preserves the most recent note text as an ACTIVITY_LOG merge field; full activity history is exported as a structured JSON file for reference and rebuilt manually in Mailchimp if needed.

Zurple unsubscribed contacts are exported with their email address and status flag. During Mailchimp import, unsubscribed emails are placed on the account suppression list before the active migration batch runs — preventing accidentally re-subscribing contacts who previously opted out. This step protects sender reputation and ensures compliance with email consent regulations across all future campaigns.