Migrate from eTrigue to Pipedrive

eTrigue Prospects map 1:1 to Pipedrive People. Standard fields (name, email, company, phone, address) export cleanly from the Prospects CSV and map to Pipedrive's typed Person fields. We use email address as the dedupe key. All five Lead Score sub-fields (Campaign Score, Activity Score, Source Score, Relationship Score, Buy Time Score) migrate as individual numeric custom fields on the Person record so the customer can recombine them inside Pipedrive or a third-party scoring tool.

eTrigue stores company name as a text field on the Prospect record. We extract unique company names from Prospects, deduplicate, and create Organization records in Pipedrive before importing Persons. The Organization becomes the parent of the Person record via the linked_id relationship, satisfying Pipedrive's data model requirement that People attach to Organizations for full CRM functionality.

eTrigue's Status field exports numeric codes (e.g., 1 = Active, 2 = Opt-Out) rather than human-readable labels. We decode these during data profiling before import and map to Pipedrive's Activity labels or to a custom picklist field that the customer's admin configures. If Status is used as a filter for active-only migrations, we exclude records with Status = Opt-Out code unless the customer requests full export including unsubscribed records.

Each eTrigue Prospect's Activity History records email opens, form submissions, page views, and campaign responses with timestamps. We export this as a structured activity log and map each entry to Pipedrive Activity records with activity_type set to email, call, meeting, or note and ActivityDate set to the original timestamp. The Person or Organization linked to the Activity resolves via email or company name match. Large histories (thousands of rows per Prospect) are chunked into batches during import to avoid payload size limits.

eTrigue Campaigns have no direct Pipedrive equivalent because Pipedrive organizes around Deals rather than Campaigns. We map Campaign names to a custom text field on the Person record (original_campaign__c) and create Activity records that capture campaign response context. If the customer uses Pipedrive's optional Campaign object (Professional tier and above), we map campaign names there and link Activities via a custom Campaign relationship. Partner-specific campaign attribution from Lead Accelerator maps to the Organization record's partner_program__c field.

eTrigue's 3D Lead Scoring enriches the standard composite score with content-type engagement weighting. The 3D score value exports as a separate numeric field. We map it to a custom field score_3d__c on the Person record and flag that Pipedrive's native scoring model requires manual rebuild or a third-party scoring app from the Pipedrive Marketplace. The customer's admin decides how to weight the five sub-scores in Pipedrive's own scoring tool post-migration.

eTrigue supports Boolean, Text, and other custom field types defined in Settings > Prospect Settings > Prospect Fields. Boolean fields store true/false with custom labels per value. We map these to Pipedrive's equivalent custom field types (checkbox for Boolean, text for Text, picklist for single-select, multi-select for multi-checkbox). We pre-create the custom fields in Pipedrive before import so the CSV column headers match Pipedrive field names exactly.

eTrigue Content Types classify prospect engagement with different content categories. We export these as tag values and map to Pipedrive custom multi-select fields on the Person record. If Content Types represent distinct content themes (whitepaper, webinar, case study), each unique value becomes a multi-select option so the sales team can filter by acquisition source content.

Lead Accelerator customers using eTrigue for partner channel programs store partner organization names and partner-specific campaign attribution in custom Prospect fields rather than a dedicated Partner object. We extract unique partner organization names, create Organization records in Pipedrive (type = Partner), and link the original prospect Person to the Partner Organization. Any partner-specific scoring rules are flagged in a separate Partner_Scoring_Rebuild document for the customer's admin.

eTrigue's Scheduled Exports feature uses saved search criteria to produce recurring CSV exports. Pipedrive has no scheduled export equivalent at the object level. We document the active scheduled export criteria used in eTrigue so the customer's admin can configure equivalent Pipedrive Saved Filters and potentially automate CSV exports via Pipedrive's API for any ongoing reporting requirements.