Migrate from ContactWise CRM to Nutshell

ContactWise Contacts map directly to Nutshell People. Standard fields including name, email, phone, address, and purchase history transfer to corresponding Nutshell People fields. Custom contact properties are identified during discovery, matching Nutshell custom fields are created before import, and value transformations are applied where data types differ (for example, multi-select picklists from ContactWise convert to comma-separated text in Nutshell).

ContactWise Leads map to Nutshell People with a lead_source tag applied during import. The Lead status and source attribution migrate as custom fields on the Person record. If the customer wants to distinguish Leads from Contacts in Nutshell's People model, we create a custom field for lead_status and tag records accordingly.

ContactWise Company records map to Nutshell Company with a direct field correspondence. Company name, address, website, and industry transfer to matching Nutshell fields. Company is created before any Person import so that the Person-to-Company association is satisfied at the moment of Person insert.

ContactWise Opportunities map to Nutshell Deals with deal name, amount, stage, expected close date, and owner assignment preserved. The opportunity_value maps to Deal value; opportunity_stage maps to Nutshell Deal status. Owner assignment resolves by email match against Nutshell users.

ContactWise pipeline stage definitions are documented during discovery, including stage names, order, and probability percentages. We create a stage mapping table that is applied during import, and Nutshell Deal status values are configured to match the source stage sequence. Stage names are preserved as written in ContactWise unless they exceed Nutshell's character limit.

ContactWise custom properties on Contact and other objects are identified during scoping, and matching Nutshell custom fields are created before any data import. Field names must match exactly for Nutshell's CSV import to map them correctly. We apply type transformations where ContactWise data types do not map to Nutshell field types, such as date formats and numeric precision.

ContactWise service desk tickets do not have a direct Nutshell equivalent because Nutshell does not include a native ticket or case object. We export ticket records to a CSV for customer reference and create a lookup document mapping each ticket to its linked Contact Person. If the customer needs ticket functionality in Nutshell, we recommend creating a Deal for each active ticket with a custom ticket_status picklist field and closing the Deal when resolved.

ContactWise time tracking entries are exported to a CSV linked to the associated Contact, Ticket, or Project reference. Nutshell does not have a native time tracking object, so we preserve the export for customer reference and note the association in the migration deliverable. Time entries do not map to standard Nutshell activity records.

ContactWise documents and attachments associated with Contacts, Opportunities, or Tickets are exported to cloud storage (customer-provided bucket or our staging storage). Link records are created in Nutshell as file attachments on the corresponding Person, Company, or Deal. We flag any file type that Nutshell does not support for preview rendering.

ContactWise workflow rules are platform configuration, not data records, and do not export as transferable logic. We document every active workflow during discovery with its trigger type, conditions, and actions, then deliver a written inventory recommending equivalent Nutshell Powerup rules or Workflow automation configurations. The customer's admin rebuilds the automation logic post-migration.