Migrate from Zymplify to monday CRM

Zymplify Contact records (name, email, phone, role, company association) map to Monday.com CRM Person entities. Enrichment provenance from the CDP hub and intent data sources transfers as custom fields on the Person entity since Monday.com CRM supports custom fields on all entity types. Email match is used as the dedupe key during import.

Zymplify Company records map to Monday.com CRM Organization entities. The intent signal metadata (Bombora score, G2 Buyer Intent flag, intent spike timestamp) attaches as custom fields on the Organization entity. Zymplify's intent scores are preserved as numeric or text custom fields rather than native scoring since Monday.com CRM does not have an equivalent intent-surfacing feature. Account is created before any Person import so the relationship is satisfied at insert time.

Zymplify Deals map to Monday.com CRM Deal entities with pipeline stages represented as board status columns. We map Zymplify deal stages 1:1 to Monday.com Deal status values, preserving custom stage names. The Deal entity links to the associated Person (contact) and Organization (company) entities in Monday.com CRM.

Zymplify Sales Cadences (email steps, delays, task actions) are Zymplify-native outreach sequences with no direct Monday.com CRM equivalent. Monday.com CRM has no native sales engagement cadence feature. We export cadence structure as a sequence definition document covering step order, action type, delay rules, and task assignments, and the customer's admin rebuilds using Monday.com's automation recipes or a dedicated sales engagement tool.

Zymplify Marketing Workflows (triggers, conditions, actions) do not migrate as automation code. Monday.com's recipe-based automation builder uses a different trigger-action model. We document the workflow logic — triggers, branch conditions, action sequences, and intended outcomes — in a requirements spec that the customer's admin uses to rebuild in Monday.com's automation layer.

Zymplify's health scores and churn risk indicators are Zymplify-native calculations. We export the raw health metrics (component scores, risk indicators, last-seen timestamps) as custom fields on the Organization entity. The scoring model itself does not migrate; it requires reconstruction in Monday.com using custom formulas or a separate reporting layer.

Zymplify's CDP hub stores contact enrichment provenance, deduplication decisions, and list management records. We carry the cleansed contact data to Monday.com CRM Person entities and flag enrichment source as a custom field (e.g., enrichment_provider__c) since source-of-truth provenance has no native equivalent in Monday.com CRM. Data cleansing decisions (merged records, suppressed records) are preserved as notes on the Person entity.

Zymplify custom fields are supported across all object types but the export schema is not publicly documented. We discover the full custom field inventory during the discovery phase by querying the Zymplify API, then map each field to a Monday.com CRM custom field of equivalent type (text, number, date, dropdown, checkbox). Field-level transformation rules are documented in the mapping spec.

Zymplify user records (role, hub assignment, ownership) map to Monday.com CRM users. We resolve Zymplify owners by email match against the destination Monday.com workspace. Users without a matching account go to a reconciliation queue for the customer to provision before record import resumes.

Zymplify tags applied to Contacts and Companies are Zymplify-native. We export tags as a comma-separated custom field on the Person or Organization entity. The customer chooses during scoping whether to rebuild tagging taxonomy using Monday.com CRM's native tag feature or maintain the field-based approach. This is a configuration decision, not a direct data migration.