Migrate from Highrise to Nutshell

Highrise People map directly to Nutshell Contacts. All standard fields—name, email, phone, address, social links—transfer cleanly via the Highrise parties.xml API or structured CSV export. We use the email address as the primary dedupe key during Nutshell import. Any associated Company (Party) is resolved via the Highrise contact-company association before inserting, so that the Nutshell Contact lands with the correct Account linked.

Highrise Companies export via parties.xml as a distinct Party type alongside People. We export all Company records with their name, domain, address, and phone, then insert them into Nutshell as Accounts before the Contact import phase. The Highrise contact-to-company linkage migrates as the Nutshell Contact-to-Account relationship using the association endpoint.

Highrise Deals export only as .txt files rather than structured CSV or API-backed records. We parse the TXT output to extract deal name, stage name, monetary value, responsible user email, and associated party reference. Those parsed values are then reconstructed as Nutshell Deal records. Any Deals with embedded tables, rich-text formatting, or multi-line notes in the TXT export are flagged for manual review before the final migration step.

Highrise Cases (customer support or task tracking) export as .txt only, identical to Deals. We parse the TXT output to extract case title, status, associated party, and responsible user, then insert them as Nutshell Case records. Complex Cases with long text histories or embedded references are flagged for manual review. Note that Nutshell Cases require the Nutshell Pro or Enterprise tier.

Highrise Tasks transfer cleanly via the API as standard task objects with due dates, assignees, status, and priority. We export both open and completed tasks with the related party reference. The responsible user resolves to a Nutshell User via email match. Completed status and the original due date are preserved in the migration.

Highrise stores all notes, emails, and comments as Recordings linked to People or Companies via the recordings.xml endpoints. Export is .txt only, which strips HTML formatting from emails and loses inline image references. We capture the full plain-text body and metadata (date, author, type) and insert them as Nutshell Activity records on the relevant Contact or Account timeline. The customer should expect rich email content to arrive as plain text in Nutshell.

Highrise custom fields on People, Companies, and Deals are accessible via the custom_field_subjects API endpoints. We detect all custom field definitions in the Highrise account and create equivalent Nutshell custom fields on the corresponding entity (Person, Account, or Lead). Nutshell supports text, long text, currency, and date custom field types. Currency fields preserve the original amount and we set the Nutshell currency type accordingly.

Highrise tags are flat labels applied to People, Companies, Deals, and Cases via the tags.xml API. We export all tag definitions and their associations and re-apply them as Nutshell tags using the Nutshell API. Highrise has no tag hierarchy or categories, so any tag-based filtering or grouping logic the customer uses must be reconstructed manually in Nutshell post-migration.

Highrise Users are the internal team members who own records and are assigned to Deals and Cases. We export the full user roster including name and email, then match by email against the Nutshell destination account's user list. Any Highrise owner without a matching Nutshell user is held in a reconciliation queue for the customer to provision before record import resumes, since OwnerId references are required on Deal and Case inserts.

Highrise Deals use a simple pipeline with named stages (e.g., New, Contacted, Qualified, Won, Lost). We extract the full stage configuration from Highrise and recreate it as Nutshell pipeline stages using Nutshell's customizable pipeline settings. Stage order and any custom stage names transfer. Probability percentages associated with stages are noted for the customer to configure in Nutshell's pipeline settings post-migration.