Migrate from Solitics to Pipedrive

Solitics user profiles aggregate attributes, transaction history, and behavioral events into a unified record. We split this into Pipedrive Person (individual contact data, behavioral attributes, custom fields for event properties) and Organization (company-level data if available in the profile). When Solitics stores both individual and company attributes in the same profile, we use the company's domain or registered name as the Organization dedupe key. Behavioral attributes (deposit frequency, trading volume, session count) migrate as custom fields on Person rather than as event records, because Pipedrive has no native event history object.

Standard Solitics events (registration, deposit, withdrawal, trade, bet, login) cannot be stored as separate records in Pipedrive because Pipedrive lacks an event object. We flatten event summary statistics (lifetime event count, last event timestamp, event frequency averages) into custom fields on the Person record. The customer chooses which event types to summarize during scoping. Event history beyond summary statistics is documented as a data snapshot for analytics rebuild in a BI tool.

Solitics custom event types beyond the standard set require a schema discovery pass before migration. We query the Solitics API to catalog every named custom event type and its property fields, then map those properties to Pipedrive custom fields on Person. The customer defines which custom event properties are most business-critical to preserve as searchable fields. Custom event definitions are preserved as a schema inventory document alongside the migration.

Solitics segments are live, rule-based definitions built from profile attributes and behavioral conditions. Pipedrive does not have a native segment object, so we export segment definitions as rule logic and translate them into Pipedrive filter criteria or custom field values. Segments with simple attribute conditions map to a static custom field value on Person (e.g., High_Value_Trader). Segments with complex behavioral rules are documented as a filter-and-field recipe for the Pipedrive admin to recreate using Workflow Automation triggers.

Solitics Smart Gamification module stores mission definitions, loyalty point balances, badge rules, widget configurations, and achievement thresholds as platform-native objects. Pipedrive has no gamification capability. We export all gamification configuration as a structured inventory document (mission rules, point values, badge definitions, achievement thresholds, widget setup) so the customer's team can evaluate third-party gamification tools or rebuild manually. No gamification data migrates as functional records.

Solitics user journeys define automated workflows triggered by events or segment membership, with entry conditions, branching logic, delay rules, and channel steps. Pipedrive Workflow Automation (Premium and Ultimate tiers) supports record-triggered and scheduled automations with similar action types. We export every active journey as a structured flowchart document with trigger conditions, condition branches, delay durations, and action steps, mapped to equivalent Pipedrive Workflow Automation patterns. The customer's Pipedrive admin or a FlitStack AI automation engagement rebuilds these post-migration.

Solitics campaigns are containers for content assets, scheduling, and audience targets. Pipedrive includes a Campaign object (add-on on all plans, included in Premium and Ultimate) for email and activity tracking campaigns. We export Solitics campaign metadata, targeting rules, and content block summaries. Channel-specific content (WhatsApp templates, SMS bodies, push notification copy) migrates as structured content documentation for re-entry in Pipedrive's Campaign editor. Performance history migrates as campaign notes or custom fields.

Email templates, SMS message bodies, push notification copy, and WhatsApp templates from Solitics are exported as structured content with localization metadata and A/B test variants. Pipedrive's Campaign add-on supports email templates but does not natively support SMS, WhatsApp, or push templates. We deliver the full channel content as structured documentation for the customer to re-enter in Pipedrive or a separate channel tool. Sender IDs, WhatsApp business account registrations, and push certificates require fresh setup in Pipedrive or a dedicated messaging platform.

Solitics journey owners, campaign managers, and team-level access controls are exported as user references. We map these to Pipedrive User by email match. Any Solitics user without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision. Active/inactive status and role assignments (admin, manager, user) are preserved in a custom field for reassignment in Pipedrive's user management.

Solitics integrations with external systems (trading platforms, sports feeds, bonus engines, back-office databases) are configured connections, not data records. These do not migrate. We deliver a complete integration inventory document listing every active integration: source system name, data flow direction, endpoint or credential type, and current configuration. The customer's technical team uses this as a re-integration checklist for Pipedrive's API or Marketplace connectors.

Solitics built-in analytics, KPI dashboards, and campaign performance reports are exported as data snapshots (report definitions, historical values) where accessible via API. Pipedrive Insights covers standard pipeline and activity reporting but does not replicate Solitics' behavioral analytics. We deliver report data as structured CSV exports and a written summary of each Solitics report's metrics so the customer can rebuild in Pipedrive's Insights or a third-party BI tool.