By Karin Pindle
Eloqua clients! By now, you’ve likely heard about Eloqua’s new SFDC Integration App. Have you also heard that the native Eloqua-Salesforce.com CRM (SFDC) integration will no longer be supported by Oracle as of February 1, 2021? Read more about it here.
To help, we’ve put together our own recap plus our top tips to help you successfully migrate to the new SFDC Integration App before February 1, 2021.
First, our recap…
- You can continue to use the native integration after February 1, 2021 as Oracle is not going to “end of life” it – yet. Their plan is to “no longer support” it, which means you won’t be able to submit requests to Oracle Support for help with any issues or questions. It also usually means they won’t be putting any product development into maintaining and improving it.
- The SFDC Integration App was made generally available February 2019. It’s built on Oracle’s AppCloud framework and is available at no additional cost as it’s included in your Eloqua subscription.
- You can use both the native integration and Integration App simultaneously, which is very helpful during setup and testing of new Integration App.
- Pros of the SFDC Integration App based on our experience with it to date:
- It’s faster than the native integration in pushing data from Eloqua to SFDC by using Program Canvas instead of Program Builder
- It’s easier to setup and to maintain
- You can more easily filter testing to not use live data
- It has an improved reporting and management of errors so you can troubleshoot more proactively
- It supports multiple SFDC environments integrated with a single Eloqua environment (just like the native integration does)
- Cons of the SFDC Integration App based on our experience with it to date:
- If the AppCloud or the SFDC Integration App goes down, your entire integration goes down
- If you want to filter records coming into Eloqua from SFDC, you have to write a SQL query
- There are limited options for passing campaign responses to SFDC
Check out this full listing of Integration App FAQs from Oracle.
Our top tips for migrating to the SFDC Integration App:
Have a plan. Please. Yes, we said it – have a plan. Document your current integration setup with the native tool. A simple spreadsheet is a good way to do so with a tab per SFDC object. Decide what you no longer need, what just needs to be revised and/or optimized, and what new components are needed. Define a date to cut-over to the SFDC Integration App.
Next, it’s time for setup. Add the Integration App to your Eloqua instance. Keep your native integration running and setup the Integration App, ideally by connecting Eloqua with a SFDC Test environment. If you have an Eloqua Sandbox (Test) environment, we recommend integrating that with a SFDC Test environment first. Then, Eloqua Production with a SFDC Test environment. Be sure to setup error notifications to help quickly fix any issues
Time to test. Test the Integration App carefully to avoid changes to live data in Eloqua (since the native integration will continue to run until the official cut-over to the Integration App).
You’re ready to go-live and monitor. Disable the native integration and associated Program Builders then enable the Integration App components and associated Program Canvas’s. Monitor the Integration App daily for two weeks to ensure all data is flowing as expected.
As with any change, training is critical to success, so schedule the time to view this half-hour video course provided by Oracle to help you learn more about the app and how to configure it. Note, it’s comprehensive, but does require that you to understand both the Eloqua and SFDC data models and have some understanding of how they integrate. Another go-to resource we highly recommend is Eloqua Help Center documentation.
We know that some of you long-time Eloqua clients have complex native integrations which rely heavily on Program Builder. This is why it’s important to begin your planning as soon as possible! We have clients with advanced Program Builder programs that cannot migrate to Program canvas yet due to lack of functionality, so we’ve helped them come up with creative solutions to make the Program Builder programs work with the SFDC Integration App.
As a secondary priority, we also recommend that you review all of your Eloqua Program Builder programs to start planning for a full migration to Program Canvas, aka “future-proofing.” Why? It’s very likely that at some point in the future, Eloqua will no longer support Program Builder (to be clear, there has been no official announcements).
Are you wondering how to get started? We can help! We’re in the middle of helping several of our clients migrate to the new SFDC Integration App now, as well as migrate all Program Builder programs to Program Canvas.
Contact us to discuss how we can help support you in proactively tackling these important marketing automation projects.