Migrate your Oracle Eloqua data

Contacts are the primary object in Eloqua. We export full contact records including standard fields, custom fields, activity history, and contact dates. All field merge tokens and personalization strings are preserved. The destination system receives Contacts as standard Contact/Person records.

Eloqua Accounts model organizational records tied to Contacts. We map Accounts to Companies or Organizations in the destination. Account-level fields and account-to-contact associations are preserved during migration.

CDOs are customer-defined objects that store enrichment data. Each CDO has its own schema and fields. We export CDO records and map them to equivalent custom objects or entity records at the destination. Field-level type mapping (string, numeric, date, picklist) is required since CDO schemas vary per customer.

Eloqua Campaigns are multi-step orchestration containers. We export campaign metadata, step structure, and targeting criteria. Because campaign logic (wait steps, conditions, triggers) is tightly coupled to Eloqua's execution engine, we preserve the campaign architecture and document rebuild requirements for the destination platform's equivalent campaign builder.

Segments define dynamic contact audiences based on filter criteria. Shared Lists are static contact collections. We export segment filter definitions and list memberships. Dynamic segment logic must be rebuilt at the destination using equivalent filter builders, while list membership transfers as static contact records.

Email assets include HTML content, subject lines, sender/reply-to addresses, and metadata. We export email HTML and configuration data. Design rendering depends on the destination email builder's capabilities; we flag any dynamic content or field merge tokens that may behave differently in the target system.

Eloqua forms capture contact data and can be embedded on landing pages. We export form field configurations and landing page metadata. The visual design and layout of landing pages require rebuild at the destination. Form fields map to destination form fields by name and type.

Eloqua's Lead Scoring models, including weighted demographic scores and behavioral scores, are stored in proprietary configuration that has no export mechanism. We document the current scoring model structure and recommend rebuilding it in the destination system using the exported contact activity history as reference data.

Eloqua tracks engagement events (email opens, clicks, form submissions, page visits) as activity records linked to Contacts. We export activity data and map it to the destination's engagement or activity object. Note that activity data volume can be large; scoping is required to avoid transfer timeouts.

Picklists define controlled vocabulary for custom fields. Eloqua provides export and import for picklists as CSV, including both display names and stored values. We export picklist definitions and re-import them at the destination to preserve data integrity for fields using picklist constraints.

Email and landing page images stored in Eloqua's asset library can be exported via bulk API. We download assets and re-upload to the destination asset library. Images embedded via external URLs are preserved as-is if the URLs remain accessible.