Migrate your NetHunt CRM data

Contacts are primary Records within Folders, with standard fields (name, email, phone, company) plus custom fields. We migrate contacts as structured records with all custom properties preserved. NetHunt's API returns records per folder via GET /api/v1/zapier/triggers/readable-folder.

Leads are a distinct record type managed separately from Contacts in NetHunt. They include lead-specific fields and lifecycle stages. We map Leads to the destination CRM's Lead or Contact object based on the destination's data model.

Companies are stored as Records within Folders, typically linked to Contact records. We preserve company details and the contact-to-company linkage during migration. The folder-based structure requires us to query each folder separately to capture all company records.

Deals track pipeline opportunities with stage, value, and responsible user. We migrate all deal fields including custom fields, stage history context, and owner assignments. Deals must be migrated after their linked Contacts and Companies.

NetHunt supports multiple pipelines with configurable stages per pipeline. We read pipeline definitions via the API and recreate stage mappings in the destination CRM, preserving the visual pipeline structure and stage order.

Activities include emails, notes, and meeting records attached to Contacts and Deals. We map activities to the destination's activity/engagement object but note that email body content may require HTML reformatting depending on the destination's rendering engine.

Call logs are stored as a record type and can be created via the API (POST /records/{recordId}/calls). We migrate call logs with duration, direction, and notes. Some legacy call data may be incomplete if stored as free-form notes rather than structured records.

NetHunt supports custom fields within Records and Folders. Custom field schemas vary by folder, so we capture the field definition for each folder before migration and recreate equivalent custom fields in the destination CRM. Field type mapping (text, number, date, dropdown) must be verified per field.

Folders are the top-level organizational unit in NetHunt, containing Records, Views, and Filters. We treat each folder as a source dataset and map its records to destination CRM objects. Folder-specific custom fields must be captured alongside folder metadata.

Custom roles define user permissions within NetHunt and are tied to NetHunt's internal permission model. These do not map to any standard object in destination CRMs and are not migrated. User access must be reconfigured manually in the destination system.

NetHunt Workflows are automation rules (triggers, conditions, actions) that operate inside Gmail and NetHunt's web UI. Workflow logic cannot be exported via the API. We document the workflow configuration during discovery so teams can manually rebuild equivalent automations in the destination CRM.

Attachments linked to Records may be stored in NetHunt's UI or integrated services like DocHub. We migrate attachment URLs and metadata but verify that linked files remain accessible post-migration, as attachments are not always stored within NetHunt itself.

Records can be tagged for segmentation. Tags are simple string values we migrate as-is to the destination CRM's tag or label field. We flag any tags that may conflict with existing destination tags and prompt for disambiguation.