Migrate from Solitics to Odoo CRM

Solitics user profiles aggregate attributes, transaction summaries, and behavioral summaries from all integrated sources into a unified record. We map these to Odoo res.partner records with is_company=True for organizational profiles and is_company=False for individual contacts. Custom profile attributes in Solitics map to res.partner custom fields created via Odoo Studio or a data migration module. Profile-level identifiers (user_id, external_id) are preserved in a custom char field solitics_user_id__c for cross-system audit. Address, phone, and email fields map directly to Odoo's standard partner address fields.

Raw Solitics events (registration, deposit, withdrawal, trade, bet, login, custom actions) are first-class objects in Solitics but have no direct Odoo equivalent. We split the event history into two migration paths: summary statistics attach to res.partner as custom float or date fields (last_deposit_date, total_trade_count, lifetime_deposit_amount), and the full event sequence attaches as mail.message records with a custom event_type field, a serialized event_properties JSON field, and activity_date set to the original Solitics timestamp. Event type enumeration is defined during schema discovery. This approach preserves the behavioral record without forcing Odoo to store millions of raw event rows in mail.message.

Solitics segments are live, rule-based definitions built from profile attributes and behavioral conditions. We export segment definitions as rule logic rather than static lists. Each segment definition is documented as a written rule specification (field, operator, value, and combinator logic) and optionally recreated in Odoo as res.partner.category tags (for tag-based segments) or as ir.rule domain filters (for complex behavioral conditions requiring a custom module). The customer chooses the implementation strategy during scoping.

Solitics campaign metadata, targeting rules, content blocks, and performance history migrate to Odoo crm.lead records (for sales-driven campaigns) and mass.mailing records (for email marketing campaigns). Campaign audience targets are resolved to res.partner record sets via the segment mapping. Content bodies export as mail.template records. Channel-specific assets (WhatsApp templates, SMS bodies, push copy) export as structured content documentation for re-registration in Odoo's mailing module.

Solitics user journeys define automated workflows triggered by events or segment membership, with entry conditions, branching logic, delay rules, and channel steps. These are platform-native automation objects that do not have a common export format or a direct Odoo equivalent. We export complete journey definitions as written specifications (trigger event, condition tree, action sequence, delay configuration, channel assignment) and deliver them as a journey inventory document. The customer's technical team rebuilds journey logic in Odoo using studio workflows, mail.activity.plan, or a custom Python module. We do not migrate journeys as executable code.

Solitics Smart Gamification module stores mission definitions, loyalty point balances, widget configurations, and badge or achievement rules as platform-native objects. These have no Odoo equivalent and do not export as transferable data. We export a full gamification asset inventory documenting every mission, loyalty point rule, widget configuration, badge definition, and achievement threshold. The customer's team rebuilds gamification mechanics in Odoo using custom res.partner fields for point balances, ir.model.data for badge tracking, and Odoo Studio or a custom module for mission and widget logic. This is documented separately from the data migration scope.

Solitics allows teams to define custom event types beyond the standard set. We run a schema discovery pass against the Solitics API before writing any migration map, cataloging every named event type and its property fields. Each custom event type is mapped to a custom field on res.partner (for summary properties) or to a mail.message custom event_type entry (for event sequence). We pre-create the corresponding Odoo custom fields via a data migration module before importing any profile or event data.

Content assets including email templates, SMS message bodies, push notification copy, WhatsApp templates, and in-app widget copy export as mail.template records in Odoo. Localization settings and A/B test variants are preserved as separate template versions. The sending infrastructure (SMS sender IDs, WhatsApp Business Account credentials, push notification certificates, email sending domains) does not transfer and must be re-registered in Odoo's mailing and SMS modules. We provide a channel audit checklist documenting every active sender ID, WhatsApp template ID, and push certificate for the customer's technical team to re-establish.

Solitics integrations with external systems (trading platforms, sports feeds, bonus engines, BI tools, back-office databases) are configured connections, not data records, and do not transfer across platforms. We document every active integration with its data flow direction, endpoint or API configuration, and credential reference. The customer's technical team uses this integration checklist to re-establish connections in Odoo via Odoo's native connectors, Odoo.sh deployment integrations, or third-party middleware such as Zapier or API webhooks.

Solitics built-in analytics, custom KPI dashboards, and campaign performance reports are platform-native reporting objects. We export report definitions and historical data where accessible via the Solitics API. Pre-built Solitics analytics reports are recreated as Odoo ir.ui.view custom report definitions or exported to an external BI tool (such as Odoo's integrated reporting, Metabase, or a data warehouse connection). Report data history migrates as a snapshot for baseline comparison.

Journey owners, campaign managers, and team-level access controls in Solitics are exported as user references tied to Solitics user records. We map these to Odoo res.users by email match. Any Solitics user without a matching Odoo user is held in a reconciliation queue for the customer's admin to provision before record import resumes. Odoo's access rights groups (res.groups) map from Solitics team-level permissions.

If the Solitics migration scope includes any deal or sales opportunity records (such as bonus-triggered offers or high-value customer milestones that function as sales opportunities), these map to Odoo crm.lead records. Solitics does not have a native Opportunity object, but customer implementations sometimes create custom deal tracking that we surface during discovery and map to crm.lead with stage, probability, and expected_close_date fields populated from the source data.