Migrate your Solitics data

User profiles in Solitics aggregate attributes, transaction history, and behavioral events from all integrated sources into a unified record. We export the full profile snapshot including custom attributes, lifecycle stage, and computed scores. Schema mapping handles naming differences between the source system and Solitics' profile field conventions.

Raw events (registration, deposit, withdrawal, trade, bet, login, custom actions) are first-class objects in Solitics. We preserve the full event sequence with timestamps and event properties. Events that use non-standard event naming conventions require field-level mapping before import into the destination system.

Segments in Solitics are live, rule-based definitions built from profile attributes and behavioral conditions. We export segment definitions as rule logic rather than static lists, allowing the destination to reproduce the same targeting criteria. Complex nested segment conditions are translated into equivalent expressions for the target platform.

User journeys define the automated workflows triggered by events or segment membership. Journey definitions, including entry conditions, branching logic, delay rules, and channel steps, are exported as structured configuration. Any journey steps referencing Solitics-native gamification mechanics or widgets must be re-implemented in the destination platform using its equivalent components.

Campaigns are containers for content assets, scheduling, and audience targets. We export campaign metadata, targeting rules, content blocks, and performance history. Channel-specific content (WhatsApp templates, SMS scripts, push copy) is preserved as content, but channel delivery configuration must be re-established at the destination.

Solitics' Smart Gamification module stores mission definitions, loyalty point balances, widget configurations, and badge/achievement rules. These are platform-specific configurations that do not have direct equivalents in most destination systems. We export the full rule definitions so the destination team can re-implement the mechanics in their chosen tool.

Content assets — email templates, SMS message bodies, push notification copy, WhatsApp templates, in-app widgets — are exported as structured content. Localization settings and A/B test variants are preserved. Channel-level configuration (sender IDs, opt-in compliance settings) must be re-established at the destination due to regulatory and provider-specific requirements.

Solitics' integrations with external systems (trading platforms, sports feeds, bonus engines, BI tools) are configured connections rather than data objects. These are not migrated — they are re-established in the destination platform by the customer's technical team after migration is complete.

Solitics allows definition of custom event types beyond the standard set. We export all custom event definitions and their property schemas. Mapping to the destination platform's event model requires a schema discovery pass before the migration to identify all non-standard event types in use.

Solitics provides built-in analytics, custom KPI dashboards, and campaign performance reports. We export report definitions and historical data where accessible via API. Pre-built Solitics analytics reports do not transfer directly to BI platforms, but the underlying data can be re-platformed for reconstruction.

Journey owners, campaign managers, and team-level access controls are exported as user references. Because Solitics uses an internal user model, we map these to the destination's user and role structure. Permissions must be manually reviewed post-migration.