Migrate from Gamooga to Freshsales

Gamooga Users (email, mobile number, behavioral attributes) map to Freshsales Contacts. The Gamooga user profile fields migrate as standard and custom Contact fields. Email serves as the unique identifier. We extract custom properties uploaded via Gamooga's Historic Data Push as custom fields in Freshsales, preserving data type where identifiable and flagging any ambiguous typed fields. If the customer uses Gamooga's account-level data model, those records map to Freshsales Accounts with the Contact-Account relationship established via domain matching.

Gamooga Campaigns (lifecycle or promotional journeys across channels) map to Freshsales Deals. Campaign status (active, paused, completed) migrates as Deal stage; campaign targeting rules and channel configuration migrate as custom fields or deal notes rather than native Freshsales configuration. Channel-specific bindings (push template IDs, SMS sender IDs) do not migrate and are documented as configuration to rebuild in Freshsales workflow builder.

Gamooga dynamic Segments use behavioral rules (demographics, location, purchase history, app behavior) evaluated in real time. These rule definitions cannot be exported as portable configuration. We extract the rule structure as human-readable criteria and document it as Freshsales filter view definitions that the customer's admin can recreate in Freshsales's Contact filter builder. Any behavioral data attributes present in Gamooga but absent from the Freshsales Contact schema are flagged as potential custom field additions.

Gamooga Events (page views, purchases, cart actions, custom behavioral records) used to trigger automations migrate as Freshsales Activity records (Tasks). Event type maps to Activity subject or a custom field; event timestamp maps to ActivityDate; event properties migrate as custom Task fields. Because Freshsales does not have a native behavioral event schema, we preserve the event data as structured activity records with a custom event_type__c field to maintain categorization.

Gamooga workflow definitions created in the graphical canvas are documented as step sequences with trigger conditions, branching logic, and action types. We do not migrate workflows as executable code because Gamooga's automation engine and Freshsales's workflow builder are architecturally different. We deliver a written inventory of every active Gamooga workflow with its trigger, conditions, actions, and recommended Freshsales workflow equivalent for the customer's admin to rebuild post-migration.

Extended user properties uploaded via Gamooga's Historic Data Push migrate as Freshsales custom contact fields. We pre-create the destination fields in Freshsales with matching data types (text, number, date, dropdown) before contact import. Ambiguously typed properties are flagged for the customer to clarify before field creation. The Freshsales admin creates these fields under Admin Settings > Contact Fields before migration data is loaded.

Pre-built Gamooga analytics dashboards and real-time insights export as static data snapshots. The underlying live-reporting pipeline is not transferable and must be reconstructed in Freshsales's reporting module post-migration. We deliver the export data in CSV format alongside a report reconstruction guide mapping Gamooga metrics to Freshsales equivalent report types.

Gamooga Channels (Push, SMS, Email, In-App, Web Push) are delivery infrastructure specific to Gamooga's platform and do not have equivalents in Freshsales. We do not migrate channel configurations. Any audience or contact list data within a channel migrates through the User-to-Contact mapping. Channel-level content and templates must be rebuilt in Freshsales or a separate marketing tool.