Migrate from NetHunt CRM to Twenty CRM

NetHunt Contacts map to Twenty Person records. Standard fields (name, email, phone, company link) transfer directly. NetHunt custom fields on Contact records must be pre-created in Twenty as Person custom fields before import. We enumerate every NetHunt folder containing Contacts and capture its distinct custom field schema during discovery, then create equivalent Twenty field definitions via the /metadata GraphQL API. NetHunt contact-to-company linkage preserves as a Person → Company lookup relationship in Twenty.

NetHunt Leads are a distinct record type separate from Contacts, with lead-specific lifecycle stage fields. We migrate NetHunt Leads to Twenty Person records, flagging the original record type in a custom field nethunt_record_type__c so that the customer's admin can segment leads from contacts post-migration. The lead-specific fields (lead status, source, score) map to custom Person fields created in Twenty before import.

NetHunt Company records map directly to Twenty Company records. The Company name becomes displayName, domain or website maps to the URL field. Company-specific custom fields migrate to Twenty Company custom fields provisioned via the /metadata API. The folder-based Company schema is captured per-folder during discovery to handle any folder-specific custom field variations.

NetHunt Deals map to Twenty Opportunity records. The deal name becomes the Opportunity name, deal value transfers to the amount field, and stage maps to the Opportunity stage dropdown. NetHunt's multiple pipelines are not a native Twenty feature; we map each NetHunt pipeline to a custom Opportunity field (e.g., pipeline_name__c) or a tag-based segmentation strategy, depending on the customer's preference documented during scoping. Deal owner maps to the Twenty workspace Member by email resolution.

NetHunt supports multiple named pipelines with configurable stages per pipeline. Twenty's Opportunity model uses a single stage dropdown with customizable values. We capture the full pipeline definition (name, stages, probabilities) during discovery and configure Twenty's Opportunity stage picklist to reflect the customer's primary pipeline. For teams using multiple NetHunt pipelines, we create a custom Opportunity field (e.g., source_pipeline__c) to preserve which NetHunt pipeline each deal originated from.

NetHunt Activities attached to Contacts and Deals map to Twenty Task records linked to the corresponding Person or Company. Email content migrates as a Task with a body field; meeting records preserve title, date, and attendees. We use Twenty's REST API for task creation with rate-limit handling (100 or 200 calls per minute depending on tier). Activity ordering is preserved by setting the task due date to the original NetHunt timestamp.

NetHunt Call Logs are stored as a record type and can be created via POST /records/{recordId}/calls. We migrate call logs with duration, direction (inbound/outbound), and notes as custom Task fields in Twenty. The call disposition value from NetHunt maps to a custom picklist field on the Task. Legacy call data with missing duration fields migrates with a null value flagged for manual review.

NetHunt Record tags migrate as-is to Twenty's Tag system. Tags are simple string values and transfer directly without transformation. We flag any tags that may conflict with existing Twenty tags during the reconciliation step and document conflicts for the customer's admin to resolve before final import.

NetHunt Folders are the top-level organizational unit containing Records, Views, and Filters. Twenty does not have a Folder equivalent; all records live in the workspace at the object level. We use the folder enumeration step to segment records during migration, and optionally add a custom field (e.g., original_folder__c) to each record to preserve the source folder context for the customer's admin.

NetHunt supports custom fields within Records and Folders, with schema varying by folder. We capture the field definition for each folder before migration (field name, type, required flag, picklist options) and recreate equivalent custom fields in Twenty via Settings → Data Model before any data import. This is a prerequisite step because Twenty's CSV import creates records but not fields. We prioritize fields actually in use over fields that were created but never populated.

Attachments linked to NetHunt Records may be stored in NetHunt's UI or integrated services like DocHub. We migrate attachment URLs and metadata as-is. We verify that linked files remain accessible post-migration and flag any attachments stored exclusively in DocHub or other integrated services that may require re-linking in Twenty. Inline images in note bodies are extracted and migrated as separate URL references.