{"id":1467,"date":"2020-05-26T15:19:00","date_gmt":"2020-05-26T19:19:00","guid":{"rendered":"https:\/\/blog2wrkdev.wpenginepowered.com\/why-hubspot-migrated-to-workato\/"},"modified":"2026-09-30T07:45:48","modified_gmt":"2026-09-30T11:45:48","slug":"why-hubspot-migrated-to-workato","status":"publish","type":"post","link":"https:\/\/blog2workato.wpengine.com\/why-hubspot-migrated-to-workato\/","title":{"rendered":"Why HubSpot Migrated to Workato"},"content":{"rendered":"\n

We chatted with Derek Roberts, who spent 7 years as the Director of Services Strategy and Operations at HubSpot<\/a> and is now leading our Customer Success Management at Workato<\/a>, about moving from his low-code iPaaS platform, Azuqua, to Workato\u2019s Enterprise Automation Platform. We also hear about his evaluation process, and how he enabled approximately 75 people and had 45 certified recipe builders able to use Workato before he handed the reins to Jeff DaSilva, Senior Automation Analyst at HubSpot.<\/p>\n\n\n\n

Why move low-code integration platforms?<\/strong><\/h4>\n\n\n\n

In our case, Azuqua was acquired by Okta<\/a> and is officially sunset May 1st, 2020. It was unfortunate but I was interested in expanding the platform to support many integration builders so it was a blessing in disguise.
<\/p>\n\n\n\n

What was the search process for a new platform like?<\/strong><\/h4>\n\n\n\n

We did a vendor evaluation keeping growth and scalability top of mind. To start, we looked at 10 vendors, then narrowed it down to 4 to actually engage with. Two were more traditional Enterprise iPaaS providers, but they were too clunky and not easy to deploy the way we wanted to. We wanted to take a revolutionary approach where the actual teams who needed those automations could make them, themselves but with oversight from the right people.

We shouldn\u2019t have even considered other vendors, because they lacked the basic functionality we needed around security, access management, version control, etc. Workato was the perfect balance of Enterprise grade capabilities and security paired with an easy to use no-code interface. We were really careful in our selection because we did not want to go through another migration just after we completed the project so viability was also a major focus.
<\/p>\n\n\n\n

Having used a different iPaaS prior (Azuqua), what were your top priorities when choosing a new platform?<\/strong><\/h4>\n\n\n\n

We had already gained deep experience from our use of Azuqua, so one of the most important things for us the second time around was to deploy it in such a way that we got much more leverage and easily increased our ROI story. We leaned really heavily into the deployment model, making sure the vendor we selected could scale with us and have the right controls to allow an organization wide deployment.
<\/p>\n\n\n\n

Why did you choose Workato?<\/strong><\/h4>\n\n\n\n

We needed an Enterprise Grade Platform that could also deploy org wide with controls in place. Workato had:<\/p>\n\n\n\n