Migrate from Solitics to Nutshell

Solitics user profiles aggregate attributes, transaction history, and behavioral data from all integrated sources into a unified record. We split each Solitics profile into a Nutshell Person record (individual contact data, email, phone, custom behavioral attributes) and a corresponding Nutshell Account record (company-level data from the profile's organization fields). The split direction is determined by whether the Solitics profile has an identifiable organization; solo profiles land as Person only. Custom behavioral attributes from Solitics that have no standard Nutshell field are pre-created as custom fields on the Person object before migration.

Solitics Company objects map directly to Nutshell Account records. The organization name, domain, address, and any custom fields migrate as-is to Account. Account is created before Person import so that the Person-Account relationship is satisfied at the moment of Person insert.

Solitics behavioral events (registration, deposit, withdrawal, trade, bet, login, and any custom event types) have no native equivalent in Nutshell's data model. We pre-create custom fields on the Person object for key event type counts and last-event timestamps, and we write the full event sequence as Task records with the event type stored in a custom Activity Type field. This preserves the behavioral timeline against the correct Person record for audit and reporting purposes. The Solitics event property fields map to custom fields or the Task description.

Solitics custom event types are discovered during the schema phase via the Solitics API event catalog. Each custom event type and its property fields are mapped to a corresponding custom field on Nutshell Person, with the property data type guiding the Nutshell field type selection (text, date, number, currency, or checkbox). Custom event schemas with nested or array properties are flattened into delimited string fields with the structure preserved in the field description for future reference.

Solitics segments are live, rule-based definitions built from profile attributes and behavioral conditions. Nutshell does not have a segment concept; instead, we translate Solitics segment definitions into Nutshell Saved Filters on the People list. Each filter captures the equivalent attribute conditions (field, operator, value) in Nutshell's filter syntax. The original Solitics segment rule logic is preserved in the filter description field for documentation. Segment membership itself is not a migrated data object but a reporting construct rebuilt through filtering.

If the Solitics account uses deal-like records (e.g., subscription, order, or high-value transaction objects), these map to Nutshell Deals. The Solitics deal stage or status property maps to Nutshell Deal stage, and any monetary value fields map to Nutshell's value fields. Pipeline assignment from Solitics maps to a Nutshell pipeline that we configure before migration.

Solitics journey owners, campaign managers, and team-level access controls are exported as user references. We match by email against Nutshell's User table. Any Solitics owner without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before Person and Account import resumes.

Solitics campaigns are containers for content assets, scheduling, and audience targets. Nutshell does not have a native campaign object beyond reporting attribution. We export campaign metadata and targeting rules as structured documentation, and we create Nutshell Saved Filters matching the campaign audience where applicable. Channel-specific content blocks migrate as text assets in a campaign documentation file for the customer to recreate in Nutshell or their email sending tool.

Solitics user journeys define automated workflows triggered by events or segment membership. Nutshell does not have a journey or workflow automation engine equivalent. We export journey definitions including entry conditions, branching logic, delay rules, and channel steps as a structured configuration inventory. The customer uses this document to rebuild equivalent automation logic in Nutshell or a connected tool.

Solitics Smart Gamification module stores mission definitions, loyalty point balances, badge rules, widget configurations, and achievement thresholds as platform-native objects. Nutshell has no gamification module and no loyalty or achievement data model. We export the full gamification configuration as structured documentation listing every mission, point balance, badge definition, and widget setting. The mechanics must be rebuilt by the customer's technical team in their new platform or a dedicated loyalty tool.