Migrate from NetHunt CRM to Salesforce Sales Cloud

NetHunt Contacts map directly to Salesforce Contact. Standard fields (Name, Email, Phone, Title) transfer directly. Custom fields on the Contact Record migrate to Salesforce custom fields (API name suffixed __c) that we create before import. The AccountId lookup resolves by matching the NetHunt Contact's linked Company Record to a pre-created Salesforce Account, using the Company domain or name as the dedupe key during import.

NetHunt Lead records map to Salesforce Lead with all standard fields (Name, Email, Phone, Company, LeadSource) preserved. Lead-specific lifecycle stage fields migrate to Salesforce Lead Status and a custom field nethunt_lead_stage__c for original-stage audit. Owner email resolves to Salesforce User ID via the User lookup table before insert.

NetHunt Company Records map to Salesforce Account. Company Name becomes Account Name; website domain migrates to the Website field and serves as the dedupe key. Account is created before Contact import so the AccountId Lookup relationship is satisfied at the moment of Contact insert, avoiding orphaned Contact records.

NetHunt Deals map to Salesforce Opportunity with Deal value, stage, responsible user, and close date preserved. The NetHunt deal stage maps to the Salesforce StageName value that corresponds to the configured Sales Process. Closed-Won and Closed-Lost reasons from NetHunt custom fields migrate to Salesforce Loss Reason and Win Reason fields. AccountId resolves via the Deal's linked Company Record.

Each NetHunt pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process. We pre-create the Record Type and deploy the stage whitelist (probability percentages rounded to Salesforce-allowed integers) before Deal migration begins. If multiple pipelines share the same stage set, they can share a Record Type; if stage sets differ, each gets its own Record Type and Sales Process.

NetHunt Activity Records (emails, notes, meeting records attached to Contacts and Deals) migrate to Salesforce Task records for the activity timeline entry and EmailMessage for email body content. The WhoId on Task points to the migrated Lead or Contact; WhatId points to the related Opportunity or Account. HTML email body migrates as-is; plain text migrates to the Task Description field. We set ActivityDate to the original NetHunt timestamp to preserve timeline ordering.

NetHunt Call Logs (created via POST /records/{recordId}/calls) map to Salesforce Task with TaskSubtype set to Call. Call duration, direction (inbound/outbound), and disposition notes migrate to custom Task fields call_duration__c, call_direction__c, and call_disposition__c. We flag any Call Logs with missing duration or timestamp as data-quality issues in the pre-migration audit, since legacy call records on Basic tier are often incomplete.

NetHunt custom field schemas vary by folder, so we enumerate every folder during discovery and capture the field definition (name, type, required flag, picklist values) for each one. We then pre-create equivalent Salesforce custom fields (with __c API suffix) on the corresponding object before any data import. Folder-specific fields that have no natural home on a standard object become custom fields on Account or Contact depending on their intended target record. This per-folder enumeration is required because there is no single API call to export all folder schemas at once.

NetHunt Folders are the top-level organizational unit containing Records, Views, and Filters. Each folder maps to a Salesforce object, Record Type, or tagging strategy depending on its contents. Folders that contain only Contacts map to a Contact Record Type; folders with mixed record types map to the primary object with folder name preserved in a custom field nethunt_source_folder__c for audit traceability. We document every folder's contents and record type mix during scoping.

NetHunt Tags are simple string values stored on Records. Tags migrate as-is to a Salesforce custom text field on the relevant object. If the customer uses tags for multi-value classification (e.g., multiple tags per Contact), we migrate to a multi-select picklist. We flag any tags that conflict with existing Salesforce picklist values and let the customer resolve the conflict before migration.

NetHunt Owners (assigned to Contacts, Companies, Deals, and Activities) map to Salesforce User records. We resolve owners by email match against the destination Salesforce org's User table. Any NetHunt Owner without a matching Salesforce User is held in a reconciliation queue until the customer's admin provisions the User. Owner resolution must complete before Deal and Activity migration begins because OwnerId is a required reference on Opportunity.

NetHunt attachment URLs (linked files stored in NetHunt's UI or integrated services like DocHub) are migrated as URLs referenced in a custom field attachment_url__c on the parent record. We verify that each linked file remains accessible post-migration; files behind NetHunt-only authentication may become inaccessible after the subscription ends. We flag these explicitly in the pre-migration audit so the customer can download or re-link them before cutover.

NetHunt Comments attached to Records migrate to Salesforce Chatter FeedItem on the parent record (Contact, Account, Opportunity) for threaded discussion context, or to a Salesforce Note if the destination org does not have Chatter enabled. We set FeedItem CreatedDate to the original Comment timestamp. Rich-text comments migrate with formatting preserved.

NetHunt Workflows are automation rules operating inside Gmail and NetHunt's web UI with no accessible export path. Workflow trigger conditions, actions, and delay steps cannot be read via the API or transferred to any destination CRM. We document every active Workflow during discovery in a structured audit format (trigger type, conditions, actions, assigned folder) and deliver it as a written handoff document for the customer's admin to rebuild in Salesforce Flow. This is a manual post-migration step, not a migration service deliverable.

NetHunt multi-channel sequences (email, LinkedIn, WhatsApp, phone cadences available on Business and above) are sales engagement cadence records that have no direct Salesforce Sales Cloud equivalent. Sequences do not export via the API. We deliver a sequence inventory document listing every active cadence (channel order, step timing, template references) for the customer's admin to rebuild in Salesforce Sales Engagement or a comparable sales engagement platform. The contact-level sequence enrollment status migrates to a custom field sequence_enrollment__c for reference.

NetHunt Custom Roles define user permissions tied to NetHunt's internal permission model and do not map to any standard object in Salesforce. User access and permissions must be reconfigured manually in Salesforce after migration using Salesforce Profiles and Permission Sets. We deliver a NetHunt role inventory document listing each role and its associated access level so the admin can design equivalent Salesforce permission sets.