Migrate from Wintouch CRM to Odoo CRM

Wintouch Contact records map directly to Odoo Contact (res.partner with customer_rank set). Standard fields (name, email, phone, mobile) migrate cleanly. Custom fields on Contact require individual type mapping (dropdown to selection, free text to char, numeric to float) validated during discovery before import. Address data from Wintouch's multi-address support migrates to Odoo's Contact address fields with postal code and country normalization applied, particularly for international records outside North America.

Wintouch Account records map to Odoo Partner records in company mode (customer_rank set to 100+). The B2B vs B2C type distinction from Wintouch maps to Odoo's company vs individual Partner type. Multiple contacts per account are preserved as child Contact records linked to the parent Company Partner. Wintouch's multi-address support on accounts maps to Odoo's Contact child records for each address location (shipping, billing, office). International addresses that lack geo-coordinates are flagged and mapped with blank lat/lng rather than silently dropped.

Wintouch Leads with web form origin or auto-assignment workflows map to Odoo CRM Lead (crm.lead). Lead-to-contact conversion logic in Wintouch is application-layer automation and cannot be exported as data. We migrate the Lead records with their status, source, and owner intact. The customer configures Odoo's Lead to Opportunity conversion rule (lead.lifecycle.mode) to match their sales process after migration. Any custom fields on Wintouch Leads are individually mapped per the custom field audit.

Wintouch Deals map to Odoo CRM Opportunity (crm.lead with type='opportunity'). The pipeline stage maps to Odoo's stage_id with a custom pipeline ID for the relevant sales team. Deal value, expected close date, and probability migrate directly. Closed-won and closed-lost reasons from Wintouch custom fields become Odoo Opportunity description notes or custom fields on the Opportunity.

Wintouch customizable pipeline stages are mapped explicitly to Odoo CRM Stage records within the relevant Sales Team (crm.team). Stage names and ordering are preserved. Historical deal stage history is migrated as a custom field or note on each Opportunity, since Odoo does not store a native stage change log as separate records. We configure the pipeline kanban view order to match Wintouch's stage ordering before the first production migration phase.

Wintouch Activity records (completed tasks and scheduled work) migrate to Odoo CRM Log Notes on the related Contact or Opportunity record. Activity date formats use AS/400 date conventions that we normalize to ISO 8601 (YYYY-MM-DD HH:MM:SS) during the transform layer. User assignment in Wintouch maps to Odoo Responsible (user_id) on the log note, resolved via email match against Odoo User records. Completed vs. open activity filtering is agreed upon with the customer during scoping before migration.

Wintouch file attachments are not covered by a documented bulk export endpoint. We extract available attachments via available file paths in the Wintouch environment and map them to the corresponding Contact, Account, or Activity record in Odoo as IrAttachment records. Any attachments that cannot be located via available paths are flagged in the reconciliation report with the source record reference so the customer's admin can manually upload or confirm loss.

Wintouch custom fields exist per object (Contacts, Activities, Accounts, Leads) and may accumulate dozens over years of use with inconsistent naming and types. During discovery we produce a full custom field inventory with field name, object, type, and current values. Each field is mapped explicitly: dropdowns become Odoo selection fields, free text becomes char or text, numeric values become float or integer. Fields with no Odoo destination object are archived to a JSON manifest rather than silently dropped. Odoo Studio is used to create the fields in the target Odoo database before production migration.

Wintouch generates latitude/longitude coordinates for addresses but only within North America. International addresses from outside the US and Canada will have no geo-coordinates in Wintouch. We flag all records with missing geo-data during extraction and either map them with blank lat/lng or record them in a separate enrichment manifest for post-migration geo-enrichment using an Odoo-compatible geocoding service. No geo-data is silently dropped during migration.

Wintouch one-click report definitions and layout configurations are application-state data stored in a centralized repository and cannot be exported as data. We extract the underlying record data that feeds each report (Contacts, Accounts, Deals, Activities) so that the same data is available in Odoo for rebuilding. We flag which reports existed in the source system during the migration handoff and provide a report inventory manifest to the customer's admin for Odoo report recreation.

Wintouch Owner records map to Odoo User accounts. We resolve owners by email match against the destination Odoo User table. Any Wintouch Owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive owners are mapped to Odoo inactive users or flagged as unknown.

Wintouch includes built-in AI and ML predictive model capabilities for basic forecasting. Odoo CRM includes a Forecasting module in its sales app for revenue projection. Any historical forecast data or scoring values stored in Wintouch custom fields migrate to corresponding Odoo custom fields. The AI model itself does not transfer; Odoo's own forecasting tools are configured post-migration using the migrated pipeline data.

Wintouch covers CRM, lightweight ERP, project management, and HR within a single platform. Odoo provides these as separate installable apps within the same database. We scope the CRM and Sales migration first. If the customer also activates Odoo Project, Invoicing, or Accounting modules, the same Contact, Account, and Opportunity records are available across all apps without re-import. We flag the multi-app scope during discovery and configure the Odoo apps before production migration begins.