Migrate from SuiteDash to Nutshell

SuiteDash Contacts map to Nutshell People records. Standard properties (name, email, phone, address) migrate directly. Contact-scoped custom fields map to Nutshell People custom fields. Tags on Contacts migrate as a comma-separated string into a Nutshell People custom field or as a label set depending on the customer's tagging strategy chosen during scoping. Primary Contact assignment on a Company does not create a Nutshell Account hierarchy relationship automatically; we flag this for admin configuration post-migration.

SuiteDash Company records map to Nutshell Accounts. Company Public custom fields map to Nutshell Account custom fields. Company Private custom fields (visible only to the Primary Contact in SuiteDash) present a visibility challenge: Nutshell does not have an equivalent private-field model. We flag all Private-scoped fields during scoping and propose three options: map to standard Account custom fields (full visibility), map to a private note field, or drop with documented loss. The customer chooses per-field during mapping review.

SuiteDash Deals map to Nutshell Leads. The Deal pipeline and stage names map to Nutshell pipeline stages. Deal probability percentages transfer to the Lead's win probability if Nutshell's probability settings are configured to use custom values. Lost-won status and closed dates migrate to Lead status and close date. Owner assignment resolves via email match to Nutshell Users.

Each SuiteDash pipeline becomes a Nutshell pipeline. SuiteDash stage names and order transfer to Nutshell stage names in the same sequence. Probabilities per stage are mapped to Nutshell stage win probabilities. We configure the pipeline in Nutshell before any Lead records import.

SuiteDash Appointments map to Nutshell Activities. Scheduling data (date, time, duration, location, associated Contact or Company) transfers to Nutshell Activity records linked to the corresponding People or Account. Booking page configurations and bidirectional calendar sync settings do not migrate; we flag these for manual reconfiguration in Nutshell's calendar integration settings.

SuiteDash Support Tickets map to Nutshell Cases if the destination Nutshell account includes the Cases feature (Pro tier and above). Ticket status workflows map to Case status values. Thread history and attachments migrate as Case comments. Custom fields on Support Tickets map to Case custom fields. Ticket priority maps to Nutshell Case priority.

SuiteDash Projects have no direct Nutshell equivalent because Nutshell is a CRM, not a project management platform. We export Projects as Nutshell Note records attached to the related Account or People record, preserving project name, description, and custom field values. Project task hierarchies are exported as a separate note block or as an activity log. The customer rebuilds project tracking in a dedicated project management tool post-migration.

SuiteDash Invoices migrate as read-only historical records. We export invoice data (line items, amounts, payment status, invoice date) as Nutshell Note records attached to the relevant Account, preserving the financial summary without creating a live billing relationship. Active or pending invoice workflows, payment processor history, subscription state, and partial payment records do not migrate cleanly; we recommend freezing recurring billing changes during cutover and starting subscriptions fresh in the destination platform.

SuiteDash Staff records map to Nutshell Users. Role assignments and staff-level custom fields transfer to Nutshell User fields. Owner and assignee references on Deals, Appointments, and Tickets resolve by matching the staff member's email to the Nutshell User record. We hold any Staff record without a matching Nutshell User in a reconciliation queue for admin provisioning before record import resumes.

SuiteDash Tags (freeform labels on Contacts and Companies) export as a comma-separated list. We propose two migration strategies during scoping: map to Nutshell label/tag feature if the account uses that, or flatten into a custom multi-select text field on People and Account. The customer chooses during mapping review based on how they use tags for segmentation.