Migrate from Ready_ to Mailchimp

Ready_ Contacts map directly to Mailchimp Members within a designated Audience. Standard fields (email, first name, last name, phone, address) map to their Mailchimp equivalents (EMAIL, FNAME, LNAME, PHONE, ADDRESS). We resolve owner Team Member IDs to email addresses during extraction and store the original owner email as a merge field owner_email for segmentation. Any Contact without an email address is flagged and excluded because Mailchimp requires an email address for a Member record.

Ready_ Company records have no direct Mailchimp equivalent. Company name maps to a custom merge field company_name (60 chars recommended, truncated if exceeding Mailchimp's 255-char text limit). For segmentation, company domain or industry maps to Mailchimp Tags applied to the Member. If the customer has multiple business lines in Ready_ Companies, we can create separate Mailchimp Audiences per company and note this in the scoping output.

Pipeline Deals in Ready_ have no equivalent in Mailchimp's Audience model. Mailchimp is not a CRM and does not store deal values, pipeline stages, or expected close dates. We document every active Deal record in the migration scope with its stage, value, and owner so the customer's admin can record these in a separate CRM or spreadsheet. Closed-won Deals may be re-imported as Members with a tag closed_won for re-engagement campaigns.

Activity records in Ready_ represent the sales engagement timeline (calls, emails, meetings, tasks) and have no Mailchimp equivalent. Mailchimp tracks email engagement (opens, clicks, unsubscribes) only after campaigns are sent from the Mailchimp platform. We deliver a written inventory of Activity records with type, timestamp, owner, and linked Contact so the customer's admin can assess whether any pre-existing engagement data should be re-imported into a connected CRM.

Ready_ custom fields on Contacts (text, number, date, picklist) map to Mailchimp merge fields. Text fields are subject to Mailchimp's 255-character limit; any field exceeding this threshold is flagged for truncation with the first 255 characters preserved and a note added to the mapping table. Date fields map to Mailchimp DATE merge fields. Picklist fields map to text merge fields with the selected value as content. We validate the total field count against Mailchimp's 30-field per Audience limit during scoping and consolidate or drop low-priority fields if the count exceeds 30.

Ready_ Team Members represent users in the source CRM. We map Team Member email addresses to Mailchimp Members using the owner email field rather than creating a separate User object (Mailchimp has no user-management concept). For segmentation purposes, each Team Member's contacts can be tagged by owner to enable sending reports per rep or filtering audience views by original owner. Team Members who do not appear as Contacts in Ready_ are not imported as Members.

Ready_ Notes attached to Contacts have no Mailchimp equivalent. Notes cannot be stored on Member records in Mailchimp. We export Notes as a separate CSV file with Contact email (as lookup key), note body, and note timestamp. The customer's admin can review this file post-migration or import it into a connected CRM if one is in place.

Pipeline stages from Ready_ Deals can be mapped to Mailchimp Tags or Segments if the customer wants to segment contacts by deal stage history. A stage tag like pipeline_won or pipeline_lost applied to Members enables post-migration re-engagement campaigns targeting specific pipeline segments. This is an optional mapping that requires customer confirmation during scoping.