Migrate from Solitics to Freshsales

Solitics User Profiles aggregate attributes, transaction history, and behavioral events into a unified record. We export the full profile snapshot including custom attributes and map the primary contact fields (name, email, phone, address) to Freshsales Contact. Profile IDs are preserved in a custom field solitics_profile_id__c for audit and cross-reference during reconciliation. Any Solitics profile that represents a company rather than a person is mapped to Account instead.

Solitics profiles tagged as company entities or those with business domain attributes (company name, industry classification, employee count) map to Freshsales Account. The solitics_profile_id__c anchor field is set on Account as well for cases where a single Solitics profile contributed to both Contact and Account records.

Solitics raw events (registration, deposit, withdrawal, trade, bet, login, custom actions) with timestamps and event properties are mapped to Freshsales Tasks (for time-bounded activities) and Notes (for event property detail). Events are sequenced by timestamp and linked to the parent Contact or Account via WhoId and WhatId. Because Freshsales has no native event schema registry, event type names and property keys are preserved as text in the Task subject and Note body for searchability. Large event histories (over 50,000 records) are chunked and loaded via Freshsales CSV import with activity-date ordering preserved.

Solitics segments are live, rule-based definitions built from profile attributes and behavioral conditions. We export segment definitions as structured rule logic documentation listing each condition, operator, and value. Freshsales Smart Lists provide equivalent rule-based filtering on Contact and Account fields. The segment logic is translated into Smart List criteria during migration and the customer recreates the list in Freshsales UI. Static segment membership (snapshots of contact lists) is exported as a CSV of contact emails for import as a Freshsales Target List.

Solitics User Journeys define event-triggered automated sequences with branching logic, delays, and channel steps. Freshsales Workflows provide a similar automation surface from Growth plan upward. We export each journey as a structured documentation object listing entry trigger, conditions, branches, delay rules, and channel actions. The customer rebuilds these in Freshsales Workflow Builder using the exported logic as a specification. We do not migrate journey automation as executable code because the trigger models and action types differ between platforms.

Solitics Campaign metadata (name, targeting rules, content blocks, scheduling, performance history) migrates to Freshsales Campaign as structured records. Channel-specific content (WhatsApp message bodies, SMS copy, push notification text) migrates as Campaign content notes. A/B test variants and engagement performance data are preserved as custom fields on the Campaign record for reference. Freshsales Campaign builds audience lists from Contact and Account Smart Lists, which must be established before the campaign data imports.

Solitics Smart Gamification stores mission definitions, loyalty point balances, badge/achievement rules, widget configurations, and achievement thresholds as platform-native objects. These have no export format and no Freshsales equivalent. We export a full inventory of every gamification asset as structured documentation (JSON and CSV) listing mission names, rules, point values, badge definitions, and widget configurations. The customer uses this inventory to rebuild gamification mechanics in a dedicated loyalty platform (LoyaltyLion, Smile.io) or a custom implementation. We explicitly flag this as a non-data-migration scope item during scoping.

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 document them. Where Freshsales supports custom fields on Contact and Account, we create matching custom fields to capture event-derived attributes. For custom event types that represent distinct record classes, we create Freshsales Custom Objects (Enterprise plan) or export as documented schema for the customer to provision post-migration. Any custom event records that cannot be mapped to Freshsales native objects are exported as CSV with schema metadata.