Migrate from NetHunt CRM to Nutshell

NetHunt Contact records (the primary CRM record type for individuals) map to Nutshell People. Standard fields (name, email, phone, address) migrate directly. Custom fields defined on the source folder are recreated as custom fields on the Nutshell People object before import. NetHunt Contact-to-Company linkage (stored as a link on the Contact record) is preserved by resolving the destination Nutshell Company before Person insert so the People record is attached to the correct Company at migration time.

NetHunt Lead records (a distinct record type from Contact in NetHunt, with lead-specific lifecycle stages) map directly to Nutshell Lead. Lead status, source, and score properties migrate to Nutshell Lead's standard fields. Any custom fields on the Lead folder in NetHunt are recreated as custom fields on Nutshell Lead before migration. Lead-to-Company linkage migrates via the same Company-first resolution step used for People.

NetHunt Company records map to Nutshell Company. The domain stored in NetHunt becomes the Company website field and serves as a dedupe key during import. Nutshell Company is created before any Person or Lead that references it, ensuring the Company relationship is satisfied at the moment of linked-record insert.

NetHunt Deals (pipeline opportunities with stage, value, and responsible user) map to Nutshell's Deal tracking. Deal stage names from NetHunt's pipeline are recreated as Nutshell pipeline stages during schema setup. Deal value, expected close date, owner, and custom deal fields migrate to Nutshell Deal fields. Deals must be migrated after Companies and People/Contacts to satisfy the Account relationship and owner references.

NetHunt supports multiple pipelines with configurable stages per pipeline. We read each pipeline's stage definitions via the NetHunt API during folder enumeration and recreate them as Nutshell Pipelines with corresponding stage names and ordering. Stage-to-stage value probability mappings transfer where NetHunt stores them. Note that Nutshell Foundation tier limits users to one pipeline; Nutshell Pro and above support multiple pipelines.

NetHunt Folders are the top-level organizational container and do not map to a single Nutshell object. Each Folder is treated as a source dataset containing Records of mixed types (People, Companies, Leads, Deals). We enumerate every accessible folder, extract Records by type from each folder, and distribute them to the corresponding Nutshell object. Folder-specific custom field schemas are captured per folder and translated into Nutshell custom fields scoped to the relevant object type.

NetHunt Activities (emails, notes attached to Records) map to Nutshell's activity timeline on People and Companies. Email body content may require HTML-to-text normalization during transform depending on the source email encoding. We migrate activities after the parent People and Company records exist in Nutshell to maintain the activity linkage. Activities attached to Leads map to Nutshell Lead activity timeline.

NetHunt Call Log records (duration, direction, notes) migrate as activities on the linked Nutshell Person or Company. Call direction (inbound/outbound) maps to Nutshell's activity type. Duration and any disposition notes transfer to custom activity fields we create on the destination. Call logs without a linked Contact or Company are reconciled to a default Company or flagged for manual assignment.

NetHunt custom field schemas vary by folder, which is a structural difference from Nutshell's per-object (People, Company, Lead) custom field model. We enumerate every distinct custom field definition across all NetHunt folders, deduplicate by field name and type, and pre-create the corresponding Nutshell custom fields on the appropriate object before any data import. Field type mapping: NetHunt text maps to Nutshell text, date to date, picklist to picklist, checkbox to checkbox, number to number.

NetHunt Tags (simple string values on Records) migrate as-is to Nutshell's tag field on People, Companies, and Leads. Tags are treated as passthrough string values with no transformation. If a Nutshell tag name conflicts with an existing destination tag, we prefix the source tag with a namespace indicator and flag the conflict for the customer to resolve post-migration.