Migrate from Solitics to HighLevel

Solitics user profiles containing attributes, transaction history, and behavioral event aggregates map to GoHighLevel Contacts. We export the full profile snapshot including custom attributes, then create corresponding custom fields in GoHighLevel for any non-standard attributes. The Solitics profile ID is stored in a custom field for reconciliation. Standard fields (first name, last name, email, phone) map directly; behavioral summary data (total deposits, bet count, session duration) maps to numeric custom fields on Contact.

Solitics raw events (registration, deposit, trade, bet, login, and custom event types) map to a GoHighLevel Custom Object named Event_Log. Each event type becomes a record type or tag within the custom object. We export the full event sequence with timestamps, event names, and event properties as structured JSON in a custom field. Because GoHighLevel lacks a native behavioral event log object, the Event_Log custom object provides a searchable audit trail. We recommend organizing events by type for workflow trigger use in GoHighLevel automations.

Solitics segments are live rule-based definitions built from profile attributes and behavioral conditions. We export segment definitions as rule logic rather than static contact lists. In GoHighLevel, segments translate to Tags applied to Contacts at migration time (for static membership) or to Filter Groups used within workflows for dynamic segmentation. The customer chooses which segments to export as static tag sets versus documented filter rules for GoHighLevel workflow recreation.

Solitics user journey definitions including entry conditions, branching logic, delay rules, and channel steps are exported as structured documentation describing each journey's trigger, flow, and actions. GoHighLevel's workflow builder is the equivalent component but uses a different automation model with different trigger types, action blocks, and delay semantics. We do not migrate journeys as executable code. We deliver a written inventory of every active journey with its complete logic tree and a GoHighLevel workflow rebuild recommendation. The customer's admin or a GoHighLevel specialist rebuilds each journey.

Solitics campaigns including content assets, scheduling rules, and audience targets are exported as campaign metadata (name, status, targeting rules) and channel content (email bodies, SMS copy, push notification text). GoHighLevel uses Campaigns (for tracking and attribution) and Workflows (for automation) as separate constructs. We export campaign metadata and content as structured documentation. Channel content (email templates, SMS bodies) is exported as formatted text files for import into GoHighLevel's corresponding asset areas.

Solitics Smart Gamification module stores mission definitions, loyalty point balances, badge and achievement rules, widget configurations, and achievement thresholds as platform-native objects. GoHighLevel has no native gamification module. We export a complete written inventory of all gamification assets including point balances, mission structures, badge definitions, and widget settings. This inventory is handed off to the customer's development team to build equivalent mechanics using GoHighLevel Custom Objects and Workflows or a third-party gamification integration.

Solitics integrations with external systems (trading platforms, sports feeds, bonus engines, back-office databases) are configured connections rather than data records. These do not transfer. We document every active integration including its data flow direction, credentials or endpoint, and trigger configuration. The customer's technical team re-establishes these connections in GoHighLevel using GoHighLevel's API, webhooks, or third-party integration tools (Zapier, Make). We provide a re-integration checklist as part of the migration deliverables.

Content assets from Solitics including email templates, SMS message bodies, WhatsApp templates, and push notification copy are exported as structured text content. Localization settings and A/B test variants are preserved where present. We do not migrate channel sending infrastructure (sender IDs, WhatsApp business account registrations, email sending domains, push certificates) because these are carrier and platform registrations tied to Solitics accounts. We provide a channel audit checklist so the customer can register the compliance stack fresh in GoHighLevel.

Solitics custom event types beyond the standard set are exported with their property field definitions. We map each custom event schema to a GoHighLevel Custom Object with corresponding custom fields matching the original property types. This step requires schema discovery before migration begins because missing a custom event type results in silent data loss for that event category. We run the discovery query against the Solitics API during the discovery phase, cataloging all named event types and their fields.

Solitics built-in analytics, custom KPI dashboards, and campaign performance reports are exported as report definitions and historical data snapshots where accessible via API. GoHighLevel's reporting module provides CRM-based reports, pipeline analytics, and campaign attribution. We deliver a written report inventory describing every Solitics report's metrics, filters, and visualization type. The customer's admin rebuilds reports in GoHighLevel using its report builder or connects a BI tool for equivalent analysis.