Migrate from HaystackCRM to Nutshell

HaystackCRM Company records map to Nutshell Account. We export Companies first during migration to establish parent records before any Contact import. The Company name becomes the Account name, and any Company-level phone, address, and website fields map directly to Nutshell Account fields. The dedupe key in Nutshell's import wizard is the Account name or an explicit external ID we set from the Haystack Company ID.

HaystackCRM Contact maps to Nutshell Person (the primary contact object). Standard fields (first name, last name, email, phone, address) map 1:1. The parent Company linkage resolves to the Account imported in the prior step using the external ID we set on both sides. Haystack custom fields on Contact map to Nutshell custom fields, which we pre-create before migration using Nutshell's custom field API.

HaystackCRM Opportunity maps to either a Nutshell Lead or a Nutshell Opportunity depending on where the deal sits in the sales process. Deals in early stages (e.g., Temperature priority of Cold or Warm) map to Nutshell Lead; deals at proposal or negotiation stage map to Nutshell Opportunity. The dollar value, pipeline stage name, and close date migrate directly. We configure Nutshell pipeline stages to match Haystack stage names before migration so that stage mapping is deterministic.

HaystackCRM's Opportunity pipeline stages map to Nutshell pipeline stages in the destination CRM. We extract every distinct stage name from the Haystack export and configure matching stages in Nutshell's pipeline settings before migration. Stage probability weights from Haystack (if populated) transfer to Nutshell as stage probability percentages. Temperature priority (Hot, Warm, Cold) from Haystack migrates as a custom field if the customer wants to preserve it.

HaystackCRM Tasks map to Nutshell Tasks. Each Task carries a due date, assignment to a Contact or Opportunity, and a completion status. We export Tasks with their parent linkage preserved as an external ID field. In Nutshell, we resolve the parent Contact or Opportunity via the external ID mapping and create the Task linked to the correct record. Tasks without a resolvable parent are imported with a note flag for manual reassignment.

HaystackCRM Events (calendar-bound records with start and end timestamps) map to Nutshell Events. The event name, start time, end time, and location migrate directly. Device calendar sync links do not transfer and must be rebuilt in Nutshell. Attendee data from Haystack exports as a text field and is re-created manually in Nutshell post-migration.

HaystackCRM uses a flat tag model for segmentation with no hierarchy. Tags export as a multi-value text column on the Contact and Company records. In Nutshell, tags map to Labels (a multi-value text field on Person and Account). We flatten any implied hierarchy in Haystack tags (e.g., Region:Northeast becomes a flat label 'Region:Northeast') and map all tags to Nutshell Labels during transformation. The customer reviews the resulting label set before final import to confirm the segmentation intent is preserved.

HaystackCRM Item/Catalog records (products or services used in quoting) map to Nutshell Products. Item name, SKU, description, and unit price transfer to Nutshell Product fields. If the customer uses Haystack Quotes with line items, the line item Product references resolve to the imported Product records during migration.

HaystackCRM Users are assigned as owners of Contacts, Companies, Opportunities, and Tasks. We export the user roster and match by email against Nutshell Users. A matching Nutshell User must exist before Owner assignment can migrate; if a Haystack User has no Nutshell counterpart, the record imports with an unassigned flag and the customer's admin provisions the Nutshell User before reassigning.

HaystackCRM file attachments are stored via Dropbox, iCloud, or OneDrive integration links rather than native storage. We export the attachment reference URLs and document them in the migration scope. In Nutshell, attachments must be re-uploaded manually or via the Nutshell API file upload endpoint. We provide the customer with a manifest of every attachment reference for manual re-attachment post-migration.