Oracle Eloqua to HubSpot
Enterprise B2B marketing automation (Oracle Eloqua Marketing Cloud Service) covering contacts, segments, campaign canvas, email, forms and landing pages.
Oracle Eloqua data can move into HubSpot, landing mainly in Marketing Hub. 2 of 8 mapped objects move directly (Contacts and Accounts); 5 items need manual work and 4 do not move. Plan roughly 4-8 weeks for a small move and 14-24 weeks for a large one.
Migration checklist for Oracle Eloqua
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<100k contacts, few campaigns
Mostly contacts, lists and templates.
Mid migration
100k-1M contacts, dozens of canvases
Includes CRM integration and scoring rebuild.
Large migration
>1M contacts, many CDOs and activities
A partner source cites 10-16 weeks typical.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Oracle Eloqua: what you need to get in, what lands in HubSpot, and what will not.
REST API 2.0 plus asynchronous Bulk API 2.0
Eloqua company name, username and password for Basic auth, or an OAuth app for OAuth 2.0; the pod URL is also needed.
The user's security group must allow access to contact fields and secondary assets.
Bulk API soft limits per instance: 2000 exports/hr, 2000 imports/hr, 4000 sync actions/hr. An export definition is capped at 250 fields, and a retrieve request returns up to 50,000 records. Activity exports are capped at 5M records per sync. REST API limits are not confirmed in primary docs.
Choose your route
How will you move the data?
No native connector was found.
- You need: Eloqua company name, username and password for Basic auth, or an OAuth app for OAuth 2.0; the pod URL is also needed.
- Permission: The user's security group must allow access to contact fields and secondary assets.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Bulk API export definitions: Activities, Accounts, Contacts, Custom objects, Events, Campaign responses
- UI Data Export under Audience > Tools > Data Export and Import (CSV)
- REST API 2.0 for assets and smaller deltas
Limits: Bulk API soft limits per instance: 2000 exports/hr, 2000 imports/hr, 4000 sync actions/hr. An export definition is capped at 250 fields, and a retrieve request returns up to 50,000 records. Activity exports are capped at 5M records per sync. REST API limits are not confirmed in primary docs.
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 14-24 weeks, usually phased.
Talk to a partnerWhere each object lands
In Oracle Eloqua
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contacts | Contacts | yes | Export via Bulk API or UI Data Export, up to 250 fields per definition. Eloqua contact ID and email should be stored as properties. |
| Accounts | Companies | yes | The Bulk API exposes accounts; the contact-to-company link must be rebuilt via an import association key. |
| Custom data objects (CDOs) | Custom objects | partial | Exportable via Bulk API. Mapping 1:N and N:N relationships needs design work. Some tools claim to automate it. |
| Opportunities | Deals | partial | The Bulk API lists opportunities, but many instances hold them in the CRM instead. This should be checked per instance. |
| Contact segments and shared lists | Contacts | partial | Export membership as static lists, and rebuild filter logic as HubSpot active lists. |
| Campaign responses and activities | Notes | partial | Exportable, but not natively portable as timeline engagement. Typically archived or loaded as properties or custom events. |
| Campaign Canvas programs | Custom objects | manual | Must be rebuilt as HubSpot workflows. Logic does not transfer. |
| Email templates, forms, landing pages | Files | manual | Save HTML and assets, then rebuild in HubSpot editors and upload files. |
What to expect
The Canvas architecture does not map directly to HubSpot workflow logic.
They need to be rebuilt rather than copied exactly.
The Bulk API exports activity data but there is no native import. Vendor claims of timeline population are unverified.
They need mapping to HubSpot personalization tokens and smart content.
There is no automated Canvas conversion.
Only HTML and assets can be exported.
Filter logic must be recreated and compliance status imported.
Instances often have deep CRM integrations that must be replaced.
Eloqua Insight reports and scoring need new HubSpot equivalents.
Export global unsubscribe and bounceback fields and import them as non-marketing or unsubscribed status before any send.
Chunk exports with filters and stay under 250 fields per definition and the hourly sync limits.
Archive activity exports externally and map only key fields to properties.
Run a full instance audit of canvases, segments and scoring first.
Set up a dedicated domain and warm it up.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
Eloqua Bulk API access, auth, limits and exportable objects are backed by Oracle docs (S1,S3,S4). The HubSpot-side mapping, asset rebuild and timelines rest on partner guides and category knowledge, and no HubSpot docs were reviewed.
Sources
Related migrations
Frequently asked questions
How do I migrate Oracle Eloqua to HubSpot?
1. Audit Canvas campaigns, segments, shared filters, forms, CDOs and scoring models. 2. Create an Eloqua API user, ideally with OAuth 2.0, and confirm the security group covers contact fields and CDOs. 3. Map Eloqua fields to HubSpot properties, keeping the Eloqua contact ID and email address as the dedupe key. 4. Identify global unsubscribe, bounceback and suppression fields and the lists that hold them.
What data can move from Oracle Eloqua to HubSpot?
These objects move directly: Contacts and Accounts. Check the mapping table for partial and manual items.
What does not move from Oracle Eloqua to HubSpot?
Campaign Canvas logic as executable workflows, Lead scoring and grading models, Native engagement history and attribution as HubSpot timeline events and Dynamic content rules. Plan to rebuild or retire these.
How long does a Oracle Eloqua to HubSpot migration take?
Small (<100k contacts, few campaigns): 4-8 weeks. Mid (100k-1M contacts, dozens of canvases): 8-14 weeks. Large (>1M contacts, many CDOs and activities): 14-24 weeks. These are planning estimates, not a quote.
What access do I need to export from Oracle Eloqua?
Eloqua company name, username and password for Basic auth, or an OAuth app for OAuth 2.0; the pod URL is also needed. The user's security group must allow access to contact fields and secondary assets.
What compliance issues apply when moving Oracle Eloqua data?
Check: May hold GDPR/CCPA-covered personal data and Check for health, financial or minors' data in custom fields or CDOs. Agree consent, retention and access rules before exporting.
Moving Oracle Eloqua into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner