Migrate from REDA to Mailchimp

REDA company associations become flat text in Mailchimp with no relational integrity

REDA Contact links to Company via Salesforce AccountId lookups, supporting multiple company associations per contact. Mailchimp audience members have no relational cross-object model — the company name becomes a TEXT merge field (COMPANY_NAME) on the member record. There is no referential integrity enforcement: if a company name changes in REDA, the Mailchimp merge field value becomes stale. We recommend tagging contacts by company name for dynamic segmentation rather than relying on the static merge field value. For contacts with multiple REDA company associations, we create multiple tags (e.g., 'Company: ABC Corp', 'Company: XYZ LLC') since Mailchimp supports unlimited tags per member.

Property, Lease, and Unit objects have no Mailchimp structure and cannot migrate as records

REDA's real estate data model includes Property, Unit, Lease, and Tenant objects with relational links, lease terms, rent schedules, and unit availability status. Mailchimp is an email marketing platform with no real estate domain objects. We cannot create Property records in Mailchimp — the only migration path is to flatten relevant fields onto the contact record as TEXT or NUMBER merge fields. For example, a contact's current lease status (Active, Expired) becomes LEASE_STATUS__c on the Mailchimp member, and property interest preferences become tags. Lease terms, rent amounts, and unit numbers are not structural in Mailchimp; they can only be stored as free-text reference fields. Teams needing property-specific communications should consider a complementary real estate CRM alongside Mailchimp.

REDA Salesforce custom fields require manual merge field creation in Mailchimp before import

REDA custom fields follow Salesforce __c naming conventions and support field types including currency, percent, formula, and rollup summary. Mailchimp merge fields must be created manually in the audience settings before import, with explicit type assignment (TEXT, NUMBER, DATE, ADDRESS, PHONE). Salesforce formula fields do not evaluate in Mailchimp — we export the formula's displayed value at migration time. Rollup summary fields (e.g., total lease value across all units for a contact) cannot be computed in Mailchimp and must be stored as static values. We deliver a merge field creation checklist with field-type recommendations based on the REDA schema before migration runs, so Mailchimp is ready for data import.

Mailchimp's API rate limits extend migration batch windows for large contact volumes

Mailchimp's API imposes a 5,000-member-per-request limit on batch imports and a rolling rate limit of 2,000 requests per minute on some endpoints. REDA instances with 500,000+ contacts require multiple API batch calls, extending migration clock time beyond what smaller imports require. We parallelize batch operations across multiple import jobs when Mailchimp's infrastructure permits, but throttling is determined by Mailchimp's system at the time of import. For very large lists, we recommend migrating in tranches (e.g., active leases first, then archived contacts) to manage the batch window and minimize downtime between final delta pickup and go-live.

REDA workflows and Salesforce Flow automations have no Mailchimp Customer Journey equivalent

REDA workflows built in Salesforce Flow (lead assignment rules, property status change alerts, lease renewal notifications) do not migrate to Mailchimp Customer Journeys. Mailchimp Customer Journeys are email-specific automation constructs triggered by subscriber actions (opens, clicks, signups) or time-based delays — they cannot replicate Salesforce Flow logic involving object state changes, approval processes, or cross-object triggers. We export REDA workflow definitions as a reference document listing trigger conditions, action steps, and criteria so your team can rebuild equivalent automations in Mailchimp's Customer Journeys builder. This is a manual rebuild effort that we scope separately from the data migration.