Migrate from Groundhogg to Mailchimp

Groundhogg Contacts map to Mailchimp Audience Members. The email address is the primary key and dedupe field. Standard properties (first name, last name, phone, address) map to Mailchimp Merge Fields FNAME, LNAME, PHONE, and the address merge fields. Any contact without a valid email address is held in a skip queue and reported separately because Mailchimp does not allow members without email.

Groundhogg's tag-based taxonomy maps directly to Mailchimp Tags. Tags are exported as a flat list per contact and applied to the corresponding Mailchimp Member. Groundhogg does not store tag hierarchy; Mailchimp Tags are similarly flat, so no structural transformation is required. Tag names are preserved exactly as they appear in Groundhogg. Contacts with multiple tags receive all tags in Mailchimp.

Groundhogg custom fields map to Mailchimp Merge Fields. Text fields map to Mailchimp text type, date fields to date type, number fields to number type, and dropdown/choice fields to dropdown or radio merge field types. Groundhogg multi-checkbox fields map to Mailchimp address or text fields depending on the data. We pre-create the merge field schema in the destination Mailchimp Audience before importing any members so that field data is written on first pass.

Groundhogg Broadcast metadata (subject line, send date, recipient count) is exported as a documentation record. Mailchimp does not store sent broadcast history as a distinct object that can be imported from an external source. We document the broadcast history as a CSV that the customer's admin can reference when building new Mailchimp Campaigns. Recipients who received a broadcast in Groundhogg are already present as Members and receive their engagement data in Mailchimp going forward.

Groundhogg activity logs (email opens, link clicks, form submissions, tag applied/removed) are exported per contact and stored as a contact-level activity history document in the migration artifact. Mailchimp tracks engagement at the campaign level (open, click, bounce, unsub) per member rather than as a per-event activity log. We preserve the activity timestamp and event type as a JSON log attached to the contact record so that the customer's admin has a reference file even though the activity does not render as a native timeline in Mailchimp.

Groundhogg contact-level Notes map to a dedicated Note Merge Field in Mailchimp (type: text, long) or are exported as a CSV log paired to the Member by email address. Mailchimp does not have a native Notes object on Members. We recommend creating a dedicated Merge Field (e.g., GH_NOTES) to hold the most recent note content, with the full note history preserved in the migration artifact CSV for the admin to reference or import into a connected knowledge base tool.

Groundhogg Companies (available in Plus and above) have no Mailchimp equivalent. Mailchimp is an audience-centric platform without an Account or Company object. We export Companies as a documented CSV with company name, address, phone, and associated contact email addresses. The customer's admin decides whether to incorporate company data into a CRM adjunct, into Mailchimp Merge Fields on the Member record, or to handle it as a separate reference document.

Groundhogg Deals and Pipeline Stages (Pro tier and above) have no Mailchimp equivalent. Mailchimp does not support a deal, opportunity, or pipeline object. We export Deals with stage name, deal value, close date, and associated contact email as a documented CSV. The customer may incorporate deal data into a connected CRM (e.g., HubSpot, Salesforce, or a lightweight CRM) post-migration, or document the pipeline structure as a reference for a future CRM implementation.

Groundhogg Flows cannot be exported as reusable automation templates via the REST API. We export the Flow trigger type, step count, step names, and step sequence as a written automation audit document. The customer's admin uses this document to rebuild equivalent Customer Journeys in Mailchimp. Mailchimp Customer Journeys use a trigger-action model (e.g., 'joins audience' → 'wait 3 days' → 'send email') that differs structurally from Groundhogg's conditional branching builder, so the rebuild is manual and not automated by FlitStack AI.

Groundhogg maps contacts to WordPress user IDs as owners. Mailchimp does not have an Owner or User assignment model on Members. We do not migrate owner assignments. If the customer needs team-member attribution on contacts post-migration, we recommend adding a dedicated Merge Field (OWNER_EMAIL) or connecting Mailchimp to a CRM where ownership is a first-class object.