Migrate from Wice CRM to Odoo CRM

Wice Contact records map 1:1 to Odoo Contact (res.partner with partner_latitude type = contact). We extract via CSV export (cloud) or direct database query (on-premise), preserving name, email, phone, address, and the link to the parent Orga/organization. The Wice contact-organization relationship is preserved as partner_id on the Contact. Custom fields on contacts (Gold tier) map to Odoo custom fields created via Settings > Technical > Custom Fields before migration.

Wice Organization records map to Odoo Contact records of type company (res.partner with is_company = True). We export Organizations first so that the relationship ID is available when Contacts are imported, satisfying the partner_id foreign key. Organization address fields (street, city, country) map to standard Odoo address fields. If the Wice installation uses a custom organization-type picklist, we create a custom field on the Odoo Company record to hold that classification.

Wice Deals map to Odoo CRM Opportunity (crm.lead with type = opportunity). The Wice dealstage property maps to crm.stage via an explicit stage-mapping table that we generate during discovery using the customer's actual Wice stage names. Deal value maps to Odoo's planned_revenue. Expected close date maps to date_deadline. Owner assignment maps to user_id via email-based user lookup against the Odoo destination User table.

Wice allows fully custom pipeline stages per installation. We capture the customer's actual Wice stage names and probabilities during discovery and generate a stage-mapping table before any Opportunity records are written. Each Wice pipeline maps to an Odoo CRM Pipeline (crm.team) with its own stage sequence. Stage probability percentages from Wice are stored as Odoo stage sequence values or custom fields for reporting consistency.

Wice Project records map to Odoo Project (project.project). We export Projects before Tasks so that project_id is resolved at Task import time. Custom project fields from Wice map to Odoo custom fields on the Project record. Project status (active, on hold, closed) maps to Odoo project_stage_id.

Wice Tasks exist inside Projects and also standalone linked to contacts or deals. We export both contexts and reconstruct the hierarchy in Odoo Project. Project-linked tasks receive a project_id reference; standalone tasks are created without a project_id and linked via the related contact or opportunity. Task status and assignee migrate with owner lookup via email match.

Wice Campaigns (basic and advanced) map to Odoo Utm Campaign records (utm.campaign). Advanced campaign targeting and tracking properties that have no Odoo equivalent are stored as custom fields on the utm.campaign record. Campaign member history (sent, opened, clicked data) does not migrate because Odoo does not have a native campaign analytics object at the contact level; we deliver a CSV export of campaign member activity for the customer's admin to import into a BI tool.

Wice Tickets map to Odoo Helpdesk Ticket (helpdesk.ticket) if the customer licenses the Helpdesk module. Ticket status, priority, and custom fields migrate directly. Ticket numbering sequences may reset in Odoo; we flag this during scoping and propose a custom ticket reference field that preserves the original Wice ticket number for audit continuity.

Wice Notes attached to contacts, organizations, deals, and projects migrate to Odoo Note records (mail.message with note_flag = True) linked via mail.thread to the parent record. Plain-text note body migrates as-is; formatting is simplified to plain text because Odoo Note does not preserve rich-text styling. Activity logs (calls, emails, meetings logged as activities in Wice) migrate to Odoo Mail Activity records linked to the respective res.partner or crm.lead.

Wice custom fields on contacts, organizations, deals, and projects (Gold tier) are mapped explicitly during field-mapping phase. Picklist-style custom fields require value translation if the Odoo destination uses a different picklist vocabulary. We generate a custom field value mapping table for each picklist field during scoping. Custom fields are created in Odoo via Settings > Technical > Custom Fields before record migration begins.

Wice's category system for deduplication and classification does not map 1:1 to Odoo tags (utm.tag). We export category assignments as a comma-separated text field on the Contact record during migration, and the customer's admin chooses whether to convert them to Odoo Tags or retain them as a read-only custom field for post-migration segmentation.

Wice stores files as Hold files attached to records but provides no bulk download mechanism and no documented API endpoint for binary files. This is flagged as a manual step outside the automated migration scope. We provide the customer with a file-level export checklist listing every record with attachments and the manual download steps for cloud installations, or a custom database script for on-premise deployments to extract binary BLOBs directly. The checklist is delivered during discovery and must be completed before the go-live cutover.