Migrate from Gamooga to Twenty CRM

Gamooga User profiles (email, mobile number, behavioral attributes) map directly to Twenty CRM Person records. We extract all standard profile fields and extended properties uploaded via Gamooga's Historic Data Push, mapping each to a Twenty Person field or custom field. The Person's primary email becomes the dedupe key during import. If the Gamooga User has an associated Company name in behavioral data, we create a Company record first and link the Person via the PersonCompany关系的 foreign key.

Gamooga does not have a native Company object but associates Users with company identifiers through behavioral events (company name, domain, employee count). We extract company-level data from User attributes and behavioral event payloads, deduplicate by domain, and create Twenty CRM Company records. Company becomes the parent record before Person import, satisfying the lookup dependency that Twenty enforces.

Gamooga Campaigns represent lifecycle or promotional journeys across channels. We map Campaigns to Twenty CRM Opportunities, preserving campaign name, status (active, paused, completed), start and end dates, and target audience size as Opportunity metadata. The channel-specific delivery configuration (push template IDs, SMS sender IDs) does not migrate; we flag these as configuration stubs requiring manual setup in Twenty's notification or integration layer.

Gamooga Campaign audience membership links specific Users to a Campaign. We migrate this as a lookup relationship: each User in the campaign audience receives a link to the corresponding Opportunity record via Twenty's custom field or via an OpportunityPerson mapping table. The audience count per campaign is preserved as a custom field on the Opportunity for reporting.

Gamooga dynamic Segments use behavioral rules (demographics, location, purchase history, app behavior) evaluated in real time. These rule definitions are not exportable as portable configuration. We extract the segment rule structure as human-readable criteria (field, operator, value) and deliver it as a written specification document. The customer's admin rebuilds equivalent filters in Twenty using its filter and view system. Where segments represent static lists, we create Tags on the corresponding Person records.

Gamooga Events are behavioral records (page views, purchases, cart actions, custom events) used to trigger automations. We export event history as Activity records in Twenty CRM, mapping event type to Activity subject, event timestamp to ActivityDate, and event properties to custom Activity fields. Large event histories are chunked for Twenty's API rate limits (100/min free tier, 200/min paid tier). Not all behavioral event attributes have equivalents in Twenty's activity schema; we flag unmapped attributes in the discovery report.

Extended user properties uploaded via Gamooga's Historic Data Push migrate as custom fields on the relevant Twenty CRM object. We preserve the original data type where identifiable (text, number, date, boolean) and create matching custom fields via Twenty's /metadata API before import. Ambiguously typed fields (e.g., JSON blobs or freeform text used as structured data) are flagged for manual review during scoping.

Gamooga workflows created on the graphical canvas are migrated as structured step-sequence documentation. Each workflow's trigger, conditions, branches, delays, and channel actions are captured in a written inventory delivered to the customer. Channel-specific action steps (push template bindings, SMS sender IDs) cannot migrate. Twenty CRM workflows are available on paid tiers and must be rebuilt manually post-migration using the documented step sequence as a reference.

Pre-built analytics dashboards and real-time insights are exported as static CSV or JSON data where accessible from Gamooga's dashboard. The underlying live-reporting pipeline does not transfer. We deliver the historical report data as structured files and note which report types (funnel analysis, cohort analysis, campaign attribution) require reconstruction in Twenty's dashboard or a third-party BI tool.

Gamooga Channels (Push, SMS, Email, In-App, Web Push) are platform-native delivery infrastructure. These do not migrate. We document the channel configurations as reference for the customer's admin to reconfigure in their chosen notification provider (e.g., Braze, OneSignal, Postmark, Twilio) and connect to Twenty via webhook or Zapier.

Gamooga's dynamic recommendation engine is platform-native and tied to its predictive analytics layer. Recommendation model outputs and algorithmic configurations do not export. We document the recommendation use cases (product recommendations, content personalization) as functional requirements for rebuilding in the destination platform or a specialized recommendation engine.