Migrate from Ziggu to Mailchimp

Every Ziggu contact maps to a Mailchimp audience member. Email address is the unique identifier used for deduplication. Contacts without a valid email address are excluded from migration and flagged in the pre-migration audit report. All other contact fields such as name, phone, and custom properties are transferred as merge fields or tags to preserve full profile data.

Ziggu company name maps to the standard Mailchimp COMPANY merge field. If a contact has multiple associated companies in Ziggu, the primary company is used for the merge field and additional companies are added as tags (e.g., 'Company: Acme Corp').

Ziggu projects have no direct Mailchimp equivalent. We tag contacts by their associated project name (e.g., 'Project: Riverside Development') or create a Mailchimp segment filtered by that tag so you can target project-specific campaigns. If multiple projects apply, each is added as a separate tag, allowing segmentation across the entire development portfolio.

Each Ziggu custom contact property (e.g., Unit Number, Selection Status, Survey Score) requires a corresponding Mailchimp merge field to be created before import. Field type mapping: text properties become Mailchimp text fields; date properties become date fields; pick-list properties become dropdown or radio merge fields.

Ziggu contact tags migrate 1:1 to Mailchimp tags on the same contact record. Tags are preserved exactly as named in Ziggu, including any categorization prefixes (e.g., 'Status: Active Buyer'). This ensures that segmentation logic built on tag names in Ziggu maps directly to Mailchimp audience segments without manual renaming.

Ziggu does not natively track GDPR-style consent timestamps, but if your Ziggu setup includes a consent property or registration date, we preserve it as a custom datetime merge field (OPTIN_DATE__c) in Mailchimp for compliance segmentation. This field enables you to filter contacts based on when consent was given, supporting GDPR and CAN-SPAM compliance requirements.

Ziggu conversation threads and client messaging history do not migrate. Mailchimp has no concept of threaded conversation storage. If message content is business-critical, export Ziggu conversations as a PDF report separately — FlitStack can include this as a companion deliverable but it is not a Mailchimp contact import.

Ziggu documents and file attachments have no Mailchimp equivalent. Files stored in Ziggu cannot be migrated into Mailchimp. We recommend downloading the full Ziggu document library as a ZIP archive before migration — this is outside the scope of the Mailchimp contact migration but we can coordinate timing.

Ziggu approval workflows and task records are project-management constructs that do not translate to Mailchimp. Task ownership and approval status in Ziggu are not surfaced in Mailchimp — those processes must be re-established using Mailchimp's customer-journey automations if desired. This ensures that your team can rebuild approval logic in Mailchimp using triggers such as tag additions or field updates.

Ziggu survey responses stored as contact properties map to Mailchimp merge fields (for numeric or text responses) or tags (for categorical responses like NPS detractor/promoter). NPS scores can also be stored as a number merge field for segmentation. This mapping preserves survey insights and enables targeted campaigns based on respondent categories.

Ziggu phone numbers map to the standard Mailchimp PHONE merge field. SMS marketing consent must be handled separately — Mailchimp requires explicit SMS opt-in that is independent of email consent tracked in Ziggu.

For property developers, Ziggu stores which unit a client is associated with. This maps to a custom UNIT merge field in Mailchimp (e.g., 'Unit 4B, Riverside'). If a contact is associated with multiple units, additional units are added as tags. This approach lets you segment by unit for targeted launch announcements and post-handover communications.