Migrate from Homesnap Pro to Mailchimp

Homesnap Pro contacts map directly to Mailchimp subscribers. Email address serves as the unique identifier for deduplication. Contacts without valid email addresses are flagged and excluded from migration — no placeholder records created in Mailchimp. The email-based deduplication logic ensures that duplicate contacts in Homesnap Pro (e.g., the same person added by multiple agents) are merged into a single Mailchimp subscriber rather than creating redundant records.

Homesnap Pro stores first and last name as separate contact properties. Mailchimp's standard FNAME and LNAME merge fields receive these values directly. If only a full name field exists, we split on the first space to populate both merge fields.

Email is the primary key in Mailchimp. We use email address for deduplication: if a contact with the same email already exists in the target Audience, we update the existing subscriber rather than create a duplicate. During update operations, we preserve the subscriber's existing Mailchimp activity history (opens, clicks, unsubscribes) while overlaying the latest contact data from Homesnap Pro. This approach maintains engagement metrics while refreshing profile information.

Phone number migrates to Mailchimp's PHONE merge field. Mailchimp accepts formatted or unformatted numbers; we preserve the source format as-is to maintain readability for SMS-capable campaigns. If a contact has both mobile and office phone numbers in Homesnap Pro, we prioritize the mobile number for the PHONE merge field and store the office number in a custom merge field (OFFICE_PHONE) to preserve all available contact methods in Mailchimp.

Homesnap Pro stores full address components (street, city, state, zip, country). Mailchimp's ADDRESS merge field accepts structured address data. We map each component to its corresponding Mailchimp address subfield. Address data in Mailchimp enables location-based segmentation and personalized postcards through Mailchimp's integration with printing services. If any address component is missing or incomplete in Homesnap Pro, we populate the corresponding Mailchimp subfield with 'N/A' to maintain field consistency.

The primary company or brokerage associated with a contact in Homesnap Pro maps to Mailchimp's COMPANY merge field. This is particularly relevant for agent-to-client contacts where the agent represents a brokerage. If a contact has multiple company associations in Homesnap Pro, we use the primary company field for the COMPANY merge tag and store additional affiliations in a custom text field (OTHER_COMPANY) to preserve the complete relationship data within Mailchimp's subscriber profile.

Homesnap Pro custom property fields (e.g., lead source, transaction type, listing interest) require new merge fields to be created in the Mailchimp Audience before migration. We create these fields with appropriate types (text, number, dropdown) and map values during the load.

Homesnap Pro contact tags (e.g., Buyer, Seller, Active Listing, Hot Lead) transfer to Mailchimp tags verbatim. Tags in Mailchimp are additive — we preserve the full tag set per contact to maintain segmentation capability. If a tag name in Homesnap Pro conflicts with a Mailchimp reserved word, we append an underscore suffix (e.g., Buyer becomes Buyer_) to ensure the tag is accepted by Mailchimp's system without triggering platform restrictions.

Homesnap Pro agent profile information (bio, license number, brokerage) has no direct Mailchimp equivalent. We preserve this data as a JSON blob in a custom merge field for reference, but the agent profile itself is a source-side construct. This JSON storage approach allows agents to reference original profile data if needed, but the information will not be visible in Mailchimp's standard subscriber interface without custom development to parse the JSON payload.

Homesnap Pro showing request history and property viewing records have no structural equivalent in Mailchimp. We summarize showing activity as a text note in a custom merge field, but transactional showing data cannot map to Mailchimp's campaign-centric model. The custom field stores a text summary (e.g., '5 showings, last on 2024-01-15') rather than detailed transactional records. Agents requiring full showing history preservation should consider a CRM-to-CRM migration to a platform that supports transactional data natively.

Homesnap Pro links contacts to property listings and MLS data. Mailchimp has no concept of property associations. Listing links are not migrated — this is a fundamental model gap that requires a CRM-to-CRM migration for preservation. If maintaining listing associations is critical for your workflow, platforms like BoomTown, BoldTrail, or Lofty provide CRM functionality with email marketing integration that can preserve these relationships while offering more sophisticated lead management capabilities.