Migrate from Synerise to monday CRM

Synerise Profiles are the primary customer identity object and map directly to Monday.com People entities. We extract Profiles via the Profile Management API (89 endpoints), preserving email, first name, last name, phone, and all custom attribute values. Profile tags migrate as Monday.com tag column values. The profile UUID becomes the external_id reference in Monday.com for deduplication. Behavioral attributes (last seen timestamp, event count aggregates) migrate as custom columns on the People board.

Synerise has no standalone Company object — company data lives as profile attributes or Brickworks schema records linked via profile.assigned-to-company events. We extract all profiles with a non-null assigned-to-company link, deduplicate by company identifier, and load into Monday.com's native Companies CRM entity. Company attributes from the linked schema records become custom columns on the Company board. Company-to-People linkage is preserved via Monday.com's relationship between Companies and People.

Synerise segments return true/false membership per profile. We export segment membership as boolean or multi-select flags per Profile. In Monday.com, we map each Synerise segment to either a Status column (if mutually exclusive segments map to a pipeline-like progression) or a Tag column (if segments are non-exclusive labels). The customer chooses the strategy during scoping based on how segments are used in their existing reporting.

Every Synerise custom profile attribute maps to a Monday.com custom column of the equivalent type: text attributes become Text columns, numeric attributes become Numbers columns, dates become Date columns, and multi-value attributes become Tag or Dropdown columns. The critical pre-migration step is auditing every custom attribute name in the source workspace against Monday.com column naming conventions. If a Synerise attribute name uses characters that conflict with Monday.com column requirements, we flag it during scoping for customer decision before migration begins.

Synerise profile tags are free-form string labels that migrate as Monday.com Tag column values. We preserve the complete tag set per Profile in the export and load into the Tag column on the People board. Tag count and individual tag membership are both preserved.

Synerise transaction records contain line items, totals, timestamps, and payment status. Monday.com CRM has a native Deals entity but no native transaction object. We map Synerise Transactions to a custom Deals board in Monday.com, with line items as subitems on the Deal item. The Deal's custom columns carry transaction metadata (total amount, currency, transaction date, payment status). If the customer uses Synerise's transaction events for revenue tracking, we recommend mapping the deal amount to Monday.com's native Deal value field.

Synerise product catalogs export as item feeds from the Data Modeling Hub in CSV or JSON. We import catalog items as records in a custom Monday.com Items board, preserving SKU, name, description, price, and custom catalog attributes as columns. Product feeds used in Synerise's AI recommendation models require the customer to reconfigure recommendation logic in Monday.com after migration; we document the complete catalog structure for that rebuild.

Synerise Automation Hub workflows define trigger nodes, Profile Filter conditions, and multi-channel actions (email, SMS, push, WhatsApp, webhooks). These do not migrate because Monday.com's automation builder uses a different execution model with different trigger types, conditions, and actions. We export every active workflow definition as a JSON node graph with trigger type, conditions, and action configurations documented in a written inventory. The customer's admin uses this inventory to rebuild equivalent automations in Monday.com's Automations 2.0 builder. Active workflow state at cutover cannot be preserved.

Synerise's AI recommendation configurations (personalized, visual similarity, last seen, top items) are trained on catalog feeds and profile event history using proprietary models (BaseModel.ai, Cleora.ai). These models are not exportable. We export recommendation model configurations — thresholds, item feed references, display rules — as a written inventory. Monday.com does not have a native equivalent recommendation engine; the customer must evaluate Monday.ai capabilities or a third-party recommendation tool post-migration.

Synerise Brickworks schemas define arbitrary record structures for any data type. We export schema definitions (field names, types, constraints) from the Data Modeling Hub. Destination schema recreation requires mapping each Brickworks schema to one or more Monday.com boards with equivalent columns. We document the schema-to-board mapping in the migration manifest. Schema definitions that reference external entities (catalogs, profiles) require the customer to configure those relationships manually in Monday.com after migration.