Migrate from Wintouch CRM to Zoho CRM

Wintouch Contact records export via the UI at Contacts > Options > Export Contacts. Standard fields (First Name, Last Name, Email, Phone, Address) map directly to Zoho Contact fields. Custom contact fields from the Contacts > Custom Fields tab are audited individually during scoping and pre-created in Zoho before import. We normalize AS/400 date fields (CYYMMDD character format) to ISO 8601 before Zoho import. The Contact's Owner field resolves by email match to a Zoho User.

Wintouch Account records support B2B and B2C types with multiple contacts per account and multiple addresses. Standard field extraction is straightforward. Address normalization is required for international accounts because Wintouch's geo-enrichment operates North America only. We pre-create Accounts before Contact import so that the Account-Contact lookup is satisfied at import time.

Wintouch Lead generation records include custom web form data and auto-assignment metadata. The lead-to-contact conversion logic (application-layer workflow triggers) does not migrate as data. We import the Lead records as-is into Zoho Leads, preserving any source attribution, scoring values, and custom fields. Zoho's Lead Status field maps from the Wintouch lead stage.

Wintouch Deal records (pipeline and stage data) map to Zoho Deals. Stage names and ordering require explicit mapping to Zoho pipeline stages during scoping. Historical deal stage history is preserved as data; the automation that triggered stage transitions does not migrate. Deal owner resolves by email match to Zoho User.

Wintouch pipeline stages are customizable per organization. We map each Wintouch stage name and probability to a corresponding Zoho Pipeline Stage. In Zoho, we configure the pipeline with stage ordering and probability values matching the Wintouch configuration before Deal import begins. This is a configuration step, not a data migration step.

Wintouch Activities (completed tasks, scheduled work, calls, meetings) map to Zoho Tasks and Events. Activity date formats require normalization from Wintouch's date conventions to ISO 8601. User assignment maps by email to Zoho User records. We identify the activity type (call, meeting, general task) during extraction to route to the correct Zoho object.

Wintouch Task records (assignment, tracking, completion status) map directly to Zoho Tasks. Owner assignment resolves by email match to Zoho User. Completed versus open task filtering is agreed upon with the customer before migration to determine whether closed tasks are included in the export.

Wintouch allows per-object custom field creation on Contacts, Activities, Leads, Accounts, and Deals. Each custom field is identified during discovery, its type is validated (dropdown vs. free text vs. numeric), and it is pre-created in Zoho before any data import. Wintouch fields with no Zoho equivalent are archived to a CSV handoff file rather than silently dropped. Zoho's 300-field-per-module limit is checked during scoping to flag any overflow risk.

Wintouch file attachments stored within the platform are not covered by a documented bulk export endpoint. We extract available attachments via available file paths and map them to the corresponding Contact or Account record as Zoho File Upload attachments. Attachment volume and storage path accessibility are assessed during discovery; large file sets may require Zoho's file storage add-on.

Wintouch one-click report definitions and layout configurations live in the application repository and cannot be exported as data. We extract the underlying record data that feeds each report and flag which reports existed in the source system during the handoff. The customer's admin recreates reports in Zoho Reports or Zoho Analytics using the migrated data as the source.

Wintouch generates latitude/longitude coordinates for addresses but only within North America. International addresses may lack geo-coordinates after export. We flag all missing geo-data during extraction, preserve the original address fields in Zoho, and either flag records for post-migration enrichment or map them to a placeholder. This is surfaced explicitly before cutover rather than silently dropped.