Migrate from REIPro to Mailchimp

REIPro contacts migrate as Mailchimp subscribers in a single audience. We map the primary email address, first name, last name, and phone number to their respective Mailchimp merge field equivalents (EMAIL, FNAME, LNAME, PHONE). Unsubscribed or bounced REIPro contacts import as unsubscribed in Mailchimp to protect deliverability.

REIPro tags like 'Absentee Owner', 'Pre-Foreclosure', 'Cash Buyer', 'Realtor Referral' map directly to Mailchimp tags on the subscriber record. Multiple tags per contact are preserved individually. If REIPro uses hierarchical tags, we flatten them into dot-separated Mailchimp tags (e.g., 'Lead.Source.Absentee') and note the hierarchy in a separate merge field.

Free-text notes on REIPro contacts migrate as Mailchimp contact notes (up to the 1,000-character limit per note). Multiple notes are concatenated in reverse-chronological order with timestamps preserved. Notes exceeding the limit are truncated with a reference to the full content stored in the original-create-date merge field for audit purposes.

REIPro's property associations (linked property addresses, parcel IDs, MLS numbers) have no native Mailchimp equivalent. We create custom merge fields on the Mailchimp subscriber — PROPERTY_ADDRESS__c, PARCEL_ID__c, MLS_NUMBER__c — and populate them with the linked property data. This preserves the investor's property context without restructuring the Mailchimp data model.

REIPro's 10-step workflow stages (e.g., 'Lead Captured', 'Under Contract', 'Inspection Scheduled', 'Offer Made', 'Closed') map to a custom Mailchimp merge field called PIPELINE_STAGE__c. This field is populated from the contact's current step in REIPro's tracker. Stage history is not transferable to Mailchimp automations — it is stored as a semicolon-separated list in STAGE_HISTORY__c for reference.

REIPro's lead-source taxonomy (Absentee Owner, Bank Owned, Pre-Foreclosure, Tax Lien, MLS, Realtor Referral) maps to both a LEAD_SOURCE__c merge field and a tag on the Mailchimp subscriber. Value-by-value mapping ensures the specific source label is preserved — Mailchimp's native 'Source' field is not used because it is limited to a small set of predefined values.

REIPro's skip-trace results — including verified phone numbers, alternative contact numbers, and email confidence scores — migrate to custom merge fields SKIP_PHONE__c and EMAIL_SCORE__c on the Mailchimp subscriber record. This preserves outreach-ready contact data and eliminates the need to re-run skip-trace operations after migration.

REIPro's team member assignment (which investor or agent owns the lead) has no native Mailchimp equivalent, since Mailchimp lacks an owner or assignment model. We preserve the original owner name as ORIGINAL_OWNER__c on the subscriber record for audit trails, accountability tracking, and team reassignment purposes.

REIPro's 10-step workflow templates (step names, associated scripts, document links, reminders) cannot migrate to Mailchimp's automation model. We export the workflow definition as a structured JSON document so your team can rebuild the logic in Mailchimp's Customer Journey automation builder.

REIPro's built-in letter templates and direct-mail scripts are platform-specific HTML assets that do not translate to Mailchimp email templates. These are flagged as requiring manual rebuild using Mailchimp's template editor or third-party HTML import. Direct-mail functionality is not supported in Mailchimp's email-only environment.

REIPro's After Repaired Value (ARV) and rehab cost estimate fields map to custom Mailchimp merge fields ARV__c and REHAB_COST__c. These are informational for investor outreach sequences — they do not drive Mailchimp automations but can be used in merge tag personalization in email copy.

Mailchimp's native subscriber CreateDate and Timestamp fields reflect import time and cannot be backdated. We preserve the original REIPro creation and last-update timestamps as custom merge fields ORIGINAL_CREATE_DATE__c and ORIGINAL_UPDATE_DATE__c to maintain reporting continuity on investor outreach age, recency analysis, and contact lifecycle tracking.