Migrate from Zurple to Twenty CRM

Zurple contacts map directly to Twenty People. The primary company link becomes the companyId relation in Twenty. Contacts without a primary company are imported with companyId left null and flagged for manual association review after migration. This post-migration step allows your team to establish correct company associations using Twenty's UI or bulk-import tools. The original contact ID is preserved as Source_System_ID__c for traceability and deduplication on subsequent delta runs.

Zurple companies map 1:1 to Twenty Companies. Parent-company hierarchies map to Twenty's optional parentId relation. Multi-contact companies in Zurple become a single Company record in Twenty with multiple Person records linked via companyId. We deduplicate by name during the sample migration phase and flag any ambiguous matches for your review before the full run commits.

Zurple deals map to Twenty Opportunities. Deal name becomes Opportunity name, amount maps directly, close date maps to closeDate, and stage becomes the stage field. Owner is resolved by email match against Twenty Workspace Members before the full migration runs.

Each Zurple pipeline stage value maps to a corresponding Twenty Opportunity stage value. Where Zurple stage names differ from Twenty's defaults, we create custom stage values via Twenty's metadata API before the import batch is built. This ensures stage labels, probabilities, and ordering match your current pipeline workflow from the first record imported.

Zurple pipelines have no native Twenty equivalent. We create a Pipeline_Name__c custom field on the Opportunity object to preserve which Zurple pipeline each deal originated from. Stage mapping then applies per-pipeline to preserve deal progression history. This allows you to filter and report on deals by their original pipeline in Twenty's UI after migration completes.

Zurple leads that have not converted to contacts land as Twenty People with a custom Lead_Source__c field set to 'Zurple Lead'. Original lead score or rating migrates to a numeric custom field if present in Zurple's export. Leads with a 'Converted' status route to the Contact mapping path, associating them with their converted Person record and preserving the conversion timestamp as a custom date field.

Zurple email and call activities become Twenty Tasks linked to the parent Person or Company. Meeting activities become Notes with a timestamp header. Original activity date, duration, and assignee are preserved on each record. Attachments on activities migrate as file attachments on the corresponding Task or Note in Twenty, maintaining the complete activity history for each contact and company.

Zurple file attachments on contacts or deals re-upload as file attachments on the corresponding Twenty Person or Company note. Inline images embedded in Zurple notes are extracted, rehosted to a temporary storage bucket, and relinked in Twenty. We validate that each file is accessible and that the relinking produces a working URL before the migration run completes.

Zurple custom properties on contacts — lead score, engagement metrics, IDX attribution data, source channel — become Twenty custom fields on the Person object. We create each field via Twenty's /metadata API, inferring field type from source data format. Picklist values, number ranges, and date formats are validated during the sample migration phase to catch type mismatches before the full run.

Zurple users are matched to Twenty Workspace Members by email address. Unmatched owners are flagged as a pre-migration task — your team either invites them to Twenty first or assigns their records to a fallback member before the full run. This prevents orphaned records and ensures every migrated deal, contact, and activity retains its correct assignee from day one in Twenty.