Migrate from Pipz to Mailchimp

Pipz Contacts map to Mailchimp Audience members. Email address serves as the dedupe key. Standard fields (first name, last name, phone, address) map directly to Mailchimp merge fields (FNAME, LNAME, PHONE, ADDRESS). Custom fields on Pipz Contacts migrate to Mailchimp merge fields (text, number, date, dropdown types supported). The Customer Engagement Index migrates as a numeric merge field since Mailchimp has no native behavioral scoring. Unsubscribe status from Pipz transfers to Mailchimp's Global Unsubscribe list to preserve suppression state and protect deliverability.

Pipz Companies have no direct Mailchimp equivalent. Mailchimp does not maintain a Company or Account object natively. We flag Company records for mapping into a connected CRM (Salesforce, HubSpot, Pipedrive) via Mailchimp's integration layer, or document them for manual entry if no CRM is in scope. Company name and domain can be stored as merge fields on Contact records as a workaround, but this is not the recommended long-term approach for companies with many contacts per organization.

Pipz Deals (sales opportunities with pipeline stages and values) have no Mailchimp equivalent. Mailchimp is not a CRM and does not track deals, pipeline stages, or opportunity values. We flag Deal records in the scoping document with their stage, owner, value, and close date, and recommend mapping them to a dedicated CRM (Salesforce Sales Cloud, HubSpot, Pipedrive, or a CRM add-on within Mailchimp's ecosystem). This is a migration gap that must be addressed separately from the Mailchimp migration scope.

Pipz Pipeline Stages are CRM-specific workflow stages that do not exist in Mailchimp. We document the pipeline structure (stage names, ordering, probability mapping) for handoff to the customer's CRM administrator or integration partner. If the customer plans to connect Mailchimp to a CRM, the pipeline structure can be replicated there rather than in Mailchimp.

Pipz Email Campaigns map to Mailchimp Campaigns with campaign metadata (name, subject, send date, recipient list) preserved. Campaign performance metrics (open rate, click rate, bounce rate) do not transfer as live reporting data in Mailchimp because reporting is calculated on Mailchimp's platform for sends executed within Mailchimp. We map campaign history as a static record in a custom merge field or linked document for historical reference. Email templates from Pipz migrate as HTML files for manual upload to Mailchimp's template builder.

Pipz Smart Segments (built from demographic, tag-based, and behavioral rules) migrate as Saved Segments in Mailchimp using rule-based conditions. The underlying segmentation logic (field equals, contains, is one of) maps to Mailchimp's segment condition syntax. Complex Pipz segments built from multiple nested conditions may require simplification because Mailchimp's segment builder has different logic operators. We document each Pipz segment definition and flag any rules that require manual recreation in Mailchimp's segment builder.

Pipz Tags migrate to Mailchimp Tags on the corresponding Audience member. Tags are flat-labeling mechanisms in both platforms and map 1:1 by name. Tag associations on Pipz Contacts transfer as Mailchimp Tags on the corresponding Audience contact. Tags applied across Pipz Companies, Deals, and Campaigns do not transfer because Mailchimp Tags are contact-level only; we document cross-object tag usage for admin review.

Pipz Activities capturing email opens, link clicks, and automation events migrate to Mailchimp's activity tracking via API if the Mailchimp API exposes activity history for re-import. Email engagement events (opens, clicks) from Pipz do not generate new Mailchimp engagement records because they originated from Pipz, not Mailchimp. We document the activity volume and event types in the handoff document; live engagement history in Mailchimp starts from the date of first send in Mailchimp.

Pipz Custom Fields on Contacts map to Mailchimp Merge Fields. Field types translate as follows: text maps to text merge field, number maps to number merge field, date maps to date merge field, dropdown and radio options map to radio or dropdown merge fields. Boolean fields map to text merge fields with Y/N values. Required field settings in Pipz do not auto-apply in Mailchimp; we document required-field requirements for admin configuration post-migration.