Migrate from Wintouch CRM to Microsoft Dynamics 365 Sales

Wintouch Contact records map directly to Microsoft Dynamics 365 Sales Contact. Standard fields (full name, email, phone, address, title) translate cleanly. We resolve the Wintouch Owner referenced on each Contact to a Dynamics 365 User by email lookup during migration. Custom fields on Contact are audited individually during discovery and mapped to typed Dataverse columns (string, integer, decimal, picklist, boolean) before insert. Address normalization is applied to handle international address formats that may have been entered without country-level consistency in Wintouch.

Wintouch Account records (supporting B2B and B2C types) map to Dynamics 365 Account. The Account is created before Contact import so that the parent CustomerId lookup is satisfied at the moment of Contact insert. Multiple contacts per Account are preserved by linking each Contact's parentcustomerid field to the Account record. Address normalization is applied for international accounts; Wintouch geo-coordinates (latitude/longitude) that exist for North American addresses migrate to the Microsoft Dynamics 365 Sales address latitude and longitude fields.

Wintouch Deals map to Microsoft Dynamics 365 Sales Opportunity. The pipeline stage name maps to a Microsoft Dynamics 365 Sales Process stage value. Closed-won and closed-lost reasons from Wintouch custom fields map to Microsoft Dynamics 365 Sales custom fields for loss reason and win reason. OwnerId resolves via the User mapping. Estimated close date and actual close date migrate directly. We flag any Deals without a linked Account or Contact during extraction so the customer can decide whether to archive them or provision the parent relationship before migration.

Wintouch Activity records (calls, emails, meetings, scheduled tasks) map to Microsoft Dynamics 365 Sales Task and Event records. Call disposition and duration migrate to custom Task fields. Meeting StartDateTime and EndDateTime migrate to Event records. Email bodies migrate to EmailMessage records linked to an Activity Task. ActivityDate preserves the original Wintouch timestamp for timeline ordering. User assignment resolves via the Owner-to-User email lookup. We identify all available activity records during discovery; if the Wintouch configuration holds activities in a non-standard table, we document the table name and row count during extraction.

Wintouch Lead records (including leads generated from custom web forms and auto-assignment workflows) map to Microsoft Dynamics 365 Sales Lead. The lead-to-contact conversion logic in Wintouch is application-layer workflow logic and does not export as data. We migrate the Lead records in their unqualified state and document the conversion criteria so the customer's Dynamics 365 admin can configure lead scoring and assignment rules in Power Automate or Microsoft Dynamics 365 Sales Lead management.

Wintouch customizable pipeline stages are audited during discovery and explicitly mapped to Microsoft Dynamics 365 Sales stage values within a Sales Process. Stage names, ordering, and probability percentages are translated one-to-one. We configure the Sales Process in Dynamics 365 before any Opportunity records import so that stage validation does not reject incoming records. Historical deal stage history migrates as a date-stamped custom field or note if Wintouch exposes the history as a queryable object.

Wintouch custom fields added to Contacts, Activities, Accounts, and Deals require individual schema mapping because Wintouch allows per-object field creation with no published schema reference. We audit the full custom field inventory during discovery, map each to a typed Dataverse column in Dynamics 365, and pre-create the destination fields via the Dataverse API before any data moves. Fields with no corresponding destination (orphaned custom fields) are archived to a JSON manifest rather than silently dropped, so the customer's admin can review and restore them if needed.

File attachments stored within Wintouch do not have a documented bulk export endpoint. We extract attachments via available file paths in the Wintouch environment, map them to the corresponding Contact, Account, or Activity record, and load them as Microsoft Dynamics 365 Sales Annotations (notes with file attachments) or as SharePoint document locations if the customer's Dynamics 365 org uses SharePoint integration. Attachment extraction is scoped during discovery based on the available file path inventory.

Wintouch Users and Owners referenced on Contact, Account, Deal, and Activity records are extracted by email address and matched against the destination Microsoft Dynamics 365 Sales User table. Any Wintouch Owner without a matching Dynamics 365 User is placed in a reconciliation queue for the customer's admin to provision before record migration continues. Active and inactive status is preserved; inactive users are created as inactive Users in Dynamics 365 so that historical assignment is preserved without re-activating the user account.

Wintouch geo-coordinates are available only for North American addresses. International addresses lack coordinates in Wintouch by design. We extract all available latitude/longitude values from Wintouch and map them to Microsoft Dynamics 365 Sales address fields. For international addresses without coordinates, we flag the record and either defer enrichment to a post-migration Bing Maps API call or set the fields to null with a documented note for the customer's admin to handle manually.

Wintouch one-click report definitions and customized report layouts are stored as application-state data and cannot be exported. We extract the underlying record data that feeds each Wintouch report so that the customer can recreate the reports in Microsoft Dynamics 365 Sales using the native report builder or Power BI. We provide a written inventory of all Wintouch reports identified during discovery, including the report name, objects it references, and filters applied, so the customer's admin can replicate the logic in the new platform.

Wintouch multi-checkbox custom properties and tag values stored on Contact or Account records migrate to Microsoft Dynamics 365 Sales multi-select picklist fields. We extract the distinct values for each multi-checkbox property during discovery, define the picklist options in the Dynamics 365 schema, then populate the field during record import. If the tag vocabulary exceeds the Dynamics 365 picklist option limit, we advise on a Topic-based alternative or a separate custom entity to handle the classification.