Migrate from Oracle Eloqua to Freshsales

Eloqua Contacts map directly to Freshsales Contacts. Standard fields including First Name, Last Name, Email, Phone, Address, and Title transfer with direct field mapping. We preserve unsubscribe and consent flags in Freshsales contact_fields.emailStatus or custom subscription fields, and we flag contacts with unsubscribed status explicitly to prevent Freshsales email sending to those addresses. Custom contact fields map to Freshsales custom fields on Contact. We resolve the primary Account lookup by matching Eloqua Account name or domain to Freshsales Account records.

Eloqua Accounts map to Freshsales Accounts (Organizations). Account-level fields including company name, industry, website, address, phone, and revenue transfer as direct field mapping. Account-to-contact associations migrate so that the primary contact relationship is preserved. We use Account domain or company name as the dedupe key during import to avoid duplicate Account creation.

Eloqua CDOs are independent objects with their own schemas. Freshsales does not support standalone custom objects with separate API endpoints; enrichment data stored in CDOs must map to custom fields on the Contact or Account object. We pre-create the equivalent custom fields in Freshsales during schema setup, map CDO record fields to the correct contact or account reference, and document any CDOs that have no natural home in Freshsales' standard object model for the customer's admin to address.

Eloqua Campaigns are multi-step orchestration containers with wait steps, conditional branches, and trigger-based execution. Freshsales has no equivalent campaign canvas. We export campaign metadata (name, dates, targeting criteria) as a written inventory document. For campaigns that represent sales-oriented milestones or deal stages, we create Freshsales Deals with campaign name and dates as reference data. Active campaign logic does not migrate; it requires rebuild in Freshsales Workflows or sequences.

Eloqua Segments define dynamic contact audiences based on filter criteria. Shared Lists are static contact collections. Freshsales supports contact filters and lists but uses different filter logic. We export segment definitions and list memberships as reference data. The customer's admin rebuilds dynamic segments as Freshsales contact filters post-migration. Shared list membership transfers as contact tag or custom field assignments for static list recreation.

Eloqua tracks engagement events (email opens, clicks, form submissions, page visits) as activity records linked to Contacts. Freshsales does not have a native engagement analytics model for marketing interactions. We migrate significant engagement history as Notes on the Contact record with the engagement type, timestamp, and detail preserved as note content. Email click and open data from Eloqua converts to Freshsales contact activities with a descriptive activity title. Form submission history migrates as note records documenting the submission.

Eloqua email assets include HTML content, subject lines, and sender configuration. We export email HTML and map it to Freshsales email templates. Design rendering depends on Freshsales' template builder capabilities; complex HTML emails with dynamic content blocks may require simplification. Subject lines, sender names, and reply-to addresses transfer to Freshsales template configuration.

Eloqua's weighted demographic and behavioral Lead Scoring models are stored in proprietary configuration with no export mechanism. We document the current scoring model structure including weights, thresholds, and contributing factors during the discovery phase and deliver this as a written specification. Freshsales Freddy AI provides predictive lead scoring but uses a machine learning model rather than manual weight configuration. The customer's admin uses the Eloqua scoring documentation as input when setting up Freddy AI scoring goals and thresholds in Freshsales.

Eloqua forms capture contact data and can be embedded on landing pages. Freshsales does not have a native form builder equivalent to Eloqua's form functionality. We export form field configurations and landing page metadata as a written reference document. The customer's admin rebuilds forms in Freshsales web forms or a third-party form tool, and landing pages require rebuild in Freshsales' page builder or an external tool. Form submission history data migrates as engagement notes on the contact record.

Eloqua picklists define controlled vocabulary for custom fields. We export picklist definitions including display names and stored values as CSV and re-create them as Freshsales picklist fields or custom field options. Standard picklists like Industry, Country, and State transfer with direct value mapping. Any picklist values not present in Freshsales' standard field options create as custom picklist values on the equivalent Freshsales custom field.