Migrate from NetHunt CRM to HubSpot

NetHunt Folders containing Deals translate to HubSpot Pipelines. Each unique folder name in NetHunt becomes a named Pipeline in HubSpot. Deal Stages within the folder map to ordered Pipeline Stages with probability percentages that you specify — or we apply HubSpot defaults and flag deviations.

NetHunt Records flagged as persons map to HubSpot Contacts. Email, name, phone, job title, address, and system-created timestamps transfer directly. Owner assignment resolves by matching NetHunt user email to HubSpot user email, creating an OwnerId link. Custom fields present on the record are also transferred as HubSpot custom properties on the Contact, preserving any pick-list values that require value mapping during the migration planning phase.

NetHunt Records flagged as organizations map to HubSpot Companies. Company name, domain, industry, employee count, and annual revenue transfer as standard Company properties. Linked person-type Records associate via Company-Contact relationships in HubSpot. If the organization record includes custom fields, those become HubSpot custom properties on the Company object, and any address or phone details also map to the corresponding HubSpot fields for a complete profile.

NetHunt Records without an explicit type flag split based on field presence: records with an email address but no company domain field route to HubSpot Contact; records with a domain but no personal email route to Company. Ambiguous records surface for your review before migration commits.

NetHunt Deals map to HubSpot Deals with deal name, amount, close date, and stage inherited from the parent Folder's pipeline mapping. HubSpot Deal associations link to the resolved Company and Contact records. Owner resolves by email match. If NetHunt stores deal custom fields, those transfer to HubSpot custom properties on the Deal object, and any notes attached to the deal become HubSpot notes linked to the deal for full context.

Stage names from NetHunt Folders map to HubSpot Pipeline Stage names value-by-value. Probability percentages transfer where NetHunt stores them; otherwise HubSpot defaults apply. You specify the stage order and closed-won/closed-lost designations during planning. If NetHunt stage names include custom labels, we build a value map that aligns each with the correct HubSpot stage, and any probability weights transfer to HubSpot's stage probability field for accurate forecasting.

NetHunt Comments on Records and Deals become HubSpot Notes attached to the corresponding Contact, Company, or Deal. Original comment text, author email, and created timestamp transfer. Rich-text formatting in NetHunt converts to HubSpot's note format. If a comment mentions other records or includes file attachments, those references are preserved as linked associations or attached files on the HubSpot note for complete context.

Files attached to NetHunt Records or Deals re-upload to HubSpot's file manager and attach to the corresponding CRM record. File names, sizes, and original upload dates are preserved. URL references in NetHunt that point to Gmail attachments download and rehost in HubSpot storage.

NetHunt users map to HubSpot owners by email address. Unmatched NetHunt users are flagged before migration — your team either creates HubSpot users first or assigns records to a fallback owner. Owner names and email addresses transfer for audit continuity.

NetHunt custom fields (visible in folder settings) create HubSpot custom properties on the appropriate object (Contact, Company, or Deal). Field type translates: text-to-text, number-to-number, date-to-date, pick-list-to-enumeration. Pick-list values requiring translation become value-mapping tasks. If a custom field uses dependent pick-lists or conditional logic in NetHunt, we document those dependencies in the mapping spec and propose equivalent HubSpot pick-list setups or fallback to text fields when no direct enumeration exists.

NetHunt workflows and automation sequences do not migrate. They require rebuilding in HubSpot's workflow editor. FlitStack AI exports NetHunt workflow definitions as structured documentation (triggers, conditions, actions) that your HubSpot admin can use as a rebuild reference. This is disclosed upfront.

NetHunt's record linking feature (connecting Records to other Records, or Records to Deals) translates to HubSpot's association model. Contact-to-Company uses the standard association. Record-to-Record links that represent relationships (e.g., referral partner) may need custom association types on HubSpot Enterprise. If your migration includes many-to-many relationships or hierarchical structures, FlitStack AI can pre-create the necessary association types in HubSpot Enterprise and map the corresponding NetHunt record links accordingly.