Migrate from Solitics to Salesforce Sales Cloud

Solitics User Profiles aggregate attributes, transaction history, and behavioral events into a unified record. We split these into Salesforce Leads (for profiles with no established business relationship or low engagement score) and Contacts attached to Accounts (for profiles with a verified identity, transaction history, or explicit opt-in). The split rule is defined during scoping based on your Solitics segment criteria and business type (B2C vs B2B). We preserve the original Solitics profile ID in a custom field politics_profile_id__c for reconciliation and cross-reference.

For B2B use cases within Solitics (e.g., trading firm accounts, corporate gaming operator relationships), User Profiles that represent organizations rather than individuals map to Salesforce Account. The Solitics profile's company-level attributes (domain, segment tier, revenue tier) become Account fields. Individual users within that organization migrate as Contacts linked to this Account via the AccountId lookup.

Solitics event records (deposits, trades, bets, registrations, logins, custom actions) map to Salesforce Task or Event based on event type. Timed events (trades, bets, deposits) map to Event with StartDateTime and EndDateTime set to the event timestamp and a 1-second duration. Discrete actions (registration, login, custom events) map to Task with ActivityDate set to the original timestamp and event properties preserved in custom Task fields (event_type__c, event_properties__c as JSON). We use the Salesforce Bulk API 2.0 with batch chunking for large event histories because a single Solitics account can contain millions of event records that exceed CSV loader capacity.

Solitics segments are live rule-based definitions built from profile attributes and behavioral conditions. We export segment definitions as structured rule logic (AND/OR conditions, attribute operators, time windows). In Salesforce, segments are rebuilt as Campaign membership from a static Campaign List (generated by querying migrated Contact/Lead records against the segment rule criteria) or as a Salesforce Flow that evaluates segment membership on a scheduled basis. The segmentation strategy is agreed during scoping because Salesforce does not have a native live segment engine equivalent to Solitics.

Solitics User Journeys define automated workflows triggered by events or segment membership, including entry conditions, branching logic, delay rules, and channel steps. These are platform-native workflow definitions that do not have a standard export format. We export journey definitions as structured documentation listing every active journey, its trigger, conditions, branches, delays, and channel actions. The customer's Salesforce admin or a Flow developer rebuilds these using Salesforce Flow, Marketing Cloud Journey Builder (if Marketing Cloud is licensed), or a combination of both depending on channel requirements.

Solitics Campaigns are containers for content assets, scheduling, and audience targets. We export campaign metadata (name, status, start/end date, targeting rules) and content blocks as structured data. Channel-specific content (WhatsApp templates, SMS bodies, email HTML) migrates as Salesforce EmailTemplate, ContentDocument, or custom rich-text fields depending on channel. A/B test variants and localization settings are preserved in a campaign audit document.

Solitics Smart Gamification stores mission definitions, loyalty point balances, badge and achievement rules, widget configurations, and achievement thresholds as platform-native objects. There is no common export format for gamification mechanics. We deliver a full gamification inventory document listing every active mission, loyalty tier, point balance rule, badge definition, and widget configuration. Your technical team rebuilds these mechanics using Salesforce Flow, a loyalty AppExchange package, or a custom Force.com site. Point balances from Solitics can be imported as a custom field on Contact or Account for reference during the rebuild.

Channel assets in Solitics include email templates, SMS message bodies, push notification copy, WhatsApp templates, and in-app widget content. We export these as structured content documents with metadata (template name, channel, language, A/B test variants). Email templates migrate as Salesforce EmailTemplate records. SMS and push content migrate as custom rich-text fields on Campaign or a custom object because Salesforce Sales Cloud does not have a native SMS send capability; customers typically pair with Salesforce Marketing Cloud or a third-party SMS AppExchange connector for outbound messaging.

Solitics allows teams to define custom event types beyond the standard set. We run a schema discovery query against the Solitics API during the discovery phase to catalog every active custom event type and its property fields before writing any migration map. Each custom event schema becomes a Salesforce Custom Object (with __c API suffix) containing the event's property fields as typed Custom Fields. Custom event records from Solitics import into these Custom Objects with the original timestamp, event type, and all property values preserved. Missing this discovery step results in silent data loss for any event that falls outside the standard event types.

Solitics integrations with external systems (trading platforms, sports feeds, bonus engines, back-office databases, BI tools) are configured connections rather than data records and do not transfer across platforms. We document every active integration including its data flow direction (inbound/outbound), credentials or endpoint, trigger or polling configuration, and the Solitics object it populates. Your technical team uses this integration audit checklist to re-establish each connection in Salesforce using REST API integrations, MuleSoft, a middleware tool, or the relevant AppExchange connector.

Solitics built-in analytics, custom KPI dashboards, and campaign performance reports export as report definitions and metadata. We preserve the report structure, metric definitions, and available historical data accessible via API. Pre-built Solitics analytics dashboards do not have a direct Salesforce equivalent because Salesforce Reports use a different dimensional model. We deliver a report mapping document that pairs each Solitics report with the closest Salesforce standard report type and the custom report type or Analytics Cloud dashboard that would replicate the same insight.

Journey owners, campaign managers, and team-level access controls in Solitics are exported as user references by email. We resolve each Solitics owner reference to a Salesforce User record by email match. Any Solitics owner without a matching Salesforce User goes to a reconciliation queue for your admin to provision before record import proceeds. Access control mappings (team-level permissions, role assignments) are documented as a permissions matrix for your Salesforce admin to configure in Profiles and Permission Sets post-migration.