Migrate from Net-Results to Pipedrive

Net-Results Contact records map directly to Pipedrive Person. Standard fields (first_name, last_name, email, phone, address) map to Pipedrive's typed Person fields. We preserve lifecycle metadata (opt-in date, source, and any scoring properties) as custom fields on the Person record. Email addresses are used as the dedupe key during import to prevent duplicate Person records when Net-Results has multiple Contacts with the same email in different Campaigns.

Net-Results Company records map to Pipedrive Organization. The company_name and domain fields map to name and address fields in Pipedrive. Custom company properties require explicit type-mapped custom fields in Pipedrive. We flag any Net-Results company records that lack a name and either promote a domain or leave the Organization name blank with a note for manual completion.

Net-Results Campaigns have no direct Pipedrive equivalent because Pipedrive does not have a native Campaign object. We preserve Campaign metadata (name, status, start/end dates, type) as custom fields on the related Organization record. If the customer has deal-linked Campaigns, we attach the Campaign name as a custom field on the Pipedrive Deal. This preserves marketing attribution without creating a false deal structure.

Net-Results Email Send events (opens, clicks, bounces, delivery status) map to Pipedrive Activity records linked to the Person. Each send event becomes a separate Activity with a type (email), a note containing the subject line and send timestamp, and a custom field carrying the open/click/bounce status. Pipedrive does not have a native send-event object, so we use Activity as the container to preserve the engagement timeline against the Contact record.

Net-Results suppression records (hard bounces, unsubscribes, manual suppressions) require explicit post-load handling in Pipedrive. We export the full suppression list and apply a flag to the matching Pipedrive Person record (setting email_opt_out or a custom suppression_status field). If Pipedrive already contains active contacts with the same email, we deduplicate against existing records before applying suppression flags to avoid false opt-out on valid active contacts.

Net-Results email template HTML and asset references are exported as raw HTML files. Pipedrive supports email templates with personalization tokens (Person name, Deal value, Activity fields). We deliver the exported HTML as a file package with a mapping note indicating which Net-Results template fields map to which Pipedrive template tokens. Template layout may require manual reformatting because Net-Results' drag-and-drop rendering engine produces different HTML structure than Pipedrive's template engine.

Net-Results workflow definitions are not exportable as portable code. We capture workflow names, associated Contact enrollments, step-count metadata, and trigger conditions during discovery. The migration deliverable includes a written Workflow Rebuild Guide listing every active Net-Results workflow with its trigger, conditions, and recommended Pipedrive Workflow Automation equivalent. Pipedrive's Workflow Automation (Growth and above) supports trigger-based rules (when a Person or Deal is updated, create an Activity) but not all Net-Results workflow patterns map directly. The customer's Pipedrive admin rebuilds the automations post-migration based on the guide.

Net-Results custom fields on Contacts require explicit type-mapped custom fields in Pipedrive. We inventory all Net-Results custom field names, data types, and populated values during discovery, then pre-create the matching Pipedrive custom fields on the Person object before migration begins. Important constraint: Pipedrive does not allow field type changes after creation without recreating the field and reimporting data. We validate type compatibility (text to text, number to number, date to date) during scoping and flag any incompatible mappings for manual resolution before load.

Same constraint as Contact custom fields applies. Net-Results custom fields on Companies map to Pipedrive Organization custom fields. We pre-create the destination fields during the discovery phase and validate that the source field types are compatible with Pipedrive's supported types (text, number, date, phone, address, single-select, multi-select). Multi-select picklists in Net-Results require a corresponding multi-select picklist in Pipedrive.

Net-Results Owner records (sales reps and marketing users) map to Pipedrive Users by email match. We extract every distinct Owner referenced on Contacts, Companies, and Campaigns and attempt to resolve by email against the destination Pipedrive account's User table. Any Owner without a matching Pipedrive User is placed in a reconciliation queue for the customer's admin to provision before record import proceeds. Owner assignments on migrated records default to the migration-initiating user if unresolved at load time.