Migrate from Oracle Eloqua to HighLevel

Discovery and migration scope documentation

We audit the source Eloqua environment: total Contact and Account record counts, CDO schemas and record volumes, Shared List memberships, active Campaign and Program count, email asset count, and engagement history volume. We document every active Program and Segment as a written reference for the customer's admin to rebuild in GoHighLevel. We confirm the GoHighLevel destination workspace, existing Contacts and Companies, and any pre-built custom fields or tags to avoid collision during import. The discovery output is a written migration scope document that defines record counts, object mapping, and items excluded from the migration.

Field mapping and custom field schema preparation

We create a field mapping matrix mapping every Eloqua contact field, account field, and CDO field to its GoHighLevel equivalent or documenting it as a custom field to be created. Custom fields are pre-built in GoHighLevel before any data loads begin. We resolve field type mismatches: Eloqua date fields become GoHighLevel date fields, Eloqua picklists become GoHighLevel drop-down fields, and Eloqua multi-select fields are encoded as tags or multi-select picklists. We flag any field that cannot be mapped to an equivalent GoHighLevel type and propose a workaround or tag-based alternative.

Shared List export and GoHighLevel contact list creation

We export every Shared List from Eloqua as a list of contact email addresses. Each Shared List becomes a GoHighLevel Contact list created before the main contact migration. Lists with over 10,000 contacts are split into sub-lists to avoid GoHighLevel import timeout issues. Dynamic Segments (filter-based audiences) are documented as written filter specifications and do not produce a static contact list; the customer rebuilds these as GoHighLevel filter views or tag-based groups after migration.

Contact and Account migration in dependency order

We run Account migration first so that Companies exist in GoHighLevel before Contact import. Account Name is the dedupe key; duplicate Accounts (multiple Eloqua contacts sharing the same company) are resolved by Company Name match before insert. Contact migration follows with the email address as dedupe key, and each Contact is linked to its GoHighLevel Company by resolving the company name to the newly created Company record. Custom contact fields migrate from CDOs or Eloqua custom fields into GoHighLevel custom fields on Contact. Subscription status and unsubscribe flags migrate to GoHighLevel's built-in email opt-in fields and contact tags. We emit a row-count reconciliation report after each phase.

Engagement history migration

Eloqua engagement activity records (email opens, clicks, form submissions, page visits) are exported from the Bulk API and mapped to GoHighLevel Contact activity timeline entries. GoHighLevel's activity model is simpler than Eloqua's; each engagement type becomes a Contact activity note or tag rather than a full activity record with attribution data. We preserve the engagement type, timestamp, and asset name. Large engagement histories (over 100,000 records) are chunked by date range and loaded in batches to stay within Eloqua's Bulk API rate limits. We do not migrate Eloqua's multi-touch attribution data because GoHighLevel does not have an equivalent attribution model.

Email asset and form documentation handoff

We export Eloqua email HTML content, subject lines, sender addresses, and reply-to configuration as a GoHighLevel Email Template content package. Images stored in Eloqua's asset library are downloaded and re-uploaded to GoHighLevel's asset library with URLs updated in the template HTML. Eloqua form field configurations are documented as a written form specification listing field names, types, and required status for the customer's admin to rebuild in GoHighLevel Forms. We deliver the complete Program and Segment inventory document listing every active Program name, trigger type, step count, and condition logic for GoHighLevel Workflow rebuild.

Cutover and reconciliation

We freeze Eloqua writes during the cutover window, run a final delta migration of any contacts modified during the migration period, then hand the GoHighLevel workspace to the customer's team as the system of record. We deliver a row-count reconciliation report comparing Eloqua source counts to GoHighLevel destination counts for Contacts, Companies, and Custom Fields. We do not rebuild Programs, Segments, or Forms in GoHighLevel; those are delivered as documentation for the customer's admin to implement. We support a five-business-day post-cutover window for reconciliation issues raised by the customer's team.