Migrate from Real Geeks to Mailchimp

Real Geeks leads map 1:1 to Mailchimp contacts. Email address is the primary key — leads without a valid email address are flagged and held from import because Mailchimp requires a valid email for every contact. Duplicate emails across Real Geeks leads are resolved by keeping the most recently modified record.

Real Geeks urgency values (Cold, Warm, Hot, Contacted, Not Contacted) map to Mailchimp Tags applied at import time: RG_Urgency_Cold, RG_Urgency_Warm, RG_Urgency_Hot, RG_Urgency_Contacted, RG_Urgency_Not_Contacted. Custom urgency values are preserved as their exact text in the tag name. These tags let you segment contacts by urgency in Mailchimp campaigns and automations, preserving any custom tier names exactly as they appear in Real Geeks.

Real Geeks timeframe values (Immediately, 1 Week, 2-4 Weeks, 30 Days, 60 Days, 90 Days, 3-6 Months, 6-12 Months, 1 Year Or More) map to Mailchimp Tags like RG_Timeframe_Immediately, RG_Timeframe_1Week, etc. This enables Mailchimp segmentation by buyer readiness without requiring custom merge-field logic.

Real Geeks status values map to Mailchimp contact statuses: Active → Subscribed, Cancelled → Unsubscribed, Dead → Archived, In Escrow and Closed Escrow → Subscribed (with RG_Status_Escrow or RG_Status_Closed_Escrow tag applied). This preserves the pipeline stage signal for segmentation. You can use these status tags to trigger automation paths, such as sending escrow‑update emails when a contact receives the RG_Status_Escrow tag.

Real Geeks lead source (website, Zillow, Realtor.com, API, etc.) is stored in a custom Merge Field (RG_Source__c) on the Mailchimp contact. Source-based segmentation in Mailchimp is then done by filtering contacts where RG_Source__c equals a specific value. Combining the source merge field with urgency tags enables multi‑dimensional campaigns, such as targeting hot leads from Zillow with property‑search drip content.

Real Geeks tags on a lead are transferred as Mailchimp Tags verbatim. If a lead has tags [investor, luxury, referral], those exact tags are applied in Mailchimp. This preserves any custom tagging logic your team built in Real Geeks. After migration, you can refine or expand tags in Mailchimp to reflect new marketing segments without affecting the original Real Geeks data.

Real Geeks saved searches represent specific property-criteria sets that leads matched. Mailchimp has no saved-search equivalent — we export each saved search name and the associated lead count as a reference document so your team can recreate segments in Mailchimp using tags and merge-field filters that approximate the original criteria.

Real Geeks tracks property searches and listing views per lead. We translate this into descriptive Mailchimp Tags (e.g., RG_Searched_Condo, RG_Viewed_Over_1M, RG_Saved_10_Properties) based on the most recent or most frequent activity type. This gives Mailchimp segmentation capability around property intent without importing the raw activity log.

Real Geeks companies (name, address, domain) are split into Mailchimp Merge Fields: RG_Company_Name, RG_Company_Address, RG_Company_Domain. Mailchimp has no native company object — if your team needs company-level reporting, we recommend a separate CRM for that, or collapsing company data into contact-level fields.

Real Geeks drip campaign enrollment (which leads were in which sequence, at what step) is exported as a reference CSV: Contact_Email, Campaign_Name, Current_Step, Step_Name, Enrolled_Date. This is not imported into Mailchimp automations but serves as a rebuild guide for your email team to recreate the sequence logic in Mailchimp Customer Journeys.

Real Geeks custom lead fields map to Mailchimp Merge Fields (MERGE0–MERGE7 on Standard, up to MERGE80 on Premium). Mailchimp's field type support (text, number, date, phone, address, birthday) is matched per field. If field count exceeds the Mailchimp plan limit, we group less-critical fields into a single JSON-formatted merge field for reference.

Real Geeks last communication date maps to a Mailchimp date-type Merge Field (RG_Last_Communication__c) preserved for reporting continuity. This allows segmentation of leads not contacted in X days without querying the original CRM. You can also use this date in automation triggers, such as re‑engagement emails after a specified inactivity period.