Migrate from Streak to Mailchimp

Streak Contacts (pulled from Gmail, stored with name, email, company affiliation, and custom contact properties) map to Mailchimp Audience members. Email address is the dedupe key. Status field (subscribed, unsubscribed, cleaned) is derived from Streak's contact-level opt-out state and mail merge suppression flags. First Name, Last Name, and company name map to Mailchimp merge fields FNAME, LNAME, and COMPANY. Any Streak custom contact properties map to Mailchimp account-level merge fields, which apply to all Audience members.

Streak Boxes are not a native Mailchimp concept. We treat each Box as a subscriber context: the Box's associated Contact (or the Box creator if no Contact exists) becomes the Audience member, and Box custom property values are appended as merge field data on that member. Box stage and pipeline membership cannot map to a Mailchimp equivalent; we flag these as fields that require manual categorization via Mailchimp tags or segments post-migration. Box-level notes and attachments do not migrate to Mailchimp.

Streak Tags are flat labels applied to Boxes for filtering. Tags carry over as Mailchimp tags on the corresponding Audience member. Tags with no Boxes attached are included as empty tag lists for reconstruction in the destination. Mailchimp tags are purely descriptive and do not carry behavioral metadata (when the tag was applied, by whom) from Streak.

Streak Pipelines and Stages define deal progression and have no direct Mailchimp equivalent. We map Pipeline-Stage combinations to Mailchimp Segments using static filter conditions on merge fields (e.g., a 'Sales Qualified' segment based on a custom field). Alternatively, if the customer prefers Groups, we map Stages to Groups within the Audience. The customer chooses the strategy during scoping. Stage history (when a Box moved between stages) is not migratable to Mailchimp's flat subscriber model.

Streak custom Box properties vary per pipeline (dropdowns, text fields, dates, numbers, checkboxes). We discover the full property schema per pipeline during the schema audit, then create corresponding merge fields in the Mailchimp Audience. Date properties map to Mailchimp date merge fields; number fields map to number merge fields; text and dropdown fields map to text merge fields. Mailchimp merge fields are account-level (apply to all members), so any per-pipeline property naming collisions require prefixing or disambiguation during the mapping phase.

Streak Mail Merge Campaigns store recipient lists, email templates, send history, and open/reply tracking data. Recipient lists map to Mailchimp Audiences or Segments. Email template content migrates as Mailchimp template body text (HTML templates require re-creation in Mailchimp's template editor or import as raw HTML). Send history and open/reply metrics do not migrate because Mailchimp does not backfill historical engagement data for imported contacts beyond subscription status. We document the full campaign sequence cadence for the customer's team to rebuild in Mailchimp Customer Journeys.

Streak Snippets are templated email text blocks with merge variables (e.g., {{first_name}}). We export snippet content and variable syntax. Variable naming conventions differ: Streak uses double-brace syntax while Mailchimp uses asterisks around field names (*|FNAME|*). We transform snippet content during export, mapping merge variables to their Mailchimp merge field equivalents. Snippets used as standalone templates require re-creation in Mailchimp's template builder; snippets used as email body fragments can be imported as content blocks.

Streak Tasks are Box-level action items with assignees and due dates. Mailchimp has no task management or activity tracking for contacts. We do not migrate Tasks. We flag the existence of open tasks during scoping so the customer can decide whether to re-create them in a separate task management tool (Asana, Trello, or a native Mailchimp integration with a project tool) or treat the migration as a clean handoff where open tasks are re-opened manually in the destination system.