Migrate from Wice CRM to Microsoft Dynamics 365 Sales

Wice Organizations map directly to Microsoft Microsoft Dynamics 365 Sales Account records. Wice enforces the Contact-Organization relationship, so we export Organizations first during migration scoping to establish AccountId values before any Contact import. The Organization name becomes Account Name, the domain property becomes Website, and any custom fields on Organization map to typed Dataverse fields on Account. The dedupe key is Organization name matched against Account Name with a fuzzy match review step for near-duplicates.

Wice Contacts map 1:1 to Dynamics 365 Contact records. Each Contact has a required Organization lookup in Wice; we resolve this to AccountId during the import phase. Standard fields (name, email, phone, address) map directly. Custom contact properties from Wice Gold tier migrate to custom Dataverse fields on Contact. We preserve the Wice Contact ID in a custom field wice_contact_id__c for reconciliation and audit trail.

Wice Deals map to Dynamics 365 Opportunity records. The Wice deal stage (custom per installation) maps to a Microsoft Dynamics 365 Sales Process stage that we configure before migration, whitelisting the exact stage names from the customer's Wice instance. Deal value, expected close date, and owner assignment migrate directly. We resolve the Contact or Organization link to the Opportunity's ContactId or AccountId. Closed-Won and Closed-Lost deals preserve their status with close date and amount.

Wice allows fully customizable pipeline stages per installation, so there is no fixed stage set to map against Dynamics 365 by default. We capture the customer's actual Wice stage names during discovery and create a corresponding Microsoft Dynamics 365 Sales Process with matching StageName values and probability percentages. Stage mapping errors are the most common cause of deal-value misrepresentations post-migration, so we validate the mapping table against a sample of 20-30 live deals before production import.

Wice Projects contain tasks, assignees, and status fields with a hierarchical structure. Microsoft Dynamics 365 Sales does not have a native project object; we map Projects to Opportunities with project-specific custom fields if the customer's project tracking is deal-adjacent. If Projects represent a distinct business object (non-sales work), we recommend creating a custom Dataverse entity for Projects and Tasks and mapping the hierarchy explicitly. The customer decides the target schema during scoping.

Wice Tasks exist standalone and inside Projects. Standalone Tasks map 1:1 to Dynamics 365 Task with Status, Priority, due date, and owner preserved. Tasks linked to Deals migrate as Task with WhatId pointing to the migrated Opportunity. Orphaned Tasks (no parent record) are flagged in a reconciliation report for the customer's admin to resolve.

Wice Campaigns (basic and advanced tiers) map to Dynamics 365 Campaign. Basic campaign properties (name, status, start/end dates, target) migrate as Campaign fields. Advanced campaign targeting and tracking properties migrate to custom Campaign fields. Campaign response history (sent/open/click data) does not migrate as structured records; we note this limitation and recommend rebuilding campaign tracking in Dynamics 365 Marketing or Campaign Influence if needed.

Wice Tickets migrate to Dynamics 365 Case if the destination org includes Service Cloud or the customer enables the Case entity. Ticket status, priority, and custom fields map to Case Status, Priority, and custom Case fields. Wice ticket numbers do not map to Case numbers because Dynamics 365 assigns sequential case numbers at creation; we preserve the Wice ticket number in a custom field wice_ticket_number__c.

Wice Notes attached to Contacts, Organizations, Deals, and Projects migrate to Dynamics 365 Note (Annotation) records linked via object-specific relationship fields. We preserve the note body as plain text. Formatting (bold, lists, embedded images) may be simplified depending on the target Dynamics 365 configuration. Each Note is linked to the migrated parent record using the wice_record_id__c reconciliation key.

Wice stores binary files as Hold files attached to records. There is no documented bulk-export endpoint for these files, and no automated migration path exists. We flag every record with attachments during scoping and provide the customer with a file-level export checklist. Each Hold file must be downloaded individually through the Wice UI or via a custom script for on-premise installations, then uploaded to SharePoint or attached to the corresponding Dynamics 365 record post-migration. This step is time-intensive and falls outside the automated record migration scope.