Migrate from Property Shell to Mailchimp

Property Shell contact records with lead status migrate as Mailchimp subscribers within your primary audience. The contact's email address becomes the subscriber identifier and primary key for matching records during import. Lead source, enquiry date, and assigned agent fields map to dedicated merge tags on the subscriber record, preserving the origin and ownership context of each lead.

Purchaser records in Property Shell — representing buyers who have signed contracts or reached settlement — map directly to Mailchimp subscribers with a purchaser-type merge tag value applied. Settlement date and purchase price (where stored) migrate as date and number merge tags respectively, enabling purchase-value segmentation and anniversary campaign triggers in Mailchimp.

Property Shell's developer and company records have no direct Mailchimp equivalent, requiring flattening into subscriber merge tags. Company name, ABN/ACN, and address fields flatten into text merge tags on the contact record. Standard merge tags (FNAME, LNAME, COMPANY, PHONE) cover common fields; additional company-specific fields become custom merge tags to preserve developer attribution.

Property Shell project and listing data linked to a contact — such as 'Unit 403 at Parkview Estate' — becomes a custom text merge tag (PROPERTY_NAME__c) and a corresponding Mailchimp tag using the project name. Contacts linked to multiple projects generate multiple tag entries on the single subscriber record, enabling segment filtering by specific development interest.

Property Shell deal stages (Lead, Enquiry, Contract, Settlement) have no native Mailchimp equivalent and must be modelled via tags and segments. Each deal stage maps to a corresponding Mailchimp tag applied to the subscriber, and audience segments are created for each stage value to enable pipeline-position targeting. Stage transition timestamps migrate as custom date merge tags for tracking.

Property Shell lead status values map directly to Mailchimp subscriber statuses using a defined value mapping: Active leads become 'subscribed', closed-lost leads become 'unsubscribed', and archived records become 'cleaned'. This prevents inadvertent re-engagement campaigns targeting leads who have formally opted out in Property Shell.

The enquiry source field (e.g., 'Website', 'Referral', 'Realestate.com.au') migrates as both a text merge tag (ENQUIRY_SOURCE) and a Mailchimp tag applied to the subscriber. Tags enable segment-based campaigns targeting contacts grouped by their original acquisition channel, supporting channel attribution and ROI analysis.

Property Shell owner and agent assignments map to text merge tags on the subscriber record. The AGENT_NAME merge tag stores the assigned agent's name, while AGENT_EMAIL stores the agent's email address for internal routing reference. These remain flat tag values — they do not create linked user records or agent dashboards within Mailchimp.

Property Shell attachments including contracts, floor plans, and settlement documents stored against contacts have no Mailchimp storage equivalent. Documents must be re-hosted externally on a file hosting service and linked via URL merge tags. We generate a full attachment inventory per contact as a reference export for manual follow-up and document retrieval.

Property Shell marketing automation workflows — including enquiry nurture sequences, settlement reminder flows, and lead routing rules — do not transfer to Mailchimp's automation system. FlitStack AI exports all workflow definitions as JSON and PDF reference documents so your team can rebuild equivalent automations within Mailchimp's automation builder using the exported definitions as a functional specification.