Migrate from Net-Results to Zoho CRM

Net-Results Contacts map directly to Zoho CRM Contacts for most migrations. If Net-Results stores prospect lifecycle data (e.g., subscription tiers, engagement scores) that warrants separating unqualified prospects from active buyers, we apply a split rule during scoping: Contacts with no associated Campaign activity or with a 'subscriber' tag map to Zoho Lead; active buyers with Campaign history map to Zoho Contact attached to an Account. We preserve the original Net-Results contact ID as a custom field nr_original_id__c for deduplication if a second migration pass is needed.

Net-Results Company records map to Zoho CRM Accounts. The company_name and domain fields become Account Name and Website respectively. Account is created before any Contact import so that the Contact-to-Account lookup (Account Name field or lookup field) is satisfied at the moment of Contact insert. Any custom company properties (industry, employee count, annual revenue) map to Zoho custom fields that we provision before load.

Net-Results Campaigns (discrete marketing initiatives with name, status, dates, and type metadata) map to Zoho CRM Campaigns if the customer uses Zoho's native Campaigns module. If Zoho Campaigns is not active in the destination tenant, we create a custom Campaign module with fields for campaign name, status, start/end dates, type, and associated contact count. The campaign-contact linkage migrates as Campaign Member records linking Zoho Contacts to the Campaign.

Individual email send events from Net-Results (timestamps, open rates, click rates, bounce codes) migrate to Zoho CRM Activity records. We use the Zoho CRM Tasks object to capture send metadata: Subject = campaign name + ' send', Description = engagement metrics, Activity Date = send timestamp. Bounce events generate separate Task records with Status = 'Not Started' and Category = 'Bounce' to flag suppression candidates. Open and click events migrate as custom Activity sub-types if Zoho workflow rules require segmentation.

Net-Results email template HTML and image asset references export as-is. We flag every template for manual review post-migration because Net-Results' drag-and-drop rendering engine produces HTML that may reflow or break in Zoho Campaigns. Template import into Zoho is documented as a post-migration step; the customer tests each template with a send preview before launching campaigns from imported assets.

Net-Results workflow definitions (trigger conditions, action sequences, enrollment criteria) do not export as portable code. We capture the workflow name, associated contact count, step count, and trigger type for each active workflow and deliver a written Blueprint design document with Net-Results-to-Zoho Workflow Rule and Blueprint equivalents. The customer's Zoho admin rebuilds each workflow in Zoho's automation tools post-migration.

Net-Results suppression lists (hard bounces, unsubscribes, manually suppressed contacts) export as a contact-level flag pass after the primary Contact migration. We compare the Net-Results suppression list against existing Zoho Contacts and set HasOptedOutOfEmail = true on matching records without overwriting existing contact data. If a contact in Zoho does not yet exist in Net-Results' suppression list, we do not create a new Zoho record from the suppression entry.

Net-Results custom fields on Contacts require explicit field-by-field mapping against Zoho's Contact module schema. We inventory all custom fields during discovery, provision equivalent custom fields in Zoho (with appropriate field types: text, number, date, picklist, checkbox, multi-select), and apply a mapping document before Contact load. Custom field data migrates in the same import pass as standard fields.

Net-Results custom fields on Companies map to Zoho Account custom fields using the same field-by-field inventory and provisioning process as Contact custom fields. All custom Account fields are created in Zoho before the Account import phase begins.

Net-Results Owners (users who own Contacts, Companies, and Campaigns) map to Zoho CRM Users by email address match. We resolve each distinct owner email against the destination Zoho org's User table. Owners without a matching Zoho User enter a reconciliation queue for the customer's admin to provision before record import resumes, because Zoho Activity records require an OwnerId reference.

Net-Results contact tags (stored as multi-value properties on Contact records) migrate to Zoho CRM multi-select picklist fields on the Contact module. We inventory all distinct tag values during discovery and configure the picklist with those values as allowed options before migration. Tags used for segmentation migrate as Contact custom fields; tags used for classification migrate as a separate multi-select field.