Migrate from solve 360 to Nutshell

solve 360 Contacts map to Nutshell Contacts. Standard fields (name, email, phone, address) migrate directly. Custom fields defined on the solve 360 Contact record are created as matching Nutshell custom fields before import and populated with original values. The solve 360 contact's relationship link to a parent Company is resolved by matching the company name against Nutshell Company records, creating the Contact-Company association at migration time.

solve 360 Company records map to Nutshell Company objects. Company name, domain, and address fields migrate directly. Custom fields on solve 360 Companies are created as Nutshell Company custom fields and populated. Company is imported before Contact so that the Contact-Company lookup can be satisfied at insert time, avoiding orphaned Contact records without a parent Company.

solve 360 pipeline stages on the primary record map to Nutshell Deal records. We extract each deal's stage name, probability, pipeline assignment, value, and close date from solve 360 and create corresponding Nutshell Deals. The solve 360 pipeline structure (stage order and probability percentages) is mapped to Nutshell's Deal pipeline stages during schema configuration before migration.

solve 360 Tasks migrate to Nutshell Activities. Task status, priority, due date, assignee, and time-tracking fields transfer to Nutshell Activity records. Assignee mapping resolves solve 360 owner IDs to Nutshell user emails by matching against the User mapping table created during discovery.

solve 360 Follow-ups are a distinct activity type tied to Contacts or Companies. We export Follow-ups as time-stamped activity records and map them to Nutshell Activities linked to the parent Contact or Company. Follow-up descriptions and timestamps are preserved in the Nutshell Activity body and date field respectively.

solve 360 Support Requests have no direct Nutshell equivalent. If the destination Nutshell account includes Service Cloud, Support Requests migrate to Nutshell Cases with status transitions and linked conversations preserved. If Service Cloud is not in scope, we migrate the request history as Notes on the parent Contact or Company record, flagging the Notes with a [Support Request] prefix so the customer admin can distinguish them from general notes.

solve 360 Time Records attach to tasks, site notes, calls, and meetings. We export duration, date, billing flag, and parent object reference. Time data migrates as custom fields on the parent object (Contact, Company, or Activity) or as structured Notes if the customer prefers a flat history. The customer chooses the time-record strategy during scoping based on how they intend to report time in Nutshell.

Tags in solve 360 label Contacts, Companies, and other records. We export all tag definitions and their per-record associations. Tags are re-created as Nutshell native tags and re-applied to the corresponding records during migration, preserving the tagging relationships per Contact, Company, and Deal.

solve 360 user-defined custom fields on Contacts and Companies (including text, number, date, and selection types) are exported with their field definitions and values. We pre-create matching custom fields in Nutshell before any data import, using equivalent field types. Selection-type custom fields map to Nutshell dropdown or radio-button fields with the same option values.

Attachments on Contacts, Companies, Tasks, and Support Requests are downloaded from solve 360 as files with their metadata (name, type, size, upload date). They are re-uploaded to Nutshell and re-linked to the parent record (Contact, Company, or Deal) at the destination. We preserve the original upload date as a custom field on the attachment if the customer requires it for audit.

solve 360 Users are both system actors and assignment targets on Tasks, Follow-ups, and Deals. We export the user list and map solve 360 owner IDs to Nutshell User emails. Orphaned assignments (where the source user does not have a matching Nutshell User) are flagged in the reconciliation report for the customer admin to resolve before record import continues.