Migrate from Oracle Eloqua to monday CRM

Eloqua Contacts migrate to Monday.com CRM People items. We extract first name, last name, email address, phone, title, and address fields and map them to the corresponding People item columns. Any custom contact fields from Eloqua map to custom columns on the People item, with field type conversion (Eloqua text fields become monday.com text columns, date fields become date columns, picklist fields become dropdown or tag columns). The primary email address is used as the dedupe key during import. Contacts without a valid email address are flagged in the reconciliation report for manual review.

Eloqua Accounts migrate to Monday.com CRM Company items. We map account name, website, industry, employee count, annual revenue, and address fields. The Account-to-Contact relationship is preserved by resolving the Company item linked to each People item during import. Company dedupe uses domain matching (Account Website field). Any custom account-level fields map to custom columns on the Company item.

Eloqua CDOs each have independent schemas that we map to Monday.com custom item types or to dedicated boards. We export CDO records via the Bulk API, extract the field schema, and create matching Monday.com column structures before loading data. CDO records that reference Contacts or Accounts migrate with lookup links to the corresponding People or Company items. CDOs with inter-record relationships (CDO-to-CDO lookups) require a dependency-aware import sequence and may need to flatten into separate columns in Monday.com if the platform does not support multi-level lookups on the customer's plan tier.

Eloqua Campaigns and Programs define multi-step orchestration logic (wait steps, conditional branches, trigger conditions) that is tightly coupled to Eloqua's campaign execution engine. These do not migrate as functional objects. We export campaign metadata (name, type, targeting criteria, start and end dates) and deliver a written inventory document describing each Campaign's structure, step logic, and contact count. The customer's team uses this inventory to design equivalent Automations or Board Views in Monday.com CRM post-migration.

Eloqua Segments are dynamic filter definitions that evaluate contact properties at send time; Shared Lists are static contact collections. Dynamic segment logic has no direct equivalent in Monday.com CRM because the platform does not support live dynamic audience queries. We export Shared List memberships (the static set of contact IDs in each list) and map them to Groups or Views within the relevant People board, or to a dedicated tagging strategy. Dynamic segment filter definitions are documented for manual rebuild as monday.com Filters.

Eloqua Lead Scoring models (weighted demographic scores and behavioral scores per Contact) are stored in proprietary configuration with no export mechanism. We document the current scoring model structure including rule weights, demographic factors, behavioral factors, and score thresholds. Monday.com CRM does not include a native lead scoring engine; teams that require scoring rebuild it using monday.com Automations with conditional logic based on custom columns, or integrate a dedicated scoring tool (e.g., MadKudu, Gradient AI, or a custom model). We provide a structured handoff document for this rebuild.

Eloqua tracks engagement events (email opens, clicks, form submissions, page visits) as Activity records linked to Contacts. Monday.com CRM supports activity logging through its native Activity Log and through custom Timeline columns. We migrate engagement events as Activity Log entries or as custom columns on the People item, capturing event type, timestamp, and related asset reference where available. Large engagement histories (exceeding 100,000 records) require chunked export against Eloqua's Bulk API hourly limit of 2,000 records and extended timeline accordingly. Email-level engagement data (opens, clicks) is highest priority; form submission and page visit data migrates where the destination column structure supports it.

Eloqua picklists define controlled vocabulary for custom fields. We export picklist definitions (display name, stored value) and recreate them as Monday.com Dropdown or Tags columns on the relevant item type. Multi-select picklists map to monday.com Tags columns. The mapping between Eloqua stored values and Monday.com display values is preserved in the field mapping document. New picklist values added after migration require manual extension of the monday.com column options.

Eloqua Email Assets include HTML content, subject lines, sender configuration, and asset library images. Monday.com CRM does not include an email marketing module. We export email asset metadata (subject line, send date, contact count, open rate, click rate) as a written report. HTML email templates are exported and delivered as assets for re-upload to the customer's chosen email platform (e.g., Mailchimp, Klaviyo, HubSpot Free). Email sending and tracking must be managed through a dedicated email marketing tool post-migration.