Migrate from Synerise to Zoho CRM

Synerise Profiles are the primary customer identity unit with a lifecycle stage property (subscriber, lead, MQL, SQL, customer, evangelist). We split at migration time: Profiles with lifecycle stage of subscriber or lead map to Zoho CRM Lead; Profiles at SQL and above map to Zoho CRM Contact attached to an Account. The original Synerise lifecycle stage preserves in a custom field syn_lifecycle_stage__c on both Lead and Contact for reporting continuity. Email, first name, last name, phone, and address fields map directly; custom profile attributes audit against Zoho field naming conventions before export because Synerise attribute names are immutable post-creation.

Synerise has no standalone Company object — company data lives as profile attributes or Brickworks schema records linked via profile.assigned-to-company. We extract company name, domain, address, and industry from the profile attribute set and create Zoho CRM Account records. The Account serves as the parent for the Contact migrated from the same Synerise Profile, satisfying the Account-Contact relationship before import.

Synerise Events (product.view, transaction, page.visit, added-to-cart, and 40+ event types) map to Zoho CRM Task with an engagement_type__c custom field holding the original Synerise event name. Transaction events create both a Task record and a Zoho Deal if the event triggers a pipeline stage. Call and meeting events from Synerise's engagement tracking map to Zoho CRM Event with the original timestamp preserved in Activity Date. The full event stream exports from the Behavioral Data Hub in JSON or JSONL and transforms to Zoho Tasks and Events during the staging phase.

Synerise transaction records contain line items, totals, and timestamps. We map the transaction header to a Zoho CRM Deal with Amount, Close Date, and Deal Name. Each line item becomes a Product2 record (if not already present in Zoho) and an Opportunity Product entry on the Deal. Original Synerise transaction IDs preserve in a custom field syn_transaction_id__c for reconciliation.

Synerise Catalogs (product/item feeds) export as CSV or JSON from the Data Modeling Hub. Each catalog item maps to a Zoho CRM Product2 record with Product Code, Unit Price, and Description. A Price Book is created per catalog to preserve pricing tier structure. Item images used by Synerise's visual similarity recommendation engine are flagged as non-migratable because Zoho CRM has no visual similarity AI model — the catalog images migrate as file attachments on Product2 records, and any visual recommendation configuration documents separately for manual Zia setup.

Synerise segment membership exports as true/false flags per Profile. We map these as Zoho CRM Tags applied to the Lead or Contact, or as a custom multi-select picklist field syn_segment__c with the segment names as picklist values. The customer chooses the strategy during scoping based on reporting requirements. Complex segmentation rule logic (expression-based segments) documents separately as Zoho CRM filters or list views.

Brickworks schemas (arbitrary custom record structures in Synerise) map to Zoho CRM Custom Modules. Schema field names, types, and constraints translate to Zoho custom field definitions. The schema definition file exports from the Data Modeling Hub, and we pre-create the corresponding Zoho Custom Module with matching API field names before data import. Lookup relationships defined in Brickworks translate to Zoho lookup fields on the custom module.

Synerise Campaigns (email, SMS, push, WhatsApp, webhook) export via the Campaigns API with audience rules, templates, and scheduling. We map to Zoho CRM Campaign with Campaign Type, Status, Start Date, and End Date. Audience membership (the list of Profiles targeted) migrates as Campaign Member records. Active Synerise campaigns are flagged for re-activation planning because the migration cutover window will interrupt in-progress sends.

Synerise Automation Workflows export as JSON node graphs with trigger conditions, profile filters, and action configurations. They do not migrate as executable code to Zoho Blueprint because Synerise workflows are fire-and-forget and Blueprint uses stage gates. We deliver a written Blueprint rebuild map: trigger equivalence, condition translation, and action node mapping for each active Synerise workflow, with estimated effort per workflow for the customer's admin to rebuild.

Synerise recommendation configurations (personalized, visual similarity, last seen, top items) are trained on catalog feeds and profile event history using proprietary BaseModel.ai and Cleora.ai embedding models. The model weights are not exportable. We document every recommendation configuration (thresholds, item feed references, display rules) in the migration manifest. The destination Zoho CRM instance requires separate Zia setup for equivalent predictions; visual similarity cannot be replicated without a dedicated image embedding pipeline.