Eloqua Blog · Salesforce Integration

Eloqua Service: Migrating From The Native Salesforce Integration To The SFDC App

Oracle's supported path moved from the native Salesforce Integration Studio to the Salesforce Integration app. Here is how to understand the old setup, the new app, and the decision points before you migrate.

Feb 28, 2020 10 minute read Integration Studio SFDC App Migration

Support Is Ending

Before we start, this post does have a sales pitch attached to it. My colleagues and I at Pl8ypus put together an off-the-shelf Eloqua Salesforce integration migration product for teams that want a managed route through the change.

As of 21 February 2021, Oracle planned to stop supporting the native Eloqua Salesforce integration commonly known as Integration Studio. You may have received an email about it on 28 February 2020.

If this feels like a surprise:

Stop.
Do not stress.
Make yourself a tea or coffee.
Read the rest of the article so you can make an informed decision.

Eloqua Salesforce Integration

A typical Eloqua Salesforce integration allows data to flow between the two platforms. The shape of that flow matters because it determines what you need to rebuild, test and sign off in the app-based approach.

From Salesforce To Eloqua

These objects are typically synchronised into Eloqua.

Salesforce Contacts
Salesforce Leads
Salesforce Accounts
Salesforce Opportunities
Custom objects, such as Campaigns and Campaign Members

From Eloqua To Salesforce

Eloqua contact data can enrich or create Salesforce Leads, and update Salesforce Contacts, depending on your sales methodology and setup.

Eloqua marketing activities
Eloqua campaigns
Eloqua campaign members stored on CDOs
Other Eloqua custom objects

How Integration Studio Works

For more than 15 years, Eloqua customers relied on Integration Studio. It connected Eloqua and Salesforce through inbound and outbound integration points.

The old integration was built from internal events and external calls. Internal events gave Eloqua a function to perform, such as creating a Salesforce Lead. External calls handled the field mappings between Eloqua and Salesforce.

Inbound

Salesforce to Eloqua.

Outbound

Eloqua to Salesforce.

Send Data

External calls that push Eloqua values into Salesforce.

Retrieve Data

External calls that pull Salesforce values back into Eloqua.

Where The Old Pieces Live

Autosynchs

Salesforce-to-Eloqua integration points are mapped in the Autosynchs area of Integration Studio.

External Calls

Eloqua-to-Salesforce mappings are configured through external calls.

Program Builder

Outbound Eloqua data is sent through outbound external calls using Program Builder.

The Salesforce Integration App

Oracle wanted customers to move their Eloqua Salesforce integration from Integration Studio into the Eloqua Salesforce Integration app. After the initial setup that lets Eloqua talk to Salesforce, inbound and outbound points are rebuilt in the newer app interface.

The outbound program also moves away from Program Builder and into Eloqua Program Canvas, which changes how teams build, monitor and govern the process.

Your Three Choices

Option 1

Do Nothing

Integration Studio may continue to run, but support and future-proofing become the concern.

Option 2

Migrate Yourself

A good option if your team has the time, documentation, test scripts and direct migration experience.

Option 3

Use A Third Party

Useful when risk, resource, security process or timeline pressure makes a rehearsed migration safer.

Decision Matrix

The matrix is there to make the decision practical. The important factors are technical expertise, deployment time, internal resource and cost.

Technical Expertise

Has the team built an Integration Studio data flow from scratch, used the new app, and completed this exact migration before? If not, consider third-party help.

Deployment Time

Look for a rehearsed process, fixed stages, test scripts, existing documentation, security paperwork and change-board materials.

Internal Resource

Ask whether you can stand up the right people for one to two weeks, train them, protect their time and absorb delays.

Cost

Include opportunity cost. Your team may be able to do the work, but the cost is what they stop doing while they migrate and test.

Migration Package Steps

For teams choosing a third party, the Pl8ypus migration package can run remotely, on-site or as a hybrid. The aim is to supply the right people, upskill the Eloqua team and keep every stage visible.

Plan

Confirmation email, requirements meeting, quote, project plan and quote sign-off.

Document

Verify or document the existing integration, then develop and set up test scripts.

Approve

Get the Salesforce Integration app through security, load stages into the project tool and prepare the change-board submission.

Migrate And Test

Migrate the integration, complete testing, resolve defects, retest and repeat the process for each environment before final handover.

If you also want to update or add integration functionality, the cleanest time to discuss it is at the beginning of the project.

Integrating 1 Instance Of SFDC To 2 Instances Of Eloqua

A companion article on a more complex Salesforce and Eloqua integration scenario.

Read article

Eloqua SFDC Dashboards

Useful context for measuring Salesforce and Eloqua operational performance after integration work.