Migrate from Propertybase to Mailchimp

Each Propertybase Individual Contact becomes one Mailchimp Audience member. Email address is the required unique identifier. First name, last name, phone, and address fields map to standard Mailchimp merge fields (FNAME, LNAME, PHONE, ADDRESS). The contact's email subscription status in Propertybase determines the Mailchimp member status on import.

Propertybase contacts linked to a Company record carry the company name as a property. In Mailchimp this maps to a COMPANY merge field on the member record. The source Company record itself also generates a tag with the company name so segments can group members by brokerage or builder affiliation.

Propertybase Company records (brokerages, builders, agencies) have no direct Mailchimp equivalent. We merge the company name into a COMPANY merge field on every associated contact and create a tag from the company name so you can build Mailchimp segments by brokerage. Company-level fields like industry and address become additional merge fields or get dropped if no contact-level equivalent exists.

Propertybase Listings (projects and individual properties) carry addresses, price, and status. Since Mailchimp has no listing object, we map listing status (Active, Pending, Sold) as a tag on the contact who is the listing owner or buyer. Listing address and price become optional merge fields if they exist on the contact record; otherwise they are exported as a reference CSV for manual campaign use.

Propertybase Offers track offer amount, status, and closing date for a buyer contact. Mailchimp has no deal object, so offer status (Accepted, Pending, Withdrawn) and offer amount migrate as tags and a OFFERAMT merge field on the associated buyer contact. Closing date becomes an OFFERCLOSE merge field. Offer context enables re-engagement campaigns for buyers who did not close.

Propertybase Enquiries capture lead source and inquiry type (buying, selling, viewing). Multiple enquiry types per contact merge into a single tag group (ENQUIRY_SOURCE) on the contact's Mailchimp record. The source URL or referral channel becomes an ENQSOURCE merge field. Enquiry date is stored as ENQDATE if meaningful for segmentation.

Propertybase custom objects attached to contacts (such as mortgage details, referral sources, or property preferences) require custom merge fields in Mailchimp. We inspect the custom object schema, create Mailchimp merge fields for each relevant attribute, and apply the data to contacts that have the relationship. If the custom object is many-to-many, we flatten it into tags on each related contact.

Propertybase file attachments on contacts (such as pre-qualification letters, buyer agreements, or identification documents) download and re-upload to Mailchimp's File Manager. Each file gets a URL that can be referenced in campaigns or automation emails. Mailchimp's file size limit is 30 MB per file; larger files are linked as external URLs instead.

Propertybase Workflow Rules, Action Plans, and Process Builder flows cannot migrate to Mailchimp Automation Flows because the trigger logic depends on CRM state changes that have no equivalent in an email marketing platform. We export all workflow definitions as JSON so your Mailchimp admin can rebuild triggers based on list membership, tag changes, or date-based conditions in Automation Flows.

Propertybase tracks which agent or team member owns each contact via OwnerId. Mailchimp has no owner concept. We create an AGENT merge field on each contact and apply a tag with the agent's name so campaigns can be filtered or personalized by the responsible agent. Unassigned contacts receive an 'Unassigned Agent' tag.

Propertybase uses Contact Type pick-list values (Buyer, Seller, Lead, Vendor, etc.) to categorize contacts. Each distinct value becomes a tag in the CONTACT_TYPE group in Mailchimp. Contacts with multiple types receive multiple tags. This tag group is the primary segmentation signal for targeted campaigns and automation flows in Mailchimp.