Migrate from Wintouch CRM to monday CRM

Wintouch Contact records export via the UI export path. Standard fields (name, email, phone, address) map to corresponding Monday.com columns. Custom fields identified during scoping map to custom columns on the Contacts board. Email validation and phone number formatting are normalized before import because Wintouch address data may contain legacy formatting from the AS/400 export. International addresses are flagged — Wintouch's geo-enrichment is North America only, so any non-US/Canada contact records are imported with address columns intact but without latitude/longitude coordinates.

Wintouch Account records map to Monday.com's built-in Companies CRM entity, which functions as a shared company record that Items (Contacts and Deals) can link to. B2B and B2C account types map to a custom Account Type column. Multiple contacts per account are preserved by linking each Contact Item to the Company Item via the CRM link column.

Wintouch Deal records map to Monday.com Deal Items on a Deals board. Deal stage maps to the Board Group that represents the pipeline stage. Pipeline stage names and ordering are defined as Monday.com Groups before migration; each Wintouch dealstage value is mapped to a Group name. Historical stage change records are preserved as a text column (Stage History) rather than a native audit log, since Monday.com does not maintain a structured stage-change timeline.

Wintouch Activities capture completed tasks and scheduled work. These migrate as Items or subitems on the relevant Monday.com board. Activity date formats (Wintouch may use legacy AS/400 date conventions) are normalized to ISO 8601 before import. Owner assignment in Wintouch maps to a Monday.com Team Member column; the customer's admin provisions workspace members before migration so the lookup resolves correctly.

Wintouch allows per-object custom field creation on Contacts, Activities, Accounts, and Leads. Each custom field is identified individually during discovery scoping, typed (text, dropdown, date, number), and mapped to a Monday.com custom column of equivalent type. Fields with no Monday.com equivalent (e.g., legacy AS/400-specific data types) are archived in a reference document rather than silently dropped. The full custom field inventory with mapping decisions is signed off by the customer before data migration begins.

Wintouch pipeline stages are customizable per organization. Stage names and ordering are mapped explicitly to Monday.com Board Groups before migration. The probability percentage associated with each stage is stored as a custom Number column on the Deals board for reporting purposes. Historical deal stage history is preserved as a text column on each Deal Item.

Wintouch Lead records map to Items on a dedicated Leads board in Monday.com. Lead-to-contact conversion logic (a workflow trigger in Wintouch) does not migrate as automation — the customer's admin rebuilds this using Monday.com's Recipe automations post-migration. We document the existing conversion rule during scoping so the automation design is informed by the original behavior.

File attachments stored within Wintouch are not covered by a documented bulk export endpoint. We extract available attachments via available file paths identified during discovery and map them to the File column on the corresponding Contact or Activity Item in Monday.com. Attachments that cannot be retrieved from the Wintouch file store are flagged in the migration handoff document with the filename and parent record for manual handling.

Wintouch owners are referenced by ID on Contacts, Accounts, Deals, and Activities. We resolve each owner by email against Monday.com workspace members. Any Wintouch owner without a matching Monday.com user is placed in a reconciliation queue; the customer's admin provisions the missing workspace member before record import continues. This step gates the migration because owner assignment is required on most Monday.com CRM entities.