Migrate from Wice CRM to Salesforce Sales Cloud

Wice Contacts map 1:1 to Salesforce Contacts. We export Wice contact fields (name, email, phone, address, custom properties) as a flat row and import into Salesforce Contact using the Bulk API for large sets. The link to the parent Organization is preserved by resolving the Wice organization ID to the newly inserted Salesforce Account ID. Any picklist-style custom fields require value translation against the Wice installation's picklist options.

Wice Organizations map directly to Salesforce Account. Wice enforces a relationship between Contacts and Organizations, so we export Organizations first, insert them into Salesforce as Accounts, capture the new Salesforce Account IDs, then use those IDs as the AccountId on each Contact during import. The Wice organization name becomes Account Name; the Wice industry field maps to Industry picklist if present.

Wice Deals map to Salesforce Opportunity. Each Deal carries pipeline stage, deal value, expected close date, and owner assignment. We capture the customer's actual Wice stage names during discovery and configure corresponding Salesforce Opportunity stages and a Sales Process before import. Closed-Lost and Closed-Won transitions are mapped to the configured StageName values.

Wice allows full customization of pipeline stages per installation. We configure Salesforce Opportunity Stages with names matching the customer's Wice stage names, set probability percentages matching Wice's deal-stage probabilities, and configure the stage order within a Salesforce Sales Process. Stage mapping errors are the most common cause of deal-value misrepresentations post-migration; we generate a stage-mapping table during discovery and validate it against a sample import before the full run.

Wice Projects contain tasks, assignees, and status fields with a project-to-task hierarchy. We map Projects to Salesforce either as Opportunities with a Project record type and custom fields (if the customer uses Salesforce for project tracking) or as a Salesforce Custom Object (Project__c) if the destination org has no pre-existing project structure. The hierarchy between Projects and Tasks must be reconstructed during import.

Wice Tasks exist both inside Projects and standalone linked to contacts or deals. We export both contexts and reconstruct the hierarchy in Salesforce by resolving the parent reference at migration time. Standalone tasks linked to contacts or deals map directly to Salesforce Task with WhoId and WhatId resolved to the migrated Salesforce IDs. Tasks without a resolvable parent are flagged for customer review in a reconciliation report.

Wice differentiates basic and advanced campaigns. Basic campaigns migrate as Salesforce Campaign with Name, Status, and Type. Advanced campaigns with additional targeting and tracking properties migrate to Salesforce Campaign with those properties mapped to custom Campaign fields. Campaign history (sent/open/click data) may not exist in Wice's standard export if the campaign tracking was implemented via external tools; we note this limitation during scoping and migrate whatever data is present.

Wice Tickets are support tickets linked to contacts or organizations. We map ticket status, priority, and custom fields to Salesforce Case fields. If the destination Salesforce org includes Service Cloud, we map directly to Case; if not, we map to a custom Ticket__c object to preserve the record structure. Ticket numbering sequences in Wice do not carry over; Salesforce assigns its own case numbers on insert.

Wice free-text notes attached to contacts, organizations, deals, and projects migrate to Salesforce Note records linked via ContentDocumentLink to the parent Contact, Account, Opportunity, or custom Project object. Note body migrates as plain text; any formatting (bold, lists) may be simplified depending on the destination's Note rendering. We preserve the source-object linkage in a custom field source_object__c for audit.

Wice custom fields on contacts, organizations, deals, and projects map to Salesforce custom fields. We pre-create the destination Salesforce fields (with appropriate field types: text, picklist, number, date, checkbox) via the metadata API before migration. Picklist-style custom fields require value translation if the Wice picklist values differ from any pre-existing Salesforce picklist. Standard field length limits (e.g., 255 characters for text fields) apply and we flag truncation before import.

Wice uses a category system for deduplication and classification that does not map 1:1 to tags in most destination CRMs. We export category assignments as a comma-separated custom text field on the Contact or Account, or map to a Salesforce multi-select picklist if the customer's Salesforce admin prefers that structure. The customer chooses the target strategy during scoping.

Wice owner assignments on contacts, organizations, deals, and projects map to Salesforce User records by email match. We extract every distinct owner referenced in the Wice export, match by email against the destination Salesforce org's User table, and resolve OwnerId during import. Any Wice owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. On-premise installations may require additional mapping work if owner records are not consistently tied to email addresses.