Migrate from Oracle Eloqua to Zoho CRM

Eloqua Contacts map directly to Zoho CRM Contacts. Standard fields (First Name, Last Name, Email, Phone, Address) map to Zoho's typed fields; custom fields map to Zoho CRM custom fields created during schema pre-build. We apply the email address as the dedupe key during import to prevent duplicate records. Marketable contact status from Eloqua's ContactType field is preserved as a custom picklist value (Marketable, Non-Marketable) in Zoho so that email compliance status is available for Zoho Campaigns and compliance audits.

Eloqua Accounts map to Zoho CRM Accounts. The Account Name, Website (domain), Industry, and Employee Count fields map directly. Account-to-Contact associations in Eloqua (the relationship between an Account and its Contacts) are preserved through the Zoho CRM lookup relationship by importing Accounts before Contacts and resolving the Zoho Account reference ID at Contact insert time.

Eloqua CDOs have independent schemas that vary by customer implementation. We export each CDO's full record set via Bulk API, map its fields to Zoho CRM Custom Modules created with matching field types (text, number, date, picklist, lookup), and resolve any lookup relationships to standard Zoho CRM objects or other Custom Modules before import. CDO-to-CDO relationships map to Zoho CRM lookup fields between Custom Modules.

Eloqua Campaigns (multi-step orchestration containers) have no direct Zoho CRM equivalent because Zoho Campaigns and CRM Campaigns serve a different purpose (event and communication tracking versus multi-channel program orchestration). We export campaign metadata (name, start/end date, status, description) as a Zoho CRM Campaign record. Campaign logic, step structure, and targeting criteria are documented in a written Campaign Architecture Inventory delivered to the customer's admin for manual rebuild in Zoho CRM Workflows or BluePrint processes.

Eloqua Programs are program instances within a Campaign container. We export Program metadata (name, type, status) to Zoho CRM Campaigns. The program member contacts migrate to Zoho CRM Contacts with a custom campaign membership field. Automated wait steps, condition branches, and trigger logic in Programs do not migrate; they are documented in the Campaign Architecture Inventory for manual Zoho CRM workflow reconstruction.

Eloqua Segments (dynamic filter-based audiences) and Shared Lists (static contact collections) define which Contacts belong to a given program or campaign. We export segment filter definitions and list memberships. Dynamic segment filter logic cannot be replicated automatically in Zoho CRM because Zoho does not have a real-time segmentation engine equivalent to Eloqua's. We deliver the segment filter definitions as a written reference for the admin to apply manually using Zoho CRM Advanced Filters or Workflow conditions. Static list memberships are preserved by tagging each Contact with the relevant list names.

Eloqua tracks email opens, clicks, form submissions, and page visits as Contact-level activity records. We export activity data via Bulk API and map it to Zoho CRM Tasks (for call logs, emails, and form submissions) and Notes (for engagement metadata). The original activity timestamp is preserved as the Zoho Task Activity Date for timeline ordering. Zoho CRM does not have a native behavioral scoring engine; activity data lands as historical record entries rather than Eloqua-style engagement scores.

Eloqua Email Assets (HTML content, subject lines, sender configuration) can be exported as HTML files via the Bulk API asset download. We extract the HTML and download linked images to re-upload to Zoho CRM's Email Templates. However, the email rendering engine in Zoho CRM differs from Eloqua's; HTML templates may require adjustment for compatibility. We deliver the exported assets and recommend the customer's admin review template rendering in a Zoho CRM sandbox before production send.

Eloqua Forms (field configurations, submission routing, and thank-you page settings) have no export mechanism that preserves field logic and routing. We document the form field list, field types, required flags, and submission routing as a written Form Inventory. The customer's admin rebuilds forms in Zoho CRM's native Web Forms or Zoho PageSense as part of the post-migration workflow rebuild.

Eloqua Picklists define controlled vocabulary for custom fields. We export picklist definitions as CSV (display name and stored value) and recreate them as Zoho CRM Picklist fields during the schema pre-build phase. Both the display labels and internal values are preserved to maintain data consistency. Picklist options that do not yet exist in Zoho are created before the relevant record import phase.

Eloqua's weighted Lead Scoring models (demographic scores, behavioral scores, and opportunity influence scores) have no export mechanism and no direct Zoho CRM equivalent. We document the current scoring model in a Lead Scoring Architecture Inventory delivered to the customer, including weights, thresholds, and triggers. The customer's admin rebuilds basic lead scoring using Zoho CRM's Scoring Rules (available in Professional and above) or Workflow-based automation. This is the highest-impact manual rebuild item for teams relying heavily on lead scoring.

Eloqua Users (Campaign Owners, Program Owners) map to Zoho CRM Users. We extract distinct Owner IDs and email addresses from Contact, Account, Campaign, and Program records and match by email against Zoho CRM's User table. Any Eloqua Owner without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision before the record import phase begins.