Migrate from NetHunt CRM to Microsoft Dynamics 365 Sales

NetHunt Contact records map to Dynamics 365 Contact. Standard fields (name, email, phone, company linkage) migrate directly. Custom fields defined in the Contact's parent folder become Dynamics 365 custom fields on the Contact entity. We preserve the original folder name as a text field folder_source__c for audit and segmentation during the transition period.

NetHunt Lead records (distinct from Contacts) map directly to Dynamics 365 Lead. Lead-specific lifecycle fields migrate to the corresponding Dynamics 365 Lead attributes, and any custom fields defined on the Lead folder become custom fields on the Dynamics 365 Lead entity.

NetHunt Company records map to Dynamics 365 Account. The company name becomes the Account Name; domain data becomes Website. Account is created before Contact import so the AccountId lookup is satisfied at Contact insert time. We deduplicate by company name and domain during staging.

NetHunt Deals map to Dynamics 365 Opportunity. Deal stage maps to a Microsoft Dynamics 365 Sales Process stage that we configure before migration, whitelisting the relevant stage values per pipeline. Deal value, close date, owner, and custom fields migrate directly. We resolve the parent AccountId by matching the Deal's linked company against the migrated Account records.

NetHunt's multiple pipelines (each with configurable stages) map to Dynamics 365 Record Types on Opportunity, each paired with a corresponding Sales Process. Stage probability percentages migrate from NetHunt to Dynamics 365 StageProbability. This configuration is deployed to a Sandbox before production migration for validation.

NetHunt email engagements and notes attached to Contacts and Deals map to Dynamics 365 EmailMessage records and Note records respectively. EmailMessage stores the body content; Note stores text notes. Both link via the Regarding (object) field to the migrated Contact or Account. HTML email body content is preserved and rendered in Dynamics 365's activity timeline.

NetHunt call logs map to Dynamics 365 Task with TaskSubtype set to Call. Call duration, direction, disposition, and notes migrate to custom Task fields. The ActivityDate is set to the original NetHunt timestamp to preserve timeline ordering. Call recording URLs migrate as text fields (Dynamics 365 stores recordings separately in SharePoint or a linked storage service).

NetHunt meeting records map to Dynamics 365 Event. Start time, end time, location, and attendees transfer directly. EventRelation records link attendees to the migrated Contact, Account, or Opportunity. Meetings without attendee data migrate as standalone Event records.

NetHunt custom fields vary by folder, meaning the same logical entity may have different custom field sets depending on which folder it lives in. We enumerate all custom field definitions per folder during discovery, consolidate overlapping schemas, and create equivalent Dynamics 365 custom fields on the corresponding entity (Contact, Lead, Account, Opportunity). Field types are mapped: NetHunt text to Dynamics text, NetHunt number to Dynamics whole number or decimal, NetHunt date to Dynamics datetime.

NetHunt tags on records migrate as a text field containing comma-separated values or as a Multi-Select Picklist if the Dynamics 365 field type supports it. We flag any tag values that may conflict with existing picklist values in the destination org. The customer chooses the tag strategy during scoping based on downstream segmentation needs.