Migrate from Net-Results to Microsoft Dynamics 365 Sales

Net-Results Contacts with campaign enrollment history and no associated Company record map to Salesforce Lead or Microsoft Dataverse Contact depending on whether they represent a qualified sales prospect. We evaluate the contact's last campaign type, email engagement score, and any manual owner assignment to determine the split. Contacts with a Net-Results Company affiliation and at least one sales-associated campaign map to Dynamics 365 Contact linked to an Account. The original Net-Results contact ID is preserved in a custom field nr_original_contact_id__c for audit and reconciliation.

Net-Results Company records map directly to Microsoft Microsoft Dynamics 365 Sales Account. The Company domain field becomes the Account Website; Company name maps to Account Name. Net-Results Company records that lack a company_name are reconciled using the primary Contact's domain during migration. Account is created before any Contact import so the Contact-Account lookup relationship is satisfied at insert time.

Net-Results Campaigns map to Microsoft Dynamics 365 Sales Campaign. Campaign name, status, start and end dates, and campaign type migrate as Campaign fields. The Dynamics 365 Campaign object stores campaign metadata; we do not migrate campaign member tracking as Salesforce-style Campaign Members because Net-Results does not track explicit campaign membership in a comparable structure. Associated email send history is linked via a custom relationship field.

Individual email send events (send timestamp, open, click, bounce) from Net-Results migrate to Dynamics 365 as Note records or EmailMessage records linked to the corresponding Contact or Lead. Open and click events are preserved as custom fields on the note or as separate Task records with activity timestamps. Because Microsoft Dynamics 365 Sales does not have a native send-event object, we use the closest equivalent and flag the approach during scoping so the customer can decide whether send-level granularity is required for reporting or whether summary campaign activity is sufficient.

Net-Results suppression records (hard bounces, unsubscribes, manual suppressions) are exported and applied as a post-load cleanup pass against Dynamics 365 Contact records. We match by email address and set Dynamics 365's standard EmailOptOut field to true for unsubscribes and a custom nr_suppression_reason__c field for hard bounces. If the Dynamics 365 destination already contains existing suppression records, we deduplicate before applying the Net-Results list to avoid false opt-out flags on valid active contacts.

Net-Results workflow automation logic does not export as a portable artifact. We capture the workflow name, associated contact count, step count, and trigger conditions for each active workflow and deliver a written automation inventory. The inventory maps each workflow to an equivalent Microsoft Dynamics 365 Sales Flow (record-triggered, scheduled, or desktop flow) and documents the recommended rebuild steps. Workflow rebuild is outside the migration scope and is performed by the customer's admin or a Dynamics 365 partner.

Net-Results drag-and-drop email templates export as HTML and image asset references. We export the template HTML, inline CSS, and image URLs. Because Net-Results uses its own rendering engine, template layout may reflow or break when imported into Microsoft Dynamics 365 Sales email templates or Dynamics 365 Marketing. We flag all templates for manual review post-migration, advise customers to preview sends before launching campaigns from imported assets, and note that image hosting may need to be relocated from Net-Results' CDN to Dynamics 365's native asset library or an external CDN.

Net-Results custom fields on Contacts and Companies require explicit mapping against the Microsoft Dynamics 365 Sales Dataverse schema. We inventory all custom fields during discovery, evaluate the destination field type (text, integer, decimal, datetime, picklist, lookup), pre-create any missing custom fields in the Dynamics 365 environment, and apply a field-by-field mapping before load. Custom field values migrate as data; the field schema creation is a prerequisite completed before any record import begins.