Migrate from Rechat to Mailchimp

Rechat contacts migrate as Mailchimp subscribers within a target audience. Email address is the unique identifier. First name, last name, phone, and job title map to standard Mailchimp merge fields (FNAME, LNAME, PHONE, TITLE). Original create dates preserved as custom merge fields.

Rechat custom fields on contacts consolidate into Mailchimp merge fields. Standard plans cap at 30 merge fields per audience; Premium allows 80. We group related properties (e.g., multiple address fields into a single ADDRESS merge field) and flag fields exceeding the limit for manual placement or tagging strategy.

Rechat company name maps to Mailchimp's built-in COMPANY merge field. Industry, annual revenue, and employee count migrate as additional merge fields or contact tags depending on segmentation needs. Parent-child company hierarchies collapse to a single company affiliation. We also map the primary company website to a custom merge field for reference, and any subsidiary relationships are flattened to ensure each contact carries a single company affiliation in Mailchimp.

Rechat deal pipelines with stages, amounts, and close dates have no Mailchimp equivalent. Mailchimp tracks campaign engagement, not pipeline progress. Deal data migrates as contact tags or custom fields for reference but cannot drive workflow automation. Deal stage labels are stored as tags, letting you segment contacts by sales phase, and we provide a mapping table linking each tag to the original Rechat stage.

Rechat's real estate-specific objects — Listings, Searches, Tours — are MLS-derived data with no Mailchimp counterpart. We export these as JSON alongside the migration and document the schema for any custom rebuild you may want using Mailchimp's custom audience fields or third-party integrations.

Rechat stores email metadata (subject line, date, teaser) retrieved on-demand from Gmail/Outlook. This migrates as contact-level custom fields capturing last contacted date and subject. Full email body content is not stored in Rechat and cannot migrate. We also map the email thread identifier to a custom field so you can reference the original conversation in Gmail or Outlook if needed.

Rechat agents with user_type, features array, and MLS associations have no Mailchimp equivalent. Agent attribution (which agent owns the contact) migrates as a custom merge field (AGENT_EMAIL__c or similar). The agent's Rechat user profile and permissions do not transfer. If you need to route campaigns based on agent territory, you can use the AGENT_EMAIL__c field to filter segments, though Mailchimp does not natively support owner-based assignment.

Rechat contact tags map 1:1 to Mailchimp subscriber tags. Tags are the primary mechanism for preserving Rechat's label system in Mailchimp without consuming merge-field slots. Tag-based segmentation works natively in Mailchimp. You can also create dynamic segments based on tag combinations, and tags can be used in automation triggers to send follow‑up emails when contacts are added to specific groups.

Rechat contacts with bounce or unsubscribe status export as Mailchimp non-subscribed contacts in the suppression list. This preserves suppressions across the migration and protects sender reputation and deliverability from day one. We also verify that the suppression list size matches the exported count and flag any addresses that appear in both the active audience and the suppression list to avoid duplicate entries.

Rechat calendar events and meeting metadata sync from Gmail/Outlook but store no body content. Meeting titles and timestamps migrate as contact-level custom fields if meaningful, but Mailchimp has no native scheduling or meeting tracking capability. We recommend exporting any required meeting context to a separate system for future reference, as Mailchimp’s features are focused on audience engagement rather than calendar management.