Hevo Reviews

Seamless ETL

Pros:

Hevo is extremely user friendly and very seamless. Data pipelines can be set in a matter of a few clicks. Our business users are extremely happy with all the data at their disposal for any analysis that they need to do. Hevo's support is very prompt and always available to answer your queries.

Cons:

When we had started using Hevo 2 years ago, there were only a few sources available. However, I see more and more new sources getting added every month.

Hevo Data saved us

Pros:

Hevo Data saved our company in more ways than one. For the bi-directional Hubspot features alone, this tool is worth the cost for us, hands-down. We were able to pull all of our Hubspot data into our data warehouse, annotate, and push back to custom properties and objects. The tool worked so well, we began using it as the core ETL connector for our data lake, and are testing as our scheduled task manager for the core transformations for our data warehouse. The pricing model has worked out well for us. The free trial to prototype how the thing works, and how we could be efficient with our usage of connectors, has also been wonderful.

Cons:

THe list of connectors is really good, but not 100% where we wish. In addition, migrations from one tool to another (e.g. Intercom -> Hubspot) require us to do a bunch of manual mapping that is hard; other tools have these mappings canned and are therefore easier to use for that use-case.

Alternatives Considered: Zapier and Help Desk Migration

Reasons for Choosing Hevo: This tool is much more powerful, cost-effective and aligned with our needs.

Switched From: Zapier

Reasons for Switching to Hevo: We are using Hevo Data in conjunction with Help Desk Migration, which does the mapping we need for us.

good for using hevo data integration

Comments: hevo is good data tools

Pros:

about tools to get asana data using pipeline

Cons:

this software is so powerfull and easy to operating

Good Product

Pros:

I really like the ease with which you can deploy the tool

Cons:

The tool can get better in documentation and video tutorials.

Hevo Rocks!

Comments: If I could give their customer service / support team 10 stars, I would. They've been very responsive and patient while I ask pesky questions.

Pros:

I really like how intuitive it is to build a new pipeline and get data flowing from an API into a destination database - in our case Azure SQL.

Cons:

I don't like that REST API calls that yield the same data are not considered "historical" from a billable event standpoint.

Alternatives Considered: Retool, Make, Phiona, Gathr, Matillion, Stitch, Domo, RudderStack and Fivetran

Reasons for Choosing Hevo: We don't want to create code-based ETLs and data pipelines anymore. The maintenance overhead is way too high.

Switched From: AWS Lambda

Reasons for Switching to Hevo: Intuitive interface, pricing model, ability to connect to custom APIs

The best Data Extraction service for Startups

Comments: Hevo was the ideal tool that I needed to bootstrap our data infrastructure. As the person who set everything up I am very satisfied with them and hope that this will be a long partnership.

Pros:

Hevo is very easy to set up (the whole process is self explanatory) and has a lot of integrations. It also allows for a lot of flexibility with Rest API and Webhook integrations. The UI is very well tought out and the whole product feels professional. I should also point out the Consumer Service, which is great and very helpfull. I get answers every time I talk to them, and I feel my problems are being taken seriously.

Cons:

Hevo doesn't allow precise control of the Ingestion and Loading frequency and times. You can only choose a frequency or specify certain times, but even this one is limited to a certain number of runs. This is our only limitation with Hevo right now.

Super-easy to deploy, great support

Comments: Hevo absolutely made it simple for us to move data from a wide range of disparate applications into a single Snowflake database.

Pros:

I like how easy - almost trivially so - that it is to get started with Hevo. It literally just works. The team have made it really simple to start, and include a free trial. Also the support team are excellent. It has great documentation as well so you can synchronise easily from a wide range of sources and destinations.

Cons:

Some things aren't as polished as you'd like. For instance, you can't categorise pipelines or sort them into folders. You simply have a huge list. Also, there's no easy way - without programming it yourself using the Hevo API - to manage pipelines in bulk. Let's say you have pipelines for similar databases with the same structures; you have to manage them by-hand, individually, or you have to make your own tools.

Alternatives Considered: Talend Data Fabric and AWS Glue

Reasons for Switching to Hevo: Hevo was vastly simpler, low-cost, had great support, and gave us a single place to manage all our data ingestion regardless of source.

Automating Data Pipelines has never been easier

Comments: Absolutely great.
In terms of service itself, reliability, customer support.

Pros:

It has suited all our needs. - The most critical part was reading Oplog from production MongoDB replica. - Cleaning PII and sensitive data on the fly before loading to DWH - Wide range of sources and even Webhooks (any arbitrary source)

Cons:

I might only add Hevo is constantly evolving. I participate in proposing new useful features from my PoV.

Alternatives Considered: Integrator, Fivetran and Stitch Labs

Reasons for Choosing Hevo: Alooma deprecated support of Redshift since it was acquired by Google.

Switched From: Alooma

Reasons for Switching to Hevo: Hevo has beat up all competitors in all the assessed parameters. - Advanced features support (Oplog for MongoDB, WAL for Postgres) - Applying transformations on the fly - Great support team - Nice web interface, API, documentation

Dead simple database replication

Comments: Overall the experience has been quite smooth so far. The support provided was great and the initial setup was simple.

Pros:

Hevo's interface is simple to use, while powerful at the same time. From our tests so far the pipelines work reliably and performantly, and the transformation tools (offered both in a visual manner or through custom Python code for more advanced workflows) are quite useful. The customer experience and support provided is great.

Cons:

I seem to be unable to apply new transformation rules retroactively. That would be an important feature to us as sometimes new fields need to be masked or hidden but were already ingested into the destination.

Alternatives Considered: CData Sync and Stitch Labs

Reasons for Switching to Hevo: The experience seemed to be simpler while keeping the tool powerful for our needs. The simple pricing model was also a decision factor.

Hevo data for Extraction and Loading to Snowflake

Comments: Very Pleasing. I set it up once and I don't have to worry about it again.

Pros:

Simple and effective hassle free table syncing between Cloud VM SQL Server and Snowflake DWH.

Cons:

Getting Hevo white listed with other vendors such as FTP sites is the first big hurdle. Sometimes I'd like to have it sync a view from my source system but it struggles with this. Instead I make it sync the source tables of the view.

Alternatives Considered: Fivetran

Reasons for Switching to Hevo: Simple ease of use. It does what it says it does.

Making Data Simple

Pros:

Ease of use: Hevo's UI is very intuitive and easy to learn. With couple of clicks we can easily build scalable pipelines. Data Transformations: We can write our transformations in python. Hevo also provides out of the box flattening of complex nested json which is very handy while building Mongo pipelines. Quick and efficient Support: Hevo Support team are quite reachable and always ready to help us solving critical bugs and errors.

Cons:

Alerting could be much more precise and intelligent.

Literally just few clicks and data will start flowing.

Comments: Its an awesome product. Really very good one to get started with very little friction.

Pros:

The things which I most like about Hevo is the automation level in the product. Hevo will take care of everything from source mapping to destination mapping with just a few clicks. It has many useful features, be it table/column auto-mapping , resizing and basic transformations for complex data sources like Mongo where you want to flatten the nested data.

Cons:

Alarm feature can be little more intuitive.

Great Product

Comments: Very happy with the product so far, dramatically reduced the data ingestion times.

Pros:

Ease of setup Cost Quick ingestion times Ability to connect to multiple sources Transformations

Cons:

High CPU usage on our Amazon Aurora PostgreSQL server.

Alternatives Considered: Fivetran

Reasons for Choosing Hevo: To reduce data load times into Snowflake

Switched From: Stitch

Reasons for Switching to Hevo: Better data ingestion times and lower costs.

Hevo helped us solve our ETL needs.

Pros:

Hevo offers a fair pricing model with competitive features, along with a seamless data integration experience that complies with many data privacy groups. The ability to transform data using python code, auto map object data, and do this all in a user-friendly interface is wonderful. Hevo also ensures pure privacy with data which is vital when using cloud storage integrations.

Cons:

There was not much to dislike about the software.

Alternatives Considered: Fivetran and Stitch Labs

Reasons for Switching to Hevo: When looking for a data pipeline tool, we wanted to be able to incorporate all of the tools we currently utilized while staying compliant with GDPR. We did not want to have multiple pipelines for different resources, instead we knew we needed a single ‘one stop shop’ for our data pipeline. We looked at a few of Hevo’s main competitors within the industry before finalizing our choice with them.

Accuracy and security at competitive pricing

Pros:

HIPAA compliance, data integrity, documentation, and support

Cons:

features I miss from Stitch like column level ingestion. Ingestion and loading logs are also quite thread-bare and hard to get much information on this.

Alternatives Considered: Fivetran

Reasons for Choosing Hevo: data integrity issues

Reasons for Switching to Hevo: Price

An Amazing ETL tool

Comments: We are using hevo to get Data seamlessly from our transactional DB to our datawarehouse. Hevo is reliable and plays an important part in our data pipelines.

Pros:

The best thing I like about Hevo is the ease of use and the integrations that are avaialble for multiple sources, which makes the ETL seamless.

Cons:

In Schema Mapper/Overview tab in each pipeline, an option to skip muliple collections at a time using a check box might be a good feature which will be very helpful for us, otherwise its now taking lot of manaul effort to skip them if needed in a pipeline.

Hevo is a critical in connecting data sources across the org with each other and our warehouse!

Pros:

We have multiple pipelines and connections with almost every piece of software across our organization. Hevo makes it possible for us to keep everything up to date and helps to centralize our reporting by brining current data into our warehouse for day to day analysis and reporting.

Cons:

We have very few problems with Hevo. If we have any trouble it's almost always related to our usage limits.

Great Product

Pros:

Previously, we were using Fivetran. With Hevo, we get better features for a fraction of the price.

Cons:

Honestly, I don't have any complaints. Their support is awesome and any issues that I have had, have been resolved within hours.

Hevo is an impressive feature-packed product with great UX

Pros:

1) Self serve product with super UX - we were able to start our pipelines by ourselves within a day 2) Detailed documentation for every source / destination with appropriate up-to-date references 3) Was impressed by the overall speed - after submitting a job to queue, it picks up the job almost immediately 4) Transformation supports Python which is great, data can be manipulated by custom scripts 5) Full visibility and control over the entire pipeline 6) Schema mapper is great, auto-mapping works for most of the use cases. Manual mapping is also possible. It shows and asks user to confirm what query it is going to execute at the destination, which is good 7) Workbench available to run queries at the destination, custom data models available to create "views" from destination tables

Cons:

1) Didn't quite like the limit on number of sources in plans 2) Schema mapper doesn't have an option to change column types at the destination

Reliable, easy-to-use and good price/performance ratio

Comments: Hevo won our lengthy product comparison against other leading tools like Stitch Data, Fivetran, Matillion, etc. They provide best-of-breed usability, scale, reliability and latency. Their monitoring, schema mapping, error handling and replay capabilities are excellent. We are supporting near real-time reporting in a Snowflake warehouse thanks to Hevo's streaming replication from RDS MySQL.

Pros:

Hevo's interface is well designed, so that it is straight-forward to set up many pipelines. Unlike other tools, they do not force us into their own standards, for example for naming tables. The service is reliable and performant, including at scale. The team also consists of nice people who have been very friendly and helpful.

Cons:

We have no complaints. Hevo's MySQL binlog replication works well for us.

Makes ETL really easy

Comments: Overall, I've seen the product evolve from a beta version to a very mature one in less than a year. Our Analytics team is very happy and can sleep soundly given Hevo is doing the heavy lifting round the clock.

Pros:

We have 10+ pipelines streaming a few million rows from multiple databases to a warehouse. It's very easy to use and configure. It supports all popular database types as sources and we can put custom transformation logic in the pipelines. Hevo's support engineering team has also been very pro-active and helpful throughout our engagement to date.

Cons:

I think the documentation could be structured in a format of Source (e.g. MongoDB) to Destination (e.g. BigQuery) with the exact steps required to configure this pipeline. Most users would come to Hevo with this type of requirements and it would aid with discoverability.

My ETL tool choice

Comments: I was able to put all my database sources together to create our own database, with just the data we needed.

Pros:

The customer service is great, they were always ready to help, very kind. Great sources opinions, to integrate with and to use as destination.

Cons:

It can be complicated to make a pipeline with some specific source and it doesn’t seem to have an easy solution to fix the issue.

Alternatives Considered: Switchit

Reasons for Switching to Hevo: Price at first. Then the customer service locked me in.

Hevo - Budget Friendly Option

Comments: Able to get the data I want, in the format I want, to do the business analysis required

Pros:

Extremely Budget friendly, many connector s and destinations, easy to use and good support

Cons:

Sometimes, the transformations from the raw connectors can be a bit confusing and it requires heavy understanding of the source. But that's expected.

Alternatives Considered: Fivetran

Reasons for Switching to Hevo: Honestly, the more budget friendly option

A really good player in this field

Comments: Overall good, from meeting to implementation. The Admin interface is very well built.

Pros:

We decided to shop around for a new solution because our current provider decided to raise their prices significantly. Hevodata checked all the boxes.

Cons:

When we first started out, our BigQuery costs went up, but we were able to mitigate that by changing the frequency.

Simple to set up and great customer support

Pros:

As an ETL, you couldn't ask an easier tool to set up and test than Hevo. This is great for quickly checking if it'll work for your goals. All processes are transparent and if something seems amiss you can get a handle of a very helpful customer support quickly.

Cons:

There are some advance features for data handling that seem to be still in development. Overall, it might not be the tool for you if you have a very strict or complicated workflow.