Migrate from Oracle Eloqua to Nutshell

Eloqua Contacts map directly to Nutshell People. We export full contact records including standard fields (Email Address, First Name, Last Name, Phone, Job Title), custom fields, and contact dates. The Email Address field serves as the dedupe key during import. We flag unsubscribed, bounced, and non-opt-in contacts early so that their subscription status maps correctly to Nutshell's unsubscribe field to prevent unintended email sends post-migration.

Eloqua Accounts map to Nutshell Organizations. We export Account-level fields including company name, industry, website, and address data. Account-to-Contact associations are preserved during migration so that each Person record has the correct Organization link. Organization is created before Contact import so that the relationship field is satisfied at insert time.

CDOs are customer-defined objects with their own schema. Each CDO has either a one-to-one or one-to-many relationship with Contacts or Accounts. We export CDO records and map them to Nutshell based on cardinality: one-to-one CDOs become custom fields on the linked Person or Organization; one-to-many CDOs (e.g., Purchase History, Event Attendance) are stored as Notes with structured formatting so that each related record is preserved. We document the CDO schema during discovery and present both options to the customer before migration begins.

Eloqua tracks engagement events (email opens, clicks, form submissions, page visits) as activity records linked to Contacts. Nutshell does not have a native engagement tracking equivalent. We export engagement history and merge it into Notes attached to the corresponding Nutshell Person, with the engagement type, timestamp, and asset name preserved in the note body. This preserves the historical context without requiring a field for each engagement event.

Eloqua Email assets include HTML content, subject lines, sender addresses, and metadata. We export email configuration data including subject line templates, sender profiles, and HTML content. Nutshell does not have an email asset library; we deliver the exported HTML and configuration as a structured document that the customer's admin can reference when building emails in Nutshell's email editor or their preferred email tool.

Eloqua Segments define dynamic contact audiences based on filter criteria; Shared Lists are static contact collections. Nutshell supports Tags on People and Organizations and Saved Filters for list-building. We export segment filter definitions and list memberships, then map static list memberships to Nutshell Tags. Dynamic segment logic must be rebuilt manually as Nutshell Saved Filters since the dynamic evaluation engine differs between platforms.

Eloqua Campaigns and Program Canvas workflows are multi-step orchestration containers with conditional logic, wait steps, and trigger-based execution. Nutshell has no campaign orchestration or marketing automation equivalent. We do not migrate campaign logic as code. We export campaign metadata (name, description, targeting criteria, step count) and deliver it as a written inventory document with a rebuild recommendation for the customer's admin to evaluate. Program Canvas flows are similarly documented as process maps.

Eloqua's weighted demographic and behavioral Lead Scoring models have no export mechanism and no Nutshell equivalent. We document the current scoring model structure during discovery, including score thresholds, demographic weights, and behavioral components, and deliver this as a written specification for the customer's admin to evaluate for manual rebuild or third-party scoring integration post-migration.

Eloqua Forms capture contact data and can be embedded on landing pages. We export form field configurations and landing page metadata. Nutshell does not have native form building or landing page capabilities. We deliver a written inventory of active forms with field definitions and submission destinations, and recommend the customer evaluate third-party form tools (Typeform, HubSpot Forms, or similar) to replace Eloqua form capture.

Eloqua Picklists define controlled vocabulary for custom fields. We export picklist definitions as CSV including display names and stored values. Nutshell custom fields can be configured with predefined value lists that serve the same enumeration purpose. We map each Eloqua picklist to a corresponding Nutshell custom field with matching value options.