Migrate from Oracle Eloqua to Pipedrive

Eloqua Contacts map to Pipedrive People. The Contact's email address becomes the Person's primary email and serves as the dedupe key during import. Standard Eloqua fields (first name, last name, phone, address) map to Pipedrive Person fields. Custom fields on the Contact record map to Pipedrive custom Person fields. We resolve the Contact-to-Account association and populate the Person's linked Organization field from the mapped Organization record. Any Eloqua contact without an email address is flagged and held for customer review because Pipedrive requires an email for Person creation.

Eloqua Accounts map to Pipedrive Organizations. Account name becomes the Organization name, and Account website becomes the Organization's website field. We use Account website as a secondary dedupe key alongside Account name. Account-level custom fields map to Organization custom fields in Pipedrive. Organization must be created before Person import so that the Organization-Person link is satisfied at insert time.

Each CDO in Eloqua has an independent schema. We extract CDO records, flatten them, and map them to custom fields on the target Person or Organization based on the CDO-to-Contact relationship defined during discovery. If a CDO has a 1:1 relationship with a Contact, its fields become Person custom fields. If the CDO relates to an Account, its fields become Organization custom fields. Multi-value CDO fields (arrays, multi-select) become Pipedrive text fields with comma-separated values. We flag any CDO with more than 20 custom fields as a candidate for a separate custom Pipedrive deal or note structure to avoid hitting the custom field count limit per object.

Eloqua Campaigns have no direct Pipedrive equivalent. Pipedrive does not have a native campaign management or multi-step orchestration object. We document every active Eloqua Campaign during discovery, including targeting criteria, step structure, and status. If the Campaign is primarily a contact list or segment, we create a Pipedrive static list or tag association. If the Campaign tracks a sales nurture sequence, we represent it as an Activity note on the associated Person record with the campaign name, start date, and current status. The customer's admin rebuilds active campaign logic in Pipedrive's Activity-based workflow model or a connected automation tool.

Eloqua Programs are step-based operational containers within Campaigns. We export Program metadata (name, type, associated contacts) and represent it in Pipedrive as an Activity (type=Task or Note) linked to the Person or Deal. Program step progression that represents a lead stage (e.g., MQL to SQL) can be recorded as a Person custom field update or a Deal note. Complex multi-step Programs require a separate rebuild in Pipedrive's Activity and Automation framework.

Eloqua Segments define dynamic contact audiences based on filter criteria. Shared Lists are static contact collections. We export segment membership and list membership for each Contact. Membership in a named Eloqua list or segment becomes a Pipedrive tag on the Person record. Dynamic segment filter logic is documented and cannot be directly migrated because Pipedrive has no dynamic segment equivalent. The customer's admin rebuilds dynamic segmentation logic using Pipedrive's filter views or an automation tool.

Eloqua Email assets include HTML content, subject lines, and sender metadata. We export email subject lines, from addresses, and HTML content as a reference document delivered alongside the migration. Pipedrive has no native email asset library. The customer's admin imports email templates into Pipedrive's email template library manually or via a third-party email template tool. Email rendering depends on Pipedrive's email editor capabilities, which differ from Eloqua's template system.

Eloqua Forms capture contact data and can be embedded on landing pages. We export form field configurations and submission data as Activity notes on the Person record (type=note with form name, submission date, and field values). Form field logic and embedded placement cannot be migrated. We document every active Eloqua Form for the customer's admin to rebuild in Pipedrive's form tool or a third-party alternative.

Eloqua tracks engagement events (email opens, clicks, form submissions, page visits) as activity records linked to Contacts. We export engagement data and map each event type to a Pipedrive Activity: form submissions become Tasks with the form name as the subject; email click events become Notes with the clicked URL and timestamp; page visits with sufficient Eloqua configuration become Notes. High-frequency engagement events (every open and click) are aggregated by Contact to avoid creating hundreds of individual Activity records per Person. We discuss the aggregation strategy with the customer during scoping.

Eloqua Lead Scoring models, including weighted demographic scores and behavioral scores, are stored in proprietary configuration with no export mechanism. We document the current scoring model structure during discovery: scoring categories, weights, thresholds, and which Contact fields feed the score. This documentation is delivered as a written inventory. The customer's admin rebuilds scoring logic in Pipedrive using custom number fields updated manually or via automation rules, or selects a third-party scoring add-on from the Pipedrive Marketplace.

Eloqua Picklists define controlled vocabulary for custom fields. We export picklist definitions (display names and stored values) and recreate them as options on the corresponding Pipedrive custom field (single-select or multi-select picklist type). If a picklist value is missing from the destination custom field options, we add it during migration to prevent data loss.