Migrate from Synerise to Twenty CRM

Synerise Profiles are the primary customer identity unit and map directly to Twenty CRM's Person object. Default attributes (email, firstName, lastName) map to standard Twenty Person fields. Custom profile attributes require a pre-migration audit to identify conflicts with Twenty's reserved field names. Synerise's reserved attribute names cannot be used as custom field names on Twenty either — we cross-reference and rename before import. The profile.assigned-to-company event must be processed to link each Person to the correct Company record.

Synerise has no standalone Company object — company data lives as profile attributes or schema records in Brickworks. We extract company information from the profile.assigned-to-company event and any Brickworks company schema records, then create Company records in Twenty before Person import so the relationship is satisfied. Company names, domains, and industry codes from Synerise map to standard Twenty Company fields.

Synerise transaction events contain line items, totals, and timestamps. We aggregate transaction events per profile into an Opportunity record in Twenty, mapping the transaction total to Opportunity Amount and the transaction timestamp to Opportunity Close Date. Each profile may have multiple transactions; we create one Opportunity per transaction event, preserving the historical record rather than rolling into a single aggregate.

Synerise behavioral events (product.view, added-to-cart, page.visit, custom events) have no direct Twenty CRM equivalent. We transform events into Task records with a custom eventType field carrying the original Synerise event name, a custom metadata JSON field storing event properties, and the original event timestamp as Activity Date. High-frequency events (page.visit, product.view) may exceed practical CRM record counts — we scope event inclusion with the customer and recommend segment-based filtering or sampling for large event histories.

Synerise Catalogs are product/item feeds managed in the Data Modeling Hub. We export catalogs as CSV or JSON and recreate them as a custom Product object in Twenty CRM with fields for item ID, name, description, price, and any custom catalog attributes. Product images from Synerise Catalogs are exported as URLs and stored as custom fields; the actual image files do not transfer.

Synerise Segments return true/false membership flags per profile. Complex segment logic (multi-condition rules, behavioral triggers, AI-driven segments) cannot be reproduced automatically. We export segment membership as boolean or multi-select fields on the Person record. Simple static segments map cleanly; AI-driven behavioral segments are documented as segment_type='ai_behavioral' in the export for manual rebuild in Twenty.

Brickworks schemas are arbitrary record structures defined in Synerise's Data Modeling Hub. Each Brickworks schema becomes a separate Custom Object in Twenty CRM. We extract schema field definitions (field name, type, constraints) and recreate them in Twenty Settings → Data Model before importing schema records. Brickworks record IDs map to custom object UUIDs in Twenty. Schema relationships (foreign key references between Brickworks schemas) map to Twenty lookup fields on the custom objects.

Synerise Campaign definitions — email, SMS, push, WhatsApp — are exported as configuration JSON. Twenty CRM has no native Campaign object in its standard data model. We export campaign configurations including audience rules, templates, and scheduling, and document them as a written Campaign Inventory for the customer to rebuild using Twenty's Workflow builder or an external email tool. Active campaign state (in-flight drip sequences) does not migrate.

Synerise profile tags are exported as comma-separated strings per profile. Tags map to a custom text field on the Person record in Twenty CRM. If the customer uses a defined tag vocabulary (fewer than 50 distinct tags), we recommend a multi-select picklist custom field instead for cleaner filtering and reporting in Twenty.

Synerise Automation Workflows are exported as JSON node graphs (triggers, conditions, actions). Fire-and-forget execution semantics mean workflow state cannot be preserved across cutover. We deliver a written Workflow Inventory documenting every active Synerise workflow with its trigger type, conditions, actions, and recommended Twenty Workflow equivalent. The customer rebuilds workflows in Twenty's Workflow builder post-migration.

AI recommendation configurations (personalized, visual similarity, top items, last seen) are trained on Synerise's proprietary Cleora.ai embedding model and product catalog feeds. Only the recommendation rule configuration transfers. Visual similarity model weights are not exportable. We deliver a written Recommendation Config Inventory documenting all model configurations for manual rebuild in the customer's preferred recommendation tool.

Synerise Owners are resolved by email match against Twenty CRM Members. Owners must be provisioned in Twenty Settings → Members before Person or Company import because OwnerId is a required reference on most objects. Any Synerise Owner without a matching Twenty Member goes to a reconciliation queue for the customer's admin to provision before import resumes.