Migrate from Zymplify to Twenty CRM

Zymplify Contact records (name, email, phone, role, enrichment provenance) map directly to Twenty CRM's Person object. The Zymplify contact's enrichment source (Bombora signal attribution, G2 intent data) migrates as a custom field zymplify_enrichment_source__c. Email maps to the Person's email field; phone to phoneNumber; role/title to jobTitle. Owner resolution uses email match against Twenty User records.

Zymplify Company records map 1:1 to Twenty CRM Company. Firmographic fields (domain, industry, employee count, revenue) migrate to Twenty's standard Company fields. Intent score metadata (Bombora spike data, G2 Buyer Intent signals) migrates as a custom field zymplify_intent_score__c and zymplify_intent_sources__c as a comma-separated list. The Company record is created before Person import so that Person-to-Company lookup relationships are satisfied at insert time.

Zymplify Deals map to Twenty CRM Opportunity. The deal name becomes Opportunity name; deal amount maps to amount; close date maps to closeDate; pipeline stage maps to the Opportunity's stageName. Custom deal properties (Closed-Won reason, Closed-Lost reason, custom Zymplify fields) migrate as custom Opportunity fields. Stage vocabulary from Zymplify migrates as-is into Twenty's stage values and can be renamed post-migration.

Each Zymplify deal pipeline maps to a named Pipeline in Twenty CRM. Pipeline stages in Zymplify become Opportunity stage values under the corresponding Twenty Pipeline. We create the Pipeline structure in Twenty before Opportunity import so that stage assignment is valid at record insert time.

Zymplify Sales Cadences are platform-native outreach sequences combining email steps, delays, and task actions with no direct Twenty CRM equivalent. We export cadence structure (step order, step type, delay duration, action type) as a written sequence definition document and create placeholder Task records for the initial outreach touch if the cadence started execution. The customer rebuilds cadences in their preferred sales engagement tool (Salesloft, Outreach, or manual Twenty Tasks) using the documented sequence.

Zymplify Marketing Workflows are automation builders with triggers, conditions, and actions that have no direct equivalent in Twenty CRM. We do not migrate workflows as code. We deliver a written requirements spec for each active Zymplify workflow documenting its trigger, conditions, filter logic, and action sequence, so the customer's admin rebuilds equivalents in their preferred automation layer or as manual process documentation. Workflow documentation is a prerequisite for any post-migration automation rebuild engagement.

Zymplify Customer Success Hub health scores and churn risk indicators migrate as custom fields on Twenty CRM Company records. The raw health signal values (renewal date, engagement score, support ticket count) migrate as numeric custom fields (e.g., zymplify_health_score__c, zymplify_churn_risk__c). The Zymplify scoring model itself does not migrate; the customer documents the scoring logic independently for rebuild as a custom calculation or third-party health scoring tool.

Zymplify's CDP Hub list management and data-cleansing decisions reflect enrichment status and deduplication outcomes. The cleansed contact data itself migrates to Twenty Person with enrichment provenance flags (e.g., zymplify_enrichment_date__c, zymplify_data_quality__c) as custom fields. Source-of-truth for deduplication decisions migrates as a custom field noting the Zymplify deduplication outcome since the provenance trail cannot be fully preserved in Twenty's standard data model.

Zymplify engagement records (emails, calls, meetings, tasks, notes) map to Twenty CRM equivalents: emails map to Note records attached to the Person or Company, calls map to Task with a taskType=Call custom field, meetings map to Event, tasks map to Task, and notes map to Note. Activity timestamps migrate to preserve the timeline ordering. Owner resolution uses email match against Twenty User records. No bulk API is required at this scale; Twenty's REST API handles standard insert operations with batch chunking.

Zymplify custom fields across all object types migrate as Twenty CRM custom fields on the corresponding object. We discover the full custom field inventory during the discovery phase via API enumeration and map each field by name and type. Text fields map to text, numeric fields to number, date fields to date, and picklist fields to select. Custom field API names are prefixed with zymplify_ to avoid naming conflicts with existing Twenty fields.

Zymplify User records (name, email, role, hub assignment) map to Twenty CRM WorkspaceMember records. Resolution is by email match. Any Zymplify Owner without a matching Twenty WorkspaceMember goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role-based access information from Zymplify migrates as custom fields on the WorkspaceMember record.

Zymplify tags on Contact and Company records migrate as a custom field zymplify_tags__c containing a comma-separated list of tag values. Twenty CRM does not have a native tag taxonomy equivalent, so we recommend the customer adopt Twenty's standard label or custom select field for ongoing tagging after migration. Tag strategy decisions are made during scoping.