Migrate from Net-Results to Nutshell

Net-Results Contact records map directly to Nutshell People records with role Contact. Name, email, phone, and address fields map to their Nutshell equivalents. Lifecycle metadata (lifecycle_stage, created_date, last_modified_date) preserves as Nutshell People fields. The Nutshell API renders custom fields inside the customFields dictionary keyed by field name.

Net-Results Company records map to Nutshell Account records. The company_name field maps to Account name; domain maps to Account website as the dedupe key. Accounts are created before People import so that the People-to-Account lookup relationship is satisfied at insert time.

Net-Results Contacts that represent unqualified prospects (typically those with no associated Company or no deal history) split into Nutshell Lead records. We evaluate the contact's lifecycle stage and associated deal count at migration time to determine the split. Leads without a matching Account are created as standalone Leads; Leads associated with a migrated Account link via the AccountId field.

Net-Results Campaign records migrate to Nutshell Activity records with the campaign name, status, dates, and type preserved in Activity metadata fields. The Nutshell Activity model does not have a native campaign object, so we tag each activity with a campaign_name field and link related activities by campaign during migration to preserve the grouping context for the customer's reporting.

Net-Results Email Send records (opens, clicks, bounces, sends) migrate to Nutshell Activity records. Send timestamp maps to Activity.activity_date; open/click events map to separate Task records with activity_type = email_event; bounce codes preserve in a custom activity field. Some destinations do not have a native send-event object, so we flatten the send history into activities linked to the parent People record.

Net-Results email template HTML exports with image asset references. The drag-and-drop rendering structure may not render identically in a non-Net-Results email platform. We export all template HTML and image URLs to a structured folder and flag every template for manual review before use in the customer's replacement email marketing platform (Brevo, Mailchimp, or similar). We do not import templates directly into Nutshell because Nutshell has no native email marketing module.

Net-Results Automation Workflows define trigger-and-action sequences that do not export as portable artifacts. We capture the workflow name, enrolled contact count, step count, and trigger type for every active workflow and deliver this as a written inventory document. The customer's admin rebuilds equivalent logic in Nutshell Rules (the automation engine) post-migration. We do not migrate workflow logic as code.

Net-Results suppression records (hard bounces, unsubscribes, manually suppressed contacts) export and merge against Nutshell People records as opt-out flags. We run a deduplication pass against any existing opt-out records in the destination to avoid false unsubscribes on valid active contacts. Hard bounces and unsubscribes set the HasOptedOutOfEmail flag on the relevant People record in Nutshell.

Net-Results custom fields on Contacts and Companies require explicit mapping against Nutshell's customFields schema. Text, date, numeric, and checkbox field types map directly. Multi-select and lookup fields require case-by-case evaluation based on the destination field type. We inventory all custom fields during discovery and apply a field-by-field mapping before load. Nutshell requires custom fields to be pre-created in the UI before API-based imports can populate them.

Net-Results Custom Objects (defined under Administration > Custom Objects with standard fields and custom fields) do not have a direct Nutshell equivalent because Nutshell does not support standalone custom object types. We evaluate each Net-Results Custom Object: if it represents a one-to-many relationship (e.g., Tours per Contact), we create a custom text or JSON field on the Nutshell People record to store the key reference data, or we flatten the most important fields into custom fields on the parent record. The customer chooses the flattening strategy during scoping.