Migrate from Property Raptor to Mailchimp

Property Raptor contacts migrate as Mailchimp audience members. Email address is the primary key — matched or created per Mailchimp's deduplication rules. First name, last name, phone, and address fields map to Mailchimp's standard member fields. Each member lands in one Mailchimp audience, keyed by your account configuration.

Property Raptor company records (agency name, brokerage, developer) have no direct Mailchimp equivalent. We store the primary company name as a text merge field (COMPANY_NAME) on each related contact. For contacts with multiple associated companies, the most recently modified company becomes the primary value and additional associations are appended as comma-separated text in the same field.

Property Raptor opportunity records carry stage values such as Lead, Viewing Booked, Offer Made, Under Negotiation, Closed Won, Closed Lost. Each stage value maps to a Mailchimp tag — for example, 'Lead' becomes tag 'Stage: Lead', 'Closed Won' becomes tag 'Stage: Closed Won'. Tags are applied to the member record at migration time. Historical stage transitions are not individually preserved — the final stage at migration time drives the tag applied.

Property Raptor listings carry fields like property type, price, address, bedrooms, bathrooms, listing status, and portal references. These cannot map to any native Mailchimp object. We create custom merge fields on each related contact — PROPERTY_TYPE__c, PROPERTY_PRICE__c, LISTING_ADDRESS__c, BEDROOMS__c, LISTING_STATUS__c — capturing the most recent listing associated with that contact. Multiple listings per contact are stored as semi-colon-separated values in the primary merge field.

Property Raptor records lead source (Portal, Referral, Website, Direct) on the contact. The source value is stored as a text merge field (LEAD_SOURCE__c) on the Mailchimp member and also applied as a tag (Source: Portal, Source: Referral) for use in Mailchimp segmentation. This dual-approach ensures lead source is available in both merge field reports and in audience filter logic.

Property Raptor stores individual email, call, meeting, and note records as Salesforce Tasks and Events with timestamps and owners. Mailchimp has no equivalent activity log per member — only aggregated campaign engagement (opens, clicks, unsubscribes) is tracked. We migrate the most recent note as a text merge field (LAST_NOTE__c) and tag the member with engagement tags based on available history. Detailed activity logs are exported as a CSV reference file for manual review.

Property Raptor Enterprise allows custom objects for real estate-specific records such as property inquiries or viewing requests. Each custom object field maps to a Mailchimp merge field on the related contact. Custom object associations that use N:N relationships in Property Raptor become tags on the Mailchimp member. FlitStack surfaces the full custom object schema before migration so you can confirm which fields become merge fields versus tags.

Property Raptor owners (agents) are Salesforce users linked to contacts and opportunities. Mailchimp has no owner field — the assigned agent's name and email are stored as text merge fields (ASSIGNED_AGENT__c, AGENT_EMAIL__c) on the member and also applied as a tag using the agent name for segmentation. This allows you to route campaigns based on the agent assigned in Property Raptor.

Property Raptor files attached to contacts, listings, or opportunities have no Mailchimp equivalent. Mailchimp attachments are limited to email campaign assets. We export file metadata (filename, URL, attached record type) as a reference CSV and flag which files require manual re-upload to Mailchimp's file manager if they are campaign-relevant.

Property Raptor automations (lead assignment rules, stage-change notifications, listing-update triggers) are stored in Salesforce Flow or Raptor's rule engine. Mailchimp Customer Journeys handles email automation differently — event-based, with triggers such as 'joins audience' or 'clicks link'. We export all workflow definitions as a structured JSON reference file so your Mailchimp team can rebuild equivalent journeys in the Mailchimp automation builder.