Migrate from Net-Results to Freshsales

Net-Results Contacts migrate to Freshsales Contact records using email as the dedupe key. Standard fields (first_name, last_name, email, phone, address) map directly. Lifecycle stage metadata from Net-Results maps to Freshsales lifecycle_stage or a custom field if the customer uses custom lifecycle values. Where a Freshsales Contact with the same email already exists, we flag for the customer's admin to resolve whether to skip, merge, or overwrite.

Net-Results Company records map to Freshsales Account records. The company_name field maps to Account Name, and company_domain maps to Account Website. If the source Company has an associated primary Contact, we resolve the Freshsales Contact lookup during the Contact import phase. We flag any Company records that have no associated Contact for admin review before loading.

Net-Results Campaign records (name, status, type, start/end dates) migrate to Freshsales Note records attached to the related Account or Contact. The Campaign name becomes the Note title with campaign metadata stored in Note body text and custom fields. Active campaign status does not migrate as an active workflow; Freshsales does not have a native campaign enrollment object, so the enrollment history is preserved as read-only Note content.

Individual email send events (timestamp, recipient, open/click/bounce status, bounce code) migrate as Freshsales Task records with custom fields: send_date, open_count, click_count, bounce_code, bounce_type. The Task is linked via WhatId to the related Account or Contact. Freshsales does not have a native send-event object, so we replicate the activity history using the Task data model with a custom Task Subtype (e.g., Email Send) to distinguish from standard calls and meetings.

Net-Results email template HTML and asset references export as a structured Note record with the template name as the title and the HTML content in the Note body. We do not import template HTML into Freshsales email composer directly because Freshsales email templates use a different rendering engine. The Note serves as a reference artifact for the customer's admin to rebuild templates in Freshsales using the standard email editor.

Net-Results Automation Workflow definitions do not export as portable artifacts. We export the workflow name, associated contact count, step-count metadata, and trigger type as a Note record per workflow. This Note serves as the handoff artifact for the customer's admin to rebuild the workflow logic in Freshsales Workflows or Freddy AI rules. The workflow enrollment history (which contacts were in which workflow at migration time) is preserved as a custom multi-select field on Contact.

Net-Results suppression list records (hard bounces, unsubscribes, manual suppressions) migrate as Freshsales Contact records with HasOptedOutOfEmail set to true and a suppression_type custom field indicating the source (bounce, unsubscribe, manual). If the Freshsales destination already has existing suppression records, we deduplicate against them to avoid false opt-out flags on valid active contacts. We run the suppression pass as a post-load cleanup step after all active contacts are loaded.

Net-Results custom fields on Contacts and Companies require explicit field-level mapping against Freshsales custom fields created before migration. We inventory all custom fields during discovery, map each to a Freshsales custom field of matching type (text, number, date, dropdown), and apply the mapping during the load phase. Custom fields that have no equivalent in Freshsales (e.g., Net-Results-specific segmentation fields) are mapped to text fields and flagged for admin review.

Net-Results Owners map to Freshsales User records resolved by email match. Any Net-Results Owner without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on Contact, Account, and Email Send records is set after User resolution completes.