Migrate from Wice CRM to Nutshell

Wice Organizations map to Nutshell Companies. Wice enforces that Contacts must be linked to an Organization, so we export Organizations first and use the Wice Organization ID as the dedupe key during Nutshell Company import. Company name, address fields, phone, and website migrate directly. Any Organization without a name is flagged for the customer to name before import.

Wice Contacts map to Nutshell People. We resolve the parent Organization to a Nutshell Company by name or ID match during the Contact export phase, then set the AccountId lookup on each Person record. Name, email, phone, title, and address fields migrate directly. Custom contact properties (Gold tier on Wice) map to Nutshell custom fields on People; we create the Nutshell custom fields before import begins.

Wice Deals map to Nutshell Deals with the Person (Contact) and Company (Organization) lookups resolved at migration time. Wice allows fully custom pipeline stages per installation, so we capture the actual Wice stage names during discovery and generate a stage-mapping table before any Deal records are written to Nutshell. Deal value, expected close date, and owner assignment migrate directly.

Each distinct Wice pipeline stage becomes a Nutshell Deal stage value. We configure the Nutshell Deal stages in the account settings before migration, matching Wice stage names to Nutshell stage names chosen by the customer. Stage mapping errors are the most common cause of deal-value misrepresentations post-migration, so we validate the stage table with the customer's sign-off before any Deal writes begin.

Wice Projects contain Tasks and custom fields. We export Projects as Nutshell Milestones if the customer uses Nutshell's milestone feature, or we export the project name as a Nutshell tag on the child tasks to preserve grouping. Project-level custom fields map to custom fields on the related tasks. Orphan tasks (not inside a project) export as standalone Nutshell tasks.

Wice Tasks live inside Projects or standalone linked to contacts or deals. We export both contexts. Standalone tasks linked to a Contact map to Nutshell Tasks with the Person lookup resolved. Tasks inside a project inherit the project tag or milestone grouping. Task status, priority, due date, and assignee (owner) migrate directly. Orphaned tasks are flagged for customer review before import.

Wice differentiates basic and advanced campaigns. We export campaign names and targeting properties as a text property or Nutshell tag on the related Contact and Deal records. Campaign history (sent/open/click data) does not export from Wice and cannot be migrated. The customer rebuilds campaign tracking in Nutshell or a dedicated marketing platform post-migration.

Wice Tickets linked to contacts or organizations map to Nutshell Notes attached to the corresponding Person record, with a ticket status tag applied. Wice custom ticket fields map to custom fields on the Note or to Nutshell People custom fields at the customer's choice. Ticket numbering sequences reset in Nutshell; we document the original Wice ticket numbers in a custom field for reference.

Wice free-text notes attached to contacts, organizations, deals, and projects migrate to Nutshell Notes linked to the corresponding Person, Company, or Deal record. Note body migrates as plain text. Wice formatting (bold, lists) may be simplified. We preserve the source-object linkage so notes remain findable in context.

Wice uses a category system for deduplication and classification that does not map 1:1 to Nutshell's tag model. We export category assignments as a comma-separated text field or map to Nutshell tags if the customer chooses. The customer decides during scoping whether to use tags (actionable) or text fields (audit-only) for the category mapping.

Wice custom fields on contacts, organizations, deals, and projects (Gold tier) map to Nutshell custom fields on People, Companies, and Deals. Picklist-style custom fields require value translation if the destination picklist values differ. We create Nutshell custom fields before import begins so that CSV imports map to the correct field IDs.