Migrate your Net-Results data

Contacts are the core person records in Net-Results. We export all standard contact fields (name, email, phone, address) plus lifecycle metadata. Where the destination uses a different contact model, we apply a field-level mapping pass before loading.

Company records in Net-Results may store account-level data that maps differently in destination CRMs. We map the company_name and domain fields and flag any custom company properties that lack a direct destination equivalent.

Campaigns represent discrete marketing initiatives. We export campaign metadata (name, status, dates, type) and link associated Email Sends and Automation Workflows to the campaign record during migration.

Individual send events (opens, clicks, bounces) are activity-level records. We preserve send timestamps, open/click rates, and bounce codes. Some destinations do not have a native send-event object, so we aggregate these into campaign activity records.

Templates use a drag-and-drop HTML structure. We export the template HTML and asset references but note that template layout may not render identically in destination systems without reformatting.

Workflows define trigger-and-action sequences. Net-Results workflow logic does not export as a portable artifact. We capture the workflow name, associated contacts, and step-count metadata; the destination team recreates the logic manually or via the destination's workflow builder.

Hard bounces, unsubscribes, and manually suppressed contacts live in suppression lists. We export suppression records to ensure the destination respects opt-out status at migration completion. We flag duplicates where a contact is already suppressed in the target.

Custom fields on Contacts and Companies require explicit mapping against the destination schema. We inventory all custom fields during discovery and apply a field-by-field mapping before load.