Migrate from REsimpli to Mailchimp

Every REsimpli contact with an email address becomes a Mailchimp subscriber. Contacts without emails are flagged for review — Mailchimp requires an email address for audience membership. REsimpli's contact type (Buyer, Seller, Vendor) is preserved as a tag on the Mailchimp subscriber.

Mailchimp provides standard merge fields for common contact properties. REsimpli's first name, last name, phone, and mailing address map directly. REsimpli's address field (street, city, state, zip) maps to Mailchimp's combined ADDRESS field format. When a contact has multiple address types (mailing vs. property), we prioritize the primary property address and map it to the standard ADDRESS field while preserving secondary addresses as a custom merge field.

REsimpli's custom contact properties (property type interested in, estimated deal value, motivation level) become Mailchimp custom merge fields. Mailchimp allows up to 40 merge fields per audience — if your REsimpli setup exceeds this, we group related fields or preserve overflow in a JSON-formatted reference field.

REsimpli property records are linked to contacts, not standalone in Mailchimp. We extract the primary property address, property type, and estimated value from the linked Property record and attach them as merge fields on the subscriber. Secondary properties are preserved as comma-separated values in a secondary property merge field.

Mailchimp has no deal or opportunity object. Deal name, stage, amount, and close date from REsimpli become custom merge fields on the contact record (Deal_Name__c, Deal_Stage__c, Deal_Amount__c, Deal_Close_Date__c). Deal stage is also applied as a tag so you can build segments from it.

REsimpli's contact tags (e.g., 'hot_lead', 'out_of_state', 'cash_buyer') map directly to Mailchimp tags. Tags migrate as-is — Mailchimp supports unlimited tags per subscriber. Dynamic segments in REsimpli (based on property criteria or score thresholds) are documented as a segmentation plan for rebuild in Mailchimp.

Mailchimp's subscriber Created_Date reflects when the contact entered Mailchimp, not REsimpli. We preserve original create and modified timestamps from REsimpli as custom DATE-type merge fields. These timestamps maintain reporting continuity and enable campaign targeting based on when the lead was originally captured in your source CRM. Historical campaign attribution can reference these dates to track engagement timelines accurately.

REsimpli drip campaigns with multi-step email + SMS sequences have no Mailchimp equivalent. We export the campaign structure (step order, delay days, email content, condition branches) as a JSON rebuild reference so your Mailchimp admin can reconstruct the logic in Customer Journey automations.

REsimpli's SMS drip campaigns and AI voice sequences (SpeedToLead, VoiceFollow) are a core product feature that doesn't exist in Mailchimp. These must be rebuilt in a dedicated SMS tool (e.g., Twilio, Salesmsg) or Mailchimp's SMS add-on. We export the contact phone numbers and SMS consent flag so your SMS tool can re-import the audience.

Mailchimp tracks engagement at the campaign level — opens, clicks, and unsubscribes are native. REsimpli's historical engagement data (reply rates, call outcomes) is preserved as a custom merge field (Engagement_History__c) for reference. Future engagement data will accumulate in Mailchimp after migration.

Mailchimp has no owner assignment model — subscribers aren't owned by users. REsimpli's assigned user (agent) is preserved as a text merge field on each subscriber. If your team uses Mailchimp's Customer Journey branching, this field can be used to trigger agent-specific follow-up emails.

REsimpli's list-stacking enrichment flags (absentee owner, tax delinquent, equity rich) are common in real estate investor CRMs. We map these as Mailchimp tags plus a stacked_flags text merge field listing all applicable flags. This preserves the enrichment data without requiring multiple merge fields.