Migrate from Synerise to HubSpot

Synerise profile maps to HubSpot contact. Primary identifier resolves by email — if a Synerise profile has no email, FlitStack flags it for manual review before migration; anonymous profiles (Synerise clientId only) are preserved with a synthetic email prefix for import and flagged for deduplication against existing HubSpot contacts.

Synerise's profile-to-company linkage (assigned-to-company event) becomes a HubSpot contact with a primary company association. Synerise allows multiple companies per profile (N:N); HubSpot supports one primary CompanyId plus Contact Roles on related Deals. We map the most recently assigned company as primary and surface additional companies via contact properties for admin review.

Synerise companies map directly to HubSpot companies. Company attributes (name, city, industry, employee count) map to HubSpot company properties. Synerise company hierarchies (parent/child) map to HubSpot Parent Company ID when present. Companies without contacts are imported with a flag for reconciliation.

Synerise segments are real-time computed lists of profiles matching behavioral rules. HubSpot has no equivalent real-time segmentation engine. FlitStack evaluates each Synerise segment at migration time and imports the resulting profile set as a HubSpot static list. Dynamic re-computation requires rebuilding the segment logic as a HubSpot smart list or workflow-triggered list rule.

Synerise catalogs store items (products, SKUs, pricing, availability) and are used for recommendation engines and offer management. Each catalog item maps to a HubSpot product with name, description, price, and inventory status. HubSpot products are linked to deals via line items, which Synerise handles differently — we create products first, then link them to deals during deal migration.

Synerise behavioral events (page.visit, product.view, product.buy, added-to-cart, push.received, custom events) have no direct HubSpot equivalent. FlitStack classifies Synerise events by type: transaction events become Note records on the contact; communication events (email.sent, push.sent) are stored as HubSpot engagements. Original timestamps, event names, and payload data are preserved in a custom JSON property for reference. Behavioral events are not re-played in HubSpot.

Synerise schemas are flexible data structures created in the Data Modeling Hub — they can store loyalty tiers, subscription data, B2B attributes, or any custom entity. HubSpot custom objects require Enterprise-tier portals and must be created before data loads. FlitStack audits all schemas, creates equivalent custom objects in HubSpot (with field-type mapping for strings, numbers, dates, and booleans), and maps schema-to-object relationships to HubSpot custom object associations.

Synerise's proprietary AI recommendation models (similar items, collaborative filtering, visual similarity, top items) are trained on Synerise's event data and cannot be exported or transferred. We document the active recommendation model configurations (type, parameters, item feed ID) as a reference artifact so your team can evaluate HubSpot's personalization tools or a third-party recommendation engine post-migration.

Synerise Automation Hub workflows use event-triggered node graphs with conditions, filters, and fire-and-forget action nodes. HubSpot workflows use if-then trigger logic with enrollment criteria. The workflow definitions cannot be transferred because the trigger models, node actions, and data context are platform-specific. FlitStack exports Synerise workflow definitions as JSON/PDF artifacts for your HubSpot admin to use as rebuild specifications.

Synerise profiles can store aggregate values and computed expressions (e.g., total lifetime spend, visit count, loyalty score) created via expressions in the Data Modeling Hub. These are computed server-side and stored as profile attributes. We map each aggregate to a HubSpot custom number or currency property, preserving the current value at migration time — the expression itself is not migrated and must be rebuilt in HubSpot via workflow calculations or enrichment tools.