Migrate from NetHunt CRM to Freshsales

NetHunt Contacts (stored as Records within Folders with standard fields name, email, phone, company plus custom fields) map to Freshsales Contacts. We extract all Contact fields from each NetHunt folder during the folder enumeration phase, preserving custom field values against each contact record. Email serves as the dedupe key during import. Freshsales requires a Contact to have either an Account lookup or a standalone designation; we map NetHunt company links to Freshsales Account records created first.

NetHunt Leads (distinct from Contacts, with lead-specific lifecycle fields) map directly to Freshsales Leads. NetHunt lead stage values map to Freshsales Lead Status picklist. After migration, Freshsales Lead conversion creates a Contact, Account, and Deal in one action. We document the lead conversion mapping configuration during scoping so the customer's admin can verify field-to-field mapping before enabling conversion in production.

NetHunt Company records map to Freshsales Accounts. We create the Account first so that the AccountId lookup is resolved at Contact insert time. The NetHunt company domain becomes the Account Website field. Any company address data migrates to the Freshsales Account address fields. NetHunt allows multiple companies per contact; Freshsales enforces one primary Account per Contact, so we map the primary company or flag multi-company assignments for manual resolution.

NetHunt Deals map to Freshsales Deals with stage, value, responsible user, and associated Contact and Company preserved. Deal stage migrates to Freshsales Deal stage. NetHunt custom deal fields migrate to Freshsales custom Deal fields created before migration. Owner assignment resolves by email match against Freshsales User records. Deals must migrate after Accounts and Contacts so the AccountId and ContactId lookups are satisfied.

NetHunt supports multiple pipelines with configurable stages per pipeline. Freshsales uses a single deal pipeline with stage groups at the paid tiers. We map each NetHunt pipeline to a Freshsales stage group or document which stages merge if the customer uses multiple NetHunt pipelines. Stage probability percentages transfer to Freshsales probability values rounded to integer.

NetHunt email activities attached to Contacts and Deals map to Freshsales Task records with subtype indicating email. The email body migrates as Task Description. We link the Task to the migrated Contact or Deal via WhoId and WhatId. Email subject becomes the Task Subject for timeline display.

NetHunt Call Logs (duration, direction, notes) map to Freshsales Task records with TaskSubtype = Call. Call duration migrates to Call Duration field. We preserve the original timestamp as Activity Date for timeline ordering.

NetHunt meeting activities map to Freshsales Event records with Start Time, End Time, and Location preserved. We link Event attendees to the migrated Contact and Account records via Freshsales Event Relations.

NetHunt Comments (notes attached to Records) map to Freshsales Note records. We link Notes to the parent Contact, Lead, Account, or Deal via ContentDocumentLink. Note body migrates as-is with any embedded formatting preserved where possible.

NetHunt custom field schemas vary by folder, requiring per-folder extraction during discovery. We capture every custom field definition (field type, label, options) per folder, create equivalent custom fields in Freshsales under Contacts, Leads, Accounts, and Deals, and map values during record import. Folder-specific custom fields that have no destination equivalent are flagged for the customer to decide whether to create them or archive the data.

NetHunt tags stored on Records migrate to Freshsales Tag if the customer uses Freshsales Tags, or to a custom text field on the target object. We preserve the original tag string values. If the customer has used tags extensively for segmentation, we recommend a Freshsales custom field rather than tags for better filtering and reporting.

NetHunt Folders are the top-level organizational unit containing Records, Views, and Filters. Freshsales does not have a Folder equivalent. We treat each NetHunt folder as a source dataset and map its records to the appropriate Freshsales object. If folders represent distinct business units or data segmentation, we document the folder-to-object mapping for the customer to implement Freshsales Territories or object record types post-migration.