Migrate from Synerise to Microsoft Dynamics 365 Sales

Synerise Profiles are the primary customer identity record and map to Dynamics 365 Contact. Email, first name, last name, phone, and address attributes migrate directly. We preserve the full tag set from Synerise as multi-select picklist fields or custom text fields on Contact. Any Synerise Profile linked to a company via profile.assigned-to-company events requires an Account to exist before Contact insert so that the parent Account lookup is satisfied.

Synerise does not have a standalone Company object — company data lives as profile attributes or Brickworks schema records. We identify company-type profiles and profiles with business email domains and map them to Dynamics 365 Account. The Synerise company name attribute becomes Account Name; any address attributes become Billing Address. Accounts are inserted before Contacts to satisfy the lookup dependency.

Synerise behavioral Events (product.view, added-to-cart, transaction, page.visit, and 40+ other event types) do not have a direct Dynamics 365 equivalent. We transform events into CRM-native Activities: transactional events map to Notes attached to the Contact; engagement events (email opens, link clicks) map to Tasks with custom event-type fields. For high-volume event streams, we may create a custom Dynamics entity (event_history__c) to preserve the full behavioral timeline without inflating the native Activity count.

Synerise transaction records (POST /v4/transactions) containing line items, totals, and timestamps map to Dynamics 365 Opportunity. Transaction total becomes Estimated Revenue on the Opportunity; transaction date becomes Close Date; transaction status maps to a custom field syn_transaction_status__c. We also create Opportunity Products from Synerise transaction line items if the product catalog has been migrated to Dynamics Product2 records.

Synerise Catalogs are product/item feeds used by AI recommendation models. We export catalogs as CSV or JSON and map them to Dynamics 365 Product2 records with Standard Price Book entries. Item codes, names, descriptions, categories, and pricing migrate directly. Note that visual similarity recommendation configurations are NOT migrated — the Synerise proprietary image embedding model is not exportable. We document all recommendation configurations in the migration manifest for the customer to rebuild using Microsoft Dynamics 365 Sales intelligence tools.

Synerise segments are computed true/false membership flags per Profile. We export segment membership as boolean or multi-select fields on Contact (e.g., is_high_value_customer__c, preferred_channel__c). Complex segments with multi-condition rule logic are documented in the migration manifest with their Synerise expression syntax; the customer's Dynamics admin rebuilds these as saved views or advanced find queries.

Brickworks schemas are arbitrary record structures defined in Synerise's Data Modeling Hub. Each schema maps to a Dynamics 365 custom entity (API name with __c suffix). Schema field names, types, and constraints are recreated as custom fields on the destination entity before data import. Cross-schema lookups are preserved as Dynamics lookup fields. Schema definitions (not data) are documented as a separate data dictionary deliverable.

Synerise campaign definitions (email, SMS, push, WhatsApp) are accessible via the Campaigns API. We export campaign configurations including templates, audience rules, and scheduling. Active campaigns at migration cutover cannot have their in-flight state preserved — we document the campaign status and delivery statistics so the customer can decide whether to restart in Dynamics 365 Campaign.

Synerise Automation Hub workflows (trigger nodes, Profile Filter conditions, action configurations) are exported as JSON node graphs and documented in the migration manifest. We do not migrate workflows as code because the fire-and-forget Synerise model does not map to Power Automate's gate-condition model. The customer receives a written inventory of every active Synerise workflow with its trigger, conditions, and actions, and recommended Power Automate equivalents, for admin rebuild post-migration.