Migrate from PropFlo to Mailchimp

PropFlo contacts become Mailchimp subscribers. Email address serves as the unique identifier for subscriber matching and deduplication. First name, last name, phone, job title, and physical address map directly to Mailchimp's standard subscriber fields without requiring any custom field creation.

PropFlo leads migrate to Mailchimp as subscribers with a 'Lead Status' tag applied to indicate their original status. The lead source (Organic, Referral, Portal, Walk-in, Campaign, Direct) is preserved as a separate Mailchimp tag for segmentation and campaign attribution in the new platform.

PropFlo companies are stored as a custom field value on the subscriber record. Since Mailchimp subscribers are individual contacts (not company-centric like a CRM), the company name is mapped to a 'Company' custom field on each subscriber for direct reference and company-based segmentation.

PropFlo deals cannot map to a Mailchimp native object. Deal name, stage, amount, probability, and close date are stored as Mailchimp custom fields on the associated contact. Deal stage is also applied as a tag for filtering and audience segmentation.

Each PropFlo property record maps to one or more Mailchimp custom fields on the subscriber. Property name, type, status, price, and location are mapped to separate custom fields. If the property has nested units, unit data is concatenated into a text merge field.

PropFlo units under a property are aggregated into a single text merge field in Mailchimp (e.g., 'Unit 101: 2BHK, $4500/mo; Unit 203: 3BHK, $5200/mo'). This avoids creating multiple Mailchimp subscribers for a single contact who may be associated with multiple units.

PropFlo activity history (last call date, last email date, meeting notes, and task completions) is preserved as custom fields and tags in Mailchimp. There is no native activity timeline in Mailchimp — interaction history is limited to Mailchimp engagement events like opens and clicks.

PropFlo workflows including assignment rules, approval flows, demand note generation, and automated task generation cannot migrate to Mailchimp's Customer Journey automations. We export workflow definitions as a structured JSON and PDF reference file for your team to rebuild logic in Mailchimp's automation builder.

All PropFlo custom fields are evaluated against Mailchimp's field limits. Fields that fit within the 30-field standard limit (80 on Premium) are created as Mailchimp custom fields. Excess fields are encoded into a JSON merge field and parsed at send time using Mailchimp's personalization tokens.

PropFlo owner assignments map to a Mailchimp tag identifying the assigned agent or team member responsible for each contact. This allows you to filter sends by owner in Mailchimp, create owner-specific campaigns, and rebuild PropFlo's assignment logic as Mailchimp segments.

PropFlo cost sheets contain itemized pricing for a property unit. This structured data cannot map to a native Mailchimp field. We serialize the cost sheet as a JSON string in a merge field; your team uses Mailchimp's personalization syntax to surface relevant line items in email content.

PropFlo Agreement of Sale and Sale Deed records track post-sale legal milestones including execution dates, registration numbers, and completion status. These have no Mailchimp equivalent — we preserve the record's status and key dates as custom fields on the subscriber for compliance reference and future segmentation.

PropFlo payment tracking records (installment dates, amounts, payment status, and due dates) are serialized into a JSON merge field in Mailchimp. This keeps complete payment history accessible for reference within the email platform without creating a native billing construct for your team.

PropFlo lead source (Website Form, Property Portal, Referral, Walk-in, Campaign, Event, Partner) migrates directly as a Mailchimp tag on each subscriber. This preserves the original acquisition channel for audience segmentation, campaign attribution reporting, and future re-engagement targeting based on how contacts originally entered your pipeline.

Any PropFlo tags or labels applied to contacts are migrated as Mailchimp tags 1:1 preserving the original taxonomy. Tags in Mailchimp drive segmentation, automation triggers, Customer Journey entry points, and campaign filtering — they replicate the full contact classification logic from PropFlo for consistent audience management.