Migrate from Gamooga to Microsoft Dynamics 365 Sales

Gamooga User records are the central object holding email, mobile number, and behavioral attributes. We map qualified Users (those with purchase history or active engagement records) to Microsoft Dynamics 365 Sales Contact attached to an Account. Unqualified Users with only marketing touchpoints map to Lead. The split rule is defined during scoping based on the customer's Gamooga data. Original Gamooga user properties (custom attributes uploaded via Historic Data Push) migrate as custom contact or lead fields with data type preserved where identifiable.

If the Gamooga export includes company or organization association per user, we map to Microsoft Dynamics 365 Sales Account. Account is created before Contact import so that the parent Account lookup is satisfied at the moment of Contact insert. The Gamooga company name maps to Account Name; domain or website maps to Website field. If Gamooga does not associate companies to users, we create placeholder Accounts derived from email domain grouping during scoping.

Gamooga Campaigns represent lifecycle or promotional journeys across channels. We map campaign definitions and status to Microsoft Dynamics 365 Sales Campaign records. Campaign Member status (Sent, Viewed, Clicked, Converted) maps to Campaign Member Status. If Gamooga campaign history includes attribution to revenue outcomes, we create Campaign Influence records on related Opportunities in Dynamics. Channel-specific configuration (push template IDs, SMS sender IDs) is migrated as configurable stubs; the customer's Dynamics admin configures the actual channel connector post-migration.

Gamooga dynamic segments use behavioral rules (demographics, purchase history, geolocation, app behavior) evaluated in real time. We extract the rule structure as human-readable criteria during discovery and translate it to Microsoft Dynamics 365 Sales Marketing segment filters. Static segment membership (user IDs belonging to a segment at export time) migrates as a Dynamics static marketing list tied to Contact or Lead. Behavioral rule translation is documented in a written segment inventory; the customer's Dynamics admin rebuilds the dynamic evaluation logic using Dynamics Marketing or Power Automate.

Gamooga Events are behavioral records (page views, purchases, cart actions, feature usage) used to trigger automations. We export event history as Microsoft Dynamics 365 Sales Task records linked to the parent Contact or Account. Event type, timestamp, and key event properties (e.g., product viewed, cart value, page URL) map to custom Task fields. Activity timeline ordering is preserved by setting ActivityDate to the original Gamooga event timestamp. Events that represent transactions (purchase events) may alternatively map to Opportunity Line Items if the event includes revenue data.

Gamooga workflow definitions created on the graphical canvas are documented as structured step sequences in a written handoff inventory. Channel-specific action steps (push template bindings, SMS sender references) are migrated as configurable stubs referencing the original channel parameters. We do not rebuild Gamooga Workflows inside Dynamics because the automation paradigms differ structurally. The customer's Dynamics admin or a Microsoft partner uses the inventory to rebuild equivalent logic in Salesforce Flow or Power Automate post-migration.

Extended user properties uploaded via Gamooga's Historic Data Push migrate as custom fields on Contact, Lead, or Account in Microsoft Dynamics 365 Sales . We preserve data type where identifiable (string, number, date, boolean) and flag any ambiguous typed fields for the customer's admin to resolve. Custom field API names follow Dynamics naming conventions with a __c suffix and are created in the destination org before any data import begins.

Pre-built Gamooga analytics dashboards and real-time insights are exported as static data (CSV or Excel) during discovery. The underlying live-reporting pipeline is not transferable. We deliver the exported report data as a reference file and document the report definitions (metric names, filters, date ranges) so the customer's Dynamics admin can reconstruct equivalent views using Microsoft Dynamics 365 Sales reports, Power BI, or the native analytics workspace.