Migrate from Solitics to HubSpot

Solitics visitor profiles map 1:1 to HubSpot contacts. Each Solitics profile ID is stored as Source_System_ID__c for traceability and to support delta‑run de‑duplication. Email address serves as the primary key for matching, with first name, last name, phone, and other standard contact fields transferred directly. Original create timestamps are preserved in a custom date field (original_create_date__c) to maintain historical context. All mapping adheres to HubSpot's field‑type constraints.

Solitics company or brand associations attached to a profile map to HubSpot companies. The original Solitics company identifier is preserved as a custom property (solitics_company_id__c) for reference. HubSpot's native company‑contact association model replaces Solitics' internal linking, and we transfer standard company fields such as name, domain, industry, phone, city, and country. After migration, contacts are linked to their corresponding HubSpot company records automatically.

Solitics behavioral scores and attributes (engagement frequency, deposit totals, tier level) have no native HubSpot equivalent. For each attribute we create a matching HubSpot custom property — number for scores, currency for amounts, pick‑list for tiers — and preserve the Solitics attribute name in the property description. We validate that values conform to the defined field type and that pick‑list options exist in HubSpot before writing the data.

Solitics dynamic segments don't transfer as live segments. We export each Solitics segment’s membership at migration time and create a corresponding HubSpot static list, using the original segment name as the list name. The list receives all contacts that belonged to the segment. Dynamic segment logic — behavioral rules that continuously re‑evaluate — cannot be replicated in HubSpot and must be rebuilt with HubSpot list filters or workflows after migration.

Solitics event‑level history (deposits, trades, actions) is aggregated and stored as custom properties on the HubSpot contact record — totals, counts, and most recent timestamps for each event type. The raw event stream is serialized into a JSON blob and written to a long‑text custom field (event_log__c) for audit purposes. Where possible, we also create engagement timeline entries summarizing key activity so the contact’s timeline reflects the most important actions.

Solitics user journeys and automated campaign flows have no HubSpot equivalent. We export the journey definitions as a document (JSON or CSV) listing trigger events, audience filters, and channel steps. The journey audience — contacts and segment memberships — migrates to HubSpot contacts and static lists. The trigger logic, branches, and channel integrations (in‑app, push, SMS, WhatsApp) must be rebuilt in HubSpot Workflows or a separate CDP layer after migration.

Gamification mission status, loyalty tier, points balance, and badge data are migrated as custom contact properties (mission_status__c, tier_level__c, loyalty_points__c, badge_data__c) and attached as note attachments on the HubSpot contact. The interactive Solitics gamification UI — widgets, mini‑games, and real‑time progress triggers — has no HubSpot counterpart and cannot be transferred. The migrated data provides a reference baseline for rebuilding loyalty logic in HubSpot or a separate gamification platform after migration.

Solitics user and owner assignments are resolved by matching the owner email address to a HubSpot user. Unmatched owners are flagged in a pre‑migration exception report; your team can either invite them to HubSpot or assign a fallback owner before the run. No contact migrates without a valid HubSpot owner, and company records inherit the owner of their primary contact when available. The mapping is logged for audit purposes.

Solitics file attachments are downloaded and re‑uploaded to HubSpot Files, preserving the original file name. Each file is attached to the corresponding HubSpot contact or company record via the file‑association API. Standard HubSpot file size limits (25 MB per file) apply. If Solitics stores files externally (S3, CDN), we retrieve them via temporary download links during migration.

Solitics custom data types or extended profile fields are mapped to HubSpot custom properties on the appropriate object (Contact, Company, or Deal). If Solitics uses a custom object with relationships to contacts or companies, we evaluate whether HubSpot custom objects (Enterprise) can represent the entity or a junction‑object approach is needed. Mapping decisions are documented, and any required custom object schema is created before load.