Migrate from Solitics to Microsoft Dynamics 365 Sales

Solitics user profiles aggregate attributes, transaction history, and behavioral events from all integrated sources into a unified record. We split these into Dynamics 365 Contact (primary profile attributes and contact methods) and Account (company and organizational context). Custom profile attributes map to Contact custom fields (__c suffix) pre-created in the destination environment. The profile's primary identifier becomes the Contact's external ID field for dedupe validation during import.

Raw events (registration, deposit, withdrawal, trade, bet, login, and custom actions) are first-class objects in Solitics. We map standard event types to Dynamics 365 Task records with TaskSubtype and custom fields capturing the event name and properties. Custom event types discovered during schema discovery map to a custom entity (e.g., customevent__c) with a relationship to Contact. Event timestamps preserve the original value for timeline ordering. Because Dynamics 365 does not have a native behavioral event model, event property fields (amount, game_id, odds, instrument) become custom fields on the custom event entity rather than a flat key-value structure.

Solitics segments are live, rule-based definitions built from profile attributes and behavioral conditions. We export segment definitions as structured rule documentation with IF-THEN logic trees, not as static contact lists. For active audience-building, segments map to Dynamics 365 Marketing Lists (static) or to Power Automate flows that trigger on Contact create/update with the segment's rule conditions evaluated at runtime. The customer chooses the strategy during scoping based on whether the segment needs to stay live or can be a one-time export.

Solitics User Journeys define automated workflows triggered by events or segment membership, with entry conditions, branching logic, delay rules, and channel steps. We export the complete journey definition including trigger events, condition branches, time delays, and channel action sequence as structured documentation. Microsoft Dynamics 365 Sales does not have a native journey orchestration tool; Power Automate (included in most Microsoft 365 plans) provides the equivalent cloud flow capabilities. We deliver a Journey-to-Flow map with trigger mapping, condition translation, and action equivalence for the customer's admin to rebuild in Power Automate.

Solitics campaigns are containers for content assets, scheduling, and audience targets. We export campaign metadata (name, status, start/end dates, targeting rules) and content blocks as structured data. Channel-specific content (WhatsApp templates, SMS message bodies, push notification copy) migrates as Campaign Content Items linked to the Campaign record. Dynamics 365 Campaign tracks marketing campaign metadata and response tracking; the customer's marketing team rebuilds the scheduling and channel delivery within Dynamics 365 Marketing or a third-party email tool.

Solitics Smart Gamification stores mission definitions, loyalty point balances, widget configurations, and badge/achievement rules as platform-native objects. No common export format exists for these artifacts. We export a full structured inventory of every gamification asset (mission names, point values, badge thresholds, widget layout settings) as documentation for the customer to evaluate for rebuild in a loyalty platform (Microsoft Dynamics 365 Loyalty, a third-party gamification vendor, or a custom Power Apps solution). This asset does not migrate as data.

Content assets — email templates, SMS message bodies, push notification copy, WhatsApp templates — are exported as structured content from Solitics. Email template HTML migrates to Dynamics 365 Email Template records. SMS and push copy migrates as Note records or Knowledge Article draft content for the customer's channel team to re-configure in their communication provider (Twilio, MessageBird, or equivalent) and link to Dynamics 365 via Power Automate. Localization settings and A/B test variants are preserved in the exported asset metadata.

Solitics allows definition of custom event types beyond the standard set. We catalog every custom event schema during the discovery pass, including event name, property names, property data types, and sample values. These become Dynamics 365 custom entities (API name ending in __c) with custom fields matching the property schema. Custom events with behavioral sequences (e.g., multi-step registration flows) map to the custom event entity with a parent Contact lookup and a timestamp for sequencing.

Journey owners, campaign managers, and team-level access controls in Solitics are exported as user references. We match Solitics owner records to Dynamics 365 User records by email address. Any Solitics owner without a matching Dynamics 365 User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Team-level role mappings translate to Dynamics 365 Security Roles assigned to the corresponding User records post-provisioning.

Solitics built-in analytics, custom KPI dashboards, and campaign performance reports are exported as report definitions and historical data where accessible via API. We deliver a written inventory of every Solitics report with its metric definitions, filter logic, and data sources, plus any historical snapshot data exported as CSV. Microsoft Dynamics 365 Sales native reports provide standard sales reporting; for custom KPI reports, we recommend Power BI connected to the Dynamics 365 Dataverse via the Power Platform connector. The customer rebuilds the visualization layer in Power BI using the documented metric definitions.