Migrating from Eloqua to Salesforce Marketing Cloud: Perspective from an Expert Marketing Cloud Architect

This article was updated on January 7, 2026 with an up-to-date FAQ section.

Today the SalesWings B2B Studio team is speaking with an expert Marketing Cloud Architect, Mateusz Dąbrowski. Mateusz is a Marketing Cloud Architect at PwC. In this interview, Mateusz will give his takes on the differences between Eloqua and SFMC, choosing between the two, and migrating from Eloqua to Salesforce Marketing Cloud…

Mateusz Dąbrowski: As always, it depends ;) Salesforce Marketing Cloud and Oracle Eloqua, while both being Marketing Automation Platforms, are very different. I’m not talking about B2C vs B2B positioning – you can use either tool for both scenarios – but rather the vision behind each solution.

Eloqua is an easy-to-use email marketing automation platform that digital marketers can successfully operate independently. The superb customer journey orchestration tool is backed by a broad set of drag-and-drop tools that one can use to create all required assets. You can create complex segments, dynamic forms, personalised landing pages and emails without a single line of code. Unfortunately, if you need something not covered by the platform, there is not much you can do in this walled garden.

On the other hand, Salesforce Marketing Cloud is a multi-channel powerhouse that can do everything. However, it sacrifices some of that Eloqua straightforwardness. While you will also see “no-code” on the Salesforce banners, those marketing automation drag-and-drop parts are lacking compared to the other platform. It is evident with segmentation and forms. At the same time, there is a wide selection of code-based solutions that not only cover all of the features but then go way further, opening many new use cases. And hey, with SFMC, you can have the best of both worlds by shopping the easy and powerful options at AppExchange. I wrote an article on when this path might be worth it.

Coming back to the original question, I believe it’s less about being ahead of the game and more about the focus of each platform.

Are you looking for a stable and easy-to-use but closed and non-extendable platform? Eloqua is perfect.

Do you want to be able to customise the platform to meet your exact needs and cover every single use case, even if it might lead to some development work? Marketing Cloud is the way to go.

Looking to build a mobile application for multiple platform such as iOS & Android using a single codebase? It may be best to hire react native developers who can help you find the right solution for your requirements.

Mateusz Dąbrowski: The most significant limitation of Eloqua is its non-extendable character. When the out-of-the-box approach is not enough, there is not much you can do. Sure, there are paid apps extending Campaign features (even adding new channels), but the walled-garden approach of the platform limits them.

Marketing Cloud covers much more features out of the box, for example:

1. Incredibly flexible data model, real multi-channel (Email, SMS, Push, WhatsApp, Line, Social Advertising, Google Analytics Audiences)
2. Full and free integration with Salesforce CRM
3. Extensive AI support across all tools
4. Built-in recommendation engine and abandoned cart solutions for e-commerce
5. Full-blown backend programming languages that you can use in communication and landing pages (ReCaptcha for forms! Custom dynamic logic for email content! Pulling send-time data via API!)

And that’s just the ready-to-use features. With SFMC, the sky is the limit. You can extend it using purchases in AppExchange, and building your custom solution (hosted externally or even directly on the platform.)

Each time you hit the wall in Eloqua and have to think about a workaround to your requirement – it would be possible on Marketing Cloud.

Mateusz Dąbrowski: I would start with universal considerations:

Analyse your Marketing Automation Platform requirements with MoSCoW method. Just because something is available in either of the assessed tools doesn’t mean you need it. Be clear on your priorities and make them the cornerstone of your comparison.

Involve your Marketing Operations team from the start. They are in the first line and understand the actual needs. When choosing the right platform, you must also account for your team’s skillset.

Check the community around the platform. It is often overlooked but is crucial – a strong community means that there is a talent pool to grow your team and crowdsourced support that will help your current users onboard to the new solution.

Cross-check the critical requirements with the power users. Just because some feature is listed in the documentation and checked on the RFP doesn’t mean it is usable. There might also be constraints making it unusable for your specific needs.

Get a clear picture of the available budget. The license cost is only part of the story. You should also consider implementation, hyper care support, training, certification, add-ons and 3rd party apps as they can make or break the outcome and solution buy-in.

How do some of those points apply to the Eloqua-to-SFMC migration use case?

If your “Must Have” is a heavily integrated environment and strict implementation of company-specific workflows – Marketing Cloud is the way to go.

On the other hand, if your non-negotiable is a powerful Lead Scoring solution – SFMC doesn’t have any out-of-the-box. Invest in an integrated app that will add this feature to the Marketing Cloud and help spread your “sales wings” 😉 or look for another product (like Salesforce Pardot).

If your Marketing Automation users don’t have coding skills (basic JS, SQL), they won’t be able to leverage the full potential of Marketing Cloud. But if they have those – or are willing to learn – they will be able to bring your marketing to the next level.

The Trailblazer Community around Marketing Cloud (and Salesforce ecosystem in general) is one of the most vital selling points of the platform. It’s a massive, helpful, and innovation-driven group that will support your team and make the transition much smoother.

“The Trailblazer Community is a massive, helpful, and innovation-driven group that will support your team and make the transition much smoother.” @MDabrowskiPL #marketingcloud Mateusz Dąbrowski, PwC Switzerland Click to tweet

Mateusz Dąbrowski: There are four critical high-level phases:

Discovery – It starts internally with preparing the analysing needs (MoSCoW) and shortlisting potential solutions and implementation partners. Then it becomes a joint task to analyse the current and future state requirements and find the best partner for the transition. Here you are looking for a tool that covers all your Must Haves and most Should Haves in a way that aligns with your team’s skill set. It’s also a moment to select the implementation partner that not only has raw implementation capabilities but also understands your needs and will facilitate the knowledge transfer needed to smoothly onboard you to the new platform.

Planning – Once you choose a platform and partner, it’s time to prepare the implementation plan. Key deliverables here are user stories describing what the development team needs to do and how you will be validating that the outcome is correct. While you should have most of the scope covered here, it’s always best to have a buffer planned. With big migrations, there are always surprises, roadblocks or changes, and it benefits everyone to have some space to cover them without sacrificing anything. If possible, it’s also best to start with MVP and then extend further, as this will allow validating assumptions and training the team on the new platform early.

Build – With the plan describing what needs to be done, it’s time to roll the sleeves and get to work. Apart from the base work, you should expect in-depth documentation (not just copy-paste of configuration, but a detailed guide that will facilitate hand-off to your Marketing Operations team) and backup of the code-based solutions.

Transition – Finally, the MVP is ready, and your team can start using the new and shiny platform. Don’t jump head in – firstly, perform UAT. Check whether everything the implementation partner promised is ready in the system. Your team knows what they need, and while validating, they will learn the very basics of the platform. Next, it’s time for hyper care. Let your team do the work, but with a hotline to the platform experts that can facilitate smooth onboarding and learning process. You should be getting recommended learning paths for your team here – which is super easy in the Salesforce ecosystem thanks to their free learning platform Trailhead.

Mateusz Dąbrowski: I see a few types of challenges frequently:

The first place goes to data migration issues, especially related to historical engagement data and consent. Not only is it a complex topic with many limitations, but in many cases, old and new platforms run parallel for the transitory period.

A company is looking for an exact copy of existing functionality “because it works”. In many cases, while developers can create a matching custom, it adds unnecessary complexity and could be solved much better with more flexibility on the requirements side. A painful example: loops possible in Eloqua’s Campaign are not available in Marketing Cloud Journey Builder (unless you go really dirty).

A company does not want any additional licenses apart from the platform one. In some cases – especially drag-and-drop segmentation and leads scoring when talking about Eloqua-to-SFMC migration – a small paid add-on can solve many problems and limit (in the end, much costlier) custom work.

Finally, the challenge is always the new platform, with its quirks and features. And this is where the second part of the question comes into play. I already covered it partially in answer to the previous question – it is crucial to bring the Marketing Operations team to the discussion from the very start so that:

During discovery, they already have an initial picture of incoming changes.

During planning, they align with the implementation team on the acceptance criteria of the user stories.

During the build, they have already read through the documentation and can start preparing for the transition.

During the transition, they pull all needed knowledge about the quirks and features from the hyper care team.

That, and becoming part of the Trailblazer Community ;)

Mateusz Dąbrowski: Of course, it depends. There are many factors: number of stakeholders, level of bureaucracy, the complexity of the Eloqua implementation, flexibility and MVP approach to the migration. I would start with 3 months for a simple migration, 6-9 months for average, and up for the very complex and unique.

Mateusz Dąbrowski: Don’t let the marketing impact your choice of marketing automation tool. I don’t believe in the B2B vs B2C separation of platforms – it all depends on the exact features you need, so use the discovery phase of the migration to find the best match for your company. Only then will you know whether Salesforce Marketing Cloud is the right choice or if you look at, for example, Pardot (officially a B2B-focused tool like Eloqua).

From my experience, SFMC adds complexity but, in return, provides much more flexibility and power. Does it sound like a worthwhile tradeoff for your company? Go for it!

“Don’t let the marketing impact your choice of marketing automation tool. I don’t believe in the B2B vs B2C separation of platforms – it all depends on the exact features you need.” @MDabrowskiPL #marketingcloud Mateusz Dąbrowski, PwC Switzerland Click to tweet

Mateusz Dąbrowski: Can’t I? ;) I’m a huge tea drinker (Looking for something interesting? Try Storm Breaker Shou Puerh from Crimson Lotus Tea), boardgame player (Terraforming Mars is my favourite at the moment), and knowledge addict (both learning and sharing).

About Mateusz Dąbrowski

Mateusz is a Marketing Cloud Architect, Salesforce MVP & Marketing Champion, and author of SFMC-focused website, mateuszdabrowski.pl.