Migrate from NetHunt CRM to Pipedrive

NetHunt Contacts migrate to Pipedrive Persons. Standard fields (name, email, phone, address) map directly. NetHunt's custom fields on Contact records translate to Pipedrive custom fields on the Person object. We create the custom field schema in Pipedrive before inserting any Persons. The NetHunt contact-to-company linkage (stored as a company_id property) migrates as the Pipedrive org_id on Person after the Organization records are created.

NetHunt Leads are distinct from Contacts in NetHunt's data model and migrate to Pipedrive's Lead object. Lead-specific lifecycle stage fields map to Pipedrive's Lead status field with a custom field preserving the original NetHunt lifecycle value for audit. Pipedrive's Lead object exists separately from Person, which allows teams to keep unqualified prospects as Leads before conversion to a Person-Organization relationship.

NetHunt Company records map to Pipedrive Organizations. The Company name becomes the Organization name, and domain or website data migrates to the Organization's address and website fields. Organizations must be created before Person records to satisfy the org_id Lookup on Person. NetHunt folder-based company records are extracted per folder during enumeration and merged by domain into a deduplicated Organization list.

NetHunt Deals migrate to Pipedrive Deals with stage, value, responsible user, and expected close date preserved. NetHunt's pipeline assignment maps to Pipedrive's pipeline field on the Deal. The Deal-to-Contact linkage in NetHunt (a deal can have multiple linked Records) maps to the Person and Organization links on the Pipedrive Deal. Custom fields on the NetHunt Deal record recreate as equivalent Pipedrive custom deal fields.

Each NetHunt Folder containing Deals maps to a Pipedrive Pipeline. Folder-level stage configurations translate to Pipedrive Stage entries within the pipeline. We extract the stage name, probability percentage, and stage order from NetHunt and create equivalent Pipedrive stage definitions. Multiple NetHunt folders may map to a single Pipedrive pipeline if the customer consolidates during migration; this is a configuration decision made during scoping.

NetHunt email and note engagements attached to Contacts or Deals migrate to Pipedrive Activity records with type=email or type=note. The content body migrates as plain text with HTML stripped. Activity assignment (owner) resolves via email match to the Pipedrive User. The parent record (Person, Organization, or Deal) link is preserved via Pipedrive's deal_id, person_id, and org_id fields on the Activity.

NetHunt call logs migrate to Pipedrive Activity records with type=call. Duration, direction (inbound/outbound), disposition notes, and timestamp migrate to the equivalent Pipedrive activity fields. Call recordings referenced in NetHunt migrate as attachment URLs on the Activity, with a note flagging that Pipedrive's native call recording storage is not enabled by default and requires a VoIP integration to activate.

NetHunt custom fields vary by folder, so we capture the field definition (name, type, options, required flag) for each folder during discovery. Each custom field recreates as an equivalent Pipedrive custom field on the corresponding object (Person, Organization, Deal, or Lead). NetHunt field types (text, number, date, dropdown, checkbox) map to Pipedrive field types (varchar, int, date, enum, checkbox). Pipedrive's field type constraints require matching the source field type before migration to avoid rejection on insert.

NetHunt tags on Records migrate to Pipedrive Labels on the corresponding object (Person, Organization, or Deal). Tags are simple string values migrated as-is. We flag any tags that may conflict with existing Pipedrive Labels and resolve duplicates by appending a numeric suffix where needed. Labels in Pipedrive can be assigned across multiple object types, matching NetHunt's cross-record tagging behavior.

NetHunt Owners (assigned to Contacts, Companies, and Deals) resolve by email match to Pipedrive Users. During scoping, we extract every distinct Owner email and verify a corresponding Pipedrive User exists or will be provisioned before migration. Owners without a match go to a reconciliation queue for the customer's admin. This step gates the Deal migration because OwnerId is required on Pipedrive Deals.

NetHunt attachments stored in linked services (such as DocHub integrations) migrate as URL references attached to the corresponding record in Pipedrive. We do not download and re-upload file content unless the source URL remains publicly accessible post-migration. We flag any NetHunt-integrated attachment sources that may lose access after the migration cutoff, so the customer can provision alternative document management before go-live.

NetHunt stage names, probabilities, and ordering from each folder's pipeline configuration map to Pipedrive Stage entries. Probability percentages round to Pipedrive's stage probability field. Closed-Won and Closed-Lost statuses in NetHunt map to Pipedrive's StageClosedWon and StageClosedLost flags on the respective stage.