Migrate from Wintouch CRM to Freshsales

Discovery and Wintouch environment audit

We audit the Wintouch environment for record volumes across Contacts, Accounts, Deals, Activities, Tasks, and Leads. We extract the complete custom field inventory for every object and classify each field by type, usage frequency, and mapping destination. We document every observed automation trigger (lead assignment rules, follow-up sequences, pipeline stage update logic) in a written automation inventory. We assess the IBM iSeries data file access path and extract a sample of records to validate date format, address normalization requirements, and international address scope. We identify any geo-data gaps on international records and agree on a handling path before proceeding.

Freshsales schema setup and custom field pre-creation

We configure the Freshsales destination environment before any data import. This includes creating custom fields on Contact, Account, Deal, and Task that correspond to the Wintouch custom fields marked for migration. For every Lead custom field, we pre-create the matching field on the corresponding Contact, Account, and Deal object and configure the field mapping dropdown through Admin > Leads > Field Mapping so that data transfers automatically on lead conversion. We create the Freshsales pipeline with stage names and probabilities mapped from the Wintouch pipeline. We provision Freshsales Users matching Wintouch owners by email.

Data extraction, cleaning, and normalization

We extract records from Wintouch via the available UI export paths and direct IBM iSeries file access where needed. We clean legacy date formats (Wintouch date conventions from the AS/400 environment often differ from ISO 8601), normalize international addresses, resolve owner email references, and identify any records that reference a parent object not yet imported. We run deduplication on Contact and Account records using email as the dedupe key and agree with the customer on merge rules for any duplicates identified before import begins.

Sandbox validation pass

We run a full migration into a Freshsales sandbox using production-like data volume before touching production. The customer reviews a random sample of imported records against the Wintouch source, validates that pipeline stages, custom field values, and owner assignments are correct, and confirms the Lead-to-Contact field mapping configuration is working as expected. Any mapping corrections, custom field additions, or stage probability adjustments happen in the sandbox before production migration begins. The sandbox pass is included in all standard migration scopes.

Production migration in dependency order

We run production migration in the correct dependency order: Accounts first (from Wintouch Companies), then Contacts (with AccountId resolved), then Deals (with AccountId and OwnerId resolved), then Leads (with field mapping configured), then Tasks and Activities (with parent record resolution), then attachment path mapping if file attachments are in scope. Each phase emits a row-count reconciliation report showing records imported, skipped, and errored before the next phase begins.

Cutover, delta migration, and automation handoff

We freeze writes to Wintouch at cutover and run a final delta migration for any records created or modified during the migration window. We enable Freshsales as the system of record and deliver the written automation inventory to the customer admin so they can rebuild Wintouch triggers in Freshsales Workflows. We deliver the archived custom field inventory as a written record with notes on each field's purpose and suggested Freshsales equivalent. We provide a one-week hypercare window for reconciliation issues raised by the sales team. Rebuilding Freshsales Workflow automations is outside the migration scope.