Migrate from NetHunt CRM to HighLevel

NetHunt Contact records (standard fields: name, email, phone, company association) map directly to GoHighLevel Contact records. Custom fields on the Contact record migrate to GoHighLevel custom fields. We read Contact records from each NetHunt Folder via the API and insert into GoHighLevel Contacts using email as the dedupe key. Company linkage from NetHunt (Contact-to-Company relationship) migrates after Company records are inserted so that the GoHighLevel Contact's company association resolves correctly.

NetHunt's separate Lead object (distinct from Contact) requires a split decision based on lifecycle stage and pipeline assignment. Leads with an active sales engagement map to GoHighLevel Contacts attached to Opportunities. Leads that represent unqualified prospects with no associated Deal map to GoHighLevel Contacts with a tag indicating source system. The customer defines the split criteria during discovery based on their NetHunt Lead lifecycle configuration.

NetHunt Company records map to GoHighLevel Contact records with the Company Name field populated. GoHighLevel does not have a standalone Account/Company object separate from Contact; instead, companies are represented as a field on Contact records. We create GoHighLevel Contacts for each unique Company record first, then link the associated Contact records by setting the Company Name field to match. This preserves the company-contact relationship for reporting and filtering in GoHighLevel.

NetHunt Deals map to GoHighLevel Opportunities. Deal fields (stage, value, responsible owner, expected close date, custom fields) migrate to GoHighLevel Opportunity fields. NetHunt pipeline assignments map to GoHighLevel Pipeline IDs that we configure during the setup phase. Deal stage probability percentages from NetHunt are recreated as stage weights in GoHighLevel pipeline stages.

NetHunt's multiple pipelines with configurable stages per pipeline map to GoHighLevel Pipelines with stage definitions. We read each NetHunt pipeline's stage names and probabilities via the API and create matching GoHighLevel Pipelines with corresponding stage sequences. Stage-to-stage mapping is 1:1; any stage values not available in GoHighLevel are created as custom stage names. Pipeline configuration happens before Deal migration to ensure stage assignments are valid at insert time.

NetHunt Folders organize Records but have no direct GoHighLevel equivalent. We use Tags in GoHighLevel to replicate folder-based segmentation. Each NetHunt Folder name becomes a Tag in GoHighLevel that we apply to all Records migrated from that Folder. This preserves the organizational context of which folder a Contact, Lead, or Deal originated from, enabling filtering and reporting by original NetHunt folder post-migration.

NetHunt email activities linked to Contacts and Deals migrate to GoHighLevel Activities with type Email. Email body content migrates as the activity description, and the original timestamp is preserved as the activity date. Attachments on emails are noted as URLs requiring re-attachment post-migration if they reference external services.

NetHunt Call Logs (duration, direction, notes, associated Contact or Deal) migrate to GoHighLevel Activities with type Call. Direction (inbound/outbound) and duration in seconds transfer to GoHighLevel activity fields. Call dispositions and notes migrate to the activity description. Call logs are migrated after their parent Contact records exist in GoHighLevel to satisfy the contact association.

NetHunt custom fields are defined per Folder and vary across the data model. We enumerate each Folder's custom field schema during discovery, create equivalent custom fields in GoHighLevel (text, number, date, dropdown, checkbox) before migration begins, and map field values during the record import phase. Custom field definitions are captured in a schema manifest delivered alongside the migration output.

NetHunt tags on Records migrate as GoHighLevel Tags applied to the corresponding Contact, Lead, or Opportunity. Tags are string values migrated as-is and deduplicated by name. Any tags that conflict with existing GoHighLevel tags are prefixed with the source system name to avoid collision.