SH2
Moving to Eloqua - what do I need to know?
We've been a Pardot customer for over three years now and can't fault the product (although support is shocking since the move to SalesForce) however the powers that be have decided we're moving to Eloqua.
We've had a series of demos and have had several rounds of Q&A with Oracle and our migration partner, but I figured I'd ask my professional peers whom I trust (that's you lot) if there's any gotchas or anything else that I need to know that Oracle and the consultants won't tell us.
Please spill the beans on any horror stories you've experienced directly (or indirectly) or let me know if you have been pleasantly surprised.
Thanks!
We've been using Eloqua for several years. I haven't heard anyone on our team say they are satisfied with it. Because we want our emails to be consistent and branded (duh) I design them in Dreamweaver (other tools are availabler, but I happen to know DW) then import the HTML file into Eloqua. The drag-n-drop feature of Eloqua is not adequate for our needs. Also, before importinging the code, I use Litmus to test it in all the major clients. For this, I am eternally thankful to Litmus! The challenge is always Outlook. For this I am eternally annoyed. Here's a tip: before designing an email outside of Eloqua, I import the images into Eloqua, then copy the imported image's URL and use that in Dreamweaver.
Here's the community page with feature requests that don't currently exist. Otherwise I'm not familiar with pardot, so I can't compare anything.
Thanks Devon, I'll definitely take a look at that with the team.