Migrate from Net-Results to Salesforce Sales Cloud

Net-Results Contacts with lifecycle stage of subscriber, lead, or marketing-qualified lead map to Salesforce Lead. Contacts with lifecycle stage of sales-qualified lead, opportunity, customer, or evangelist map to Salesforce Contact attached to an Account. We compute the split at migration time using Net-Results lifecycle_stage and lead_status properties and preserve the original Net-Results lifecycle stage in a custom field nr_original_lifecycle__c on both Lead and Contact for audit and reporting continuity.

Net-Results Company records map directly to Salesforce Account. The company domain field maps to Account Website and is used as the dedupe key during import. We create the Account before any Contact import so that the AccountId lookup is satisfied at Contact insert time. Company-level custom properties map to custom Account fields catalogued during discovery.

Net-Results Campaign records map to Salesforce Campaign. Campaign name, status (active, paused, archived), start date, and end date migrate directly. Campaign type maps to Salesforce Campaign Type picklist. We attach Email Sends and Automation Workflow metadata to the Salesforce Campaign as Notes and custom activity fields since Salesforce has no native automation enrollment object.

Net-Results Email Sends (individual send events with opens, clicks, and bounces) migrate to Salesforce as a Task record (the activity timeline entry) plus an EmailMessage record (the email content and engagement metrics). Task WhoId points to the migrated Lead or Contact; Task WhatId points to the related Campaign or Account. Send timestamp, open count, click count, and bounce code migrate to custom Task fields. Large send histories (over 200,000 records) require Bulk API 2.0 with batch chunking.

Net-Results Automation Workflow definitions cannot be exported as portable logic. We capture the workflow name, enrollment date, workflow step count, and last activity date for each contact enrolled in each workflow and store this as a Note on the Contact record plus a custom multi-select picklist nr_workflow_names__c listing enrolled workflow names. This metadata becomes the reference document the customer's Salesforce admin uses to rebuild equivalent logic in Salesforce Flow.

Net-Results drag-and-drop email templates export as HTML with embedded image URLs. We export the template body and asset references but note that layout may reflow or break when imported into Salesforce's email template format due to differences in the rendering engines. We flag all templates for manual review post-migration and advise previewing sends before launching campaigns from imported assets.

Net-Results suppression records (hard bounces, unsubscribes, manually suppressed contacts) export as a suppression list and apply as a post-load cleanup pass. Hard bounces set HasOptedOutOfEmail to true on the migrated Contact or Lead. Unsubscribes set HasOptedOutOfEmail to true and add a CampaignMember Status of Unsubscribed to any relevant Salesforce Campaign Members. Where the destination org already has existing suppression records, we deduplicate against them to avoid false opt-out flags on valid active contacts.

Custom fields on Net-Results Contacts require explicit field-by-field mapping against the Salesforce schema before any load. We inventory all custom contact properties during discovery, map each to an equivalent Salesforce custom field (with the correct data type — text, number, date, picklist, checkbox), and deploy the destination schema via metadata API or change set into Sandbox before data migration begins. Custom fields without a destination equivalent are flagged for the customer to create or convert to a Notes-and-Attachments approach.

Net-Results Company custom fields map to Salesforce Account custom fields using the same explicit field-by-field approach as Contact custom fields. Company domain, industry, employee count, and revenue fields that exist in Net-Results are mapped to their Salesforce Account field equivalents where available, with remaining custom fields deployed as custom Account fields before migration.

Net-Results owners referenced on Contact, Company, and Campaign records are resolved by email match against the destination Salesforce org's User table. Any Net-Results Owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId must be resolvable on every standard object insert, making this a required pre-migration step.

Net-Results tracks lifecycle stage transitions over time as a property history log. Salesforce has no native equivalent to contact lifecycle stage history. We migrate the most recent lifecycle stage value as nr_original_lifecycle__c and store a JSON-encoded stage transition log in a long-text custom field nr_lifecycle_history__c for audit and reporting purposes. The customer can use this data to configure Salesforce path stages or reporting snapshots if needed.

If Net-Results contains product records used in campaign tracking or suppression by product interest, we migrate them to Salesforce Product2. Net-Results product_name maps to Product2 Name and product_code maps to Product2 ProductCode. Standard Price Book entries are created during import so that migrated Opportunity records can reference price books if the customer also migrates deal history.