Migrate from Gamooga to Mailchimp

Gamooga User profiles (email address, mobile number, behavioral attributes, channel preferences) map to Mailchimp Contact records within the primary Audience. We extract all standard profile fields from Gamooga's data export and map them to Mailchimp's required and optional contact fields. Email address is the primary dedupe key. Mobile numbers map to the PHONE merge field type. Channel subscription preferences (email, SMS, push opt-in flags) migrate to Mailchimp's marketing permission fields (EMAIL_OPTOUT, SMS_OPTOUT) based on the customer's data export. Custom user properties become Mailchimp Merge Fields configured in the Audience before import.

Gamooga Campaign records (lifecycle and promotional journeys) map to Mailchimp Campaign records. The campaign name, description, status, and scheduled or sent timestamps migrate as Mailchimp campaign metadata. Campaign content (email templates, body copy, images) migrates as Mailchimp Template assets that the customer rebuilds or uploads from the Gamooga export. Channel-specific campaign configuration (push template IDs, SMS sender IDs) does not transfer because Mailchimp is email-centric and those channel bindings are not applicable.

Gamooga's dynamic Segments are built from behavioral rules (demographics, location, purchase history, app behavior) evaluated in real time. These rules cannot be exported as portable configuration. We extract the segment criteria as human-readable rule documentation and reconstruct equivalent Mailchimp Segments using Mailchimp's filter-based segment builder (static segments using contact field criteria). Behavioral event conditions that have no Mailchimp equivalent (e.g., 'purchased in last 30 days') are noted as segment definitions for manual rebuild. Segment membership is preserved as Tags during migration so that the customer's admin can finalize the dynamic segment logic in Mailchimp.

Gamooga Events (page views, purchases, cart actions, custom behavioral triggers) are behavioral records used to drive omni-channel automation. Mailchimp Contacts have an activity timeline but do not support real-time behavioral event ingestion as first-class objects. We export event history from Gamooga as contact activity notes (text records appended to the contact profile) containing the event type, timestamp, and relevant attributes. This preserves the historical record for audit and reporting but does not activate Mailchimp behavioral triggers. Event-to-note mapping is configurable; the customer chooses which event types to include based on data volume.

Extended user properties uploaded via Gamooga's Historic Data Push become Mailchimp Merge Fields. We infer the data type from the Gamooga export (TEXT, NUMBER, DATE, PHONE) and configure the equivalent Mailchimp merge field type before import. Ambiguously typed fields are flagged in the scoping report for the customer's admin to review and assign a type. Merge fields are scoped per Audience; if the customer uses multiple Gamooga segment structures, we create them in the primary Audience and document secondary Audience setup.

Gamooga Workflow definitions created on the graphical canvas cannot be exported as code or portable configuration. We deliver a written Workflow Inventory document that lists every active Gamooga automation with its trigger conditions, action steps, delay rules, and channel-specific bindings. Channel action steps (push, SMS, in-app) are documented as non-applicable to Mailchimp since those channels are not native. The customer's admin uses this document to rebuild equivalent automations in Mailchimp's Customer Journeys builder. Each workflow typically requires 1-2 hours of rebuild time depending on complexity.

Gamooga pre-built analytics dashboards and real-time reporting are not transferable to Mailchimp. We export available report data (campaign send metrics, open rates, click rates, audience growth) as a static CSV for the customer's records. Mailchimp's own campaign reporting and audience analytics rebuild natively on migrated campaign and contact data post-import. The customer should capture screenshots of Gamooga dashboards before migration cutover for reference.

Gamooga Channels (Push, SMS, Email, In-App, Web Push) are platform-native delivery infrastructure with channel-specific configurations (push certificate bindings, SMS sender IDs, email DKIM settings, in-app notification templates). These are tied to Gamooga's infrastructure and cannot be extracted. Email content and campaign intent migrate as Mailchimp campaign content and template assets. SMS content migrates if the customer enables Mailchimp SMS add-on and provides the sender configuration. Push, In-App, and Web Push channels do not have a Mailchimp equivalent and must be handled separately by the customer's development team if required.