Migrate from Wintouch CRM to Twenty CRM

Wintouch Contact records export via the UI at Contacts > Options > Export Contacts as CSV. Standard fields (name, email, phone, address) map directly to Twenty's People object fields. Custom Contact fields are extracted during scoping and pre-created in Twenty's Data Model under Settings > Data Model before import. Any Wintouch contact with no email address is flagged in the mapping table and imported with a blank email field per Twenty's import behavior.

Wintouch Account records (B2B and B2C types, multiple contacts per account, multiple addresses) map to Twenty's Company object. Address normalization is required for international accounts because Wintouch's geo-enrichment is North America only; we flag non-North American addresses and either preserve raw address fields or pass them to a post-migration enrichment step. Account name is the dedupe key during import.

Wintouch Leads map to Twenty's People object with the original lead source preserved in a custom field. Wintouch's lead-to-contact conversion logic is not exportable as data because the workflow triggers live in the application layer; we document the conversion workflow during scoping so the customer can replicate lead assignment and routing in Twenty's workflow builder post-migration.

Wintouch Deals map to Twenty's Opportunity object. The Wintouch dealstage and pipeline assignment map to Twenty's Opportunity stage configuration, which we pre-build in the destination workspace before import. Historical deal stage history migrates as a JSON field on the Opportunity record if the customer requires it for reporting continuity.

Wintouch's customizable pipeline stages are exported during discovery and configured in Twenty as Opportunity stage values before deal migration begins. Stage names and ordering are mapped explicitly. Any Wintouch stage with no direct Twenty equivalent is created as a custom stage in Twenty during schema setup.

Wintouch Activities (completed tasks and scheduled work) map to Twenty's Task and Note objects. Completed activities with a body of text migrate as Note records; scheduled work items migrate as Task records. Activity date formats (which vary by Wintouch installation) are normalized to ISO 8601 during the transform step. Owner assignment resolves by email match to Twenty Members.

Wintouch Task records map directly to Twenty's Task object. Completed versus open task status is preserved. Owner assignment is resolved via email lookup to the Twenty Members table. Any task assigned to a Wintouch Owner with no matching Twenty user is placed in a reconciliation queue for the customer's admin to provision before the migration phase resumes.

Wintouch allows per-object custom field creation across Contacts, Activities, Accounts, and Leads. We audit the full custom field inventory during discovery, identify field types (dropdown, free text, checkbox, numeric, date), and pre-create all custom fields in Twenty's Data Model before any record import. Fields with no Twenty equivalent are archived to a JSON field on the record with a migration note rather than silently dropped.

File attachments stored within Wintouch are not covered by a documented bulk export endpoint. We extract available attachments via accessible file paths in the Wintouch environment and map them to the corresponding Contact or Activity record. Where file path access is restricted, we document the attachment inventory and flag which records have unresolved attachments for the customer's admin to handle post-migration.

Wintouch generates latitude/longitude coordinates for addresses but only within North America. International addresses exported from Wintouch will lack geo-coordinates. We extract available coordinate data and map it to Twenty's address fields, flagging records from outside North America for post-migration geo-enrichment if required. No coordinate data is silently dropped; all gaps are surfaced in the extraction audit.