Fivetran Data Movement Platform
FivetranExternal reviews
457 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Good for large datasets - limited in terms of controls
What do you like best about the product?
It does effectively pull large data sets.
Integrations with various platforms
Integrations with various platforms
What do you dislike about the product?
Inability to schedule pulls, has to be every 24h. (Not necessarily for weekly / monthly reports so it seems excessive).
For CM360 it is difficult to pull 'Seat' or 'Network' as a dimension.
For CM360 it is difficult to pull 'Seat' or 'Network' as a dimension.
What problems is the product solving and how is that benefiting you?
It supports me in reporting in bulk - ultimately extracting large datasets and improving efficiency by saving time
Good Product -- Slow to pivot
What do you like best about the product?
We have a wide variety of source systems we need to extract data from. For 90+% of these FiveTran does the trick. Setup is easy and there isn't much to manage once set up.
What do you dislike about the product?
There is a known issue with Business Central connectors. We have been working with them for months trying to get it fixed or even get a timeline and we continue to be flying blind. This is pretty critical to our business and I'm sure with others using Microsoft Business Central so I wish they would be more communicative about this.
What problems is the product solving and how is that benefiting you?
We use this to pull in data from many sources and load them into one consolidated warehouse.
Fivetran Review
What do you like best about the product?
Easy integration and intuitive controls make it quite helpful
What do you dislike about the product?
Set up and implementation through consultancy was cumbersome.
What problems is the product solving and how is that benefiting you?
Data storage and merging.
useful low effort tool for db beginners
What do you like best about the product?
prebuilt connectors
simple schema management
simple schema management
What do you dislike about the product?
unclear why syncs are delayed
limited webhook capabilities
limited webhook capabilities
What problems is the product solving and how is that benefiting you?
build our data warehouse with limited api knowledge
My experience on using Fivetran connector is not that great.
What do you like best about the product?
Easy to connect to most of the data sources, and it is user friendly integration.
What do you dislike about the product?
We are facing fivetran failure in our project due to which data sync is improper.
What problems is the product solving and how is that benefiting you?
Fivetran is not capable in connecting to Lever data source and do a data extract. We are facing sync issue from last 2 months.
Easy to use - plug and play ETL tool
What do you like best about the product?
Ease of use - it gives us the benefits of a custom data pipe line in configuring the fields we need without having to have an internal data engineering team
What do you dislike about the product?
There are some additional requirements we need to have met on some sources, which prevent us to switch to Fivetran completely
What problems is the product solving and how is that benefiting you?
It allows us to access the data we need for more advanced analytics without needing to build a data engineering team
Production Grade Connector Service
What do you like best about the product?
The reliability of data quality in it's connectors
What do you dislike about the product?
Cost structure. Not great for connectors that are lower MAR. Lack of customization in cost structure
What problems is the product solving and how is that benefiting you?
Not having to build and maintain connectors
Gets the job done with our legacy environment
What do you like best about the product?
I like that it supports moving data from a legacy environment. It easily connects to our mainframe database and moves incremental data. When we needed support, we are able to get on a call and solve the issue. I like the number of available connectors, should we decide to utilize more data sources. The recent change in licensing has allowed us to increase our data and reduce our spend. Overall I like this tool.
What do you dislike about the product?
Our challenge is that we have a cloud hosted mainframe database, we had an issue using the proxy version of the sync tool, and had to switch to a reverse SSH tunnel that requires a bit more work to set up an maintain. After a few months of figuring it out, we are now stable.
What problems is the product solving and how is that benefiting you?
We needed an easy tool to move our data from mainframe to Snowflake. I like that it does incremental change for the database, which makes the sync time less.
Convenient but expensive
What do you like best about the product?
Makes it really easy to sync external data into any major warehouse
What do you dislike about the product?
Cost is expensive and doesn't allow for scaling easily
What problems is the product solving and how is that benefiting you?
Connecting data from various external sources into our warehouse
Reliable platform, little pricing transparency
What do you like best about the product?
Most of the older connectors are reliable -- consistent data, a consistent data delivery schedule, easy setup, implementation, and integration.
What do you dislike about the product?
We operate Fivetran in a multi-tenant environment. While not all Fivetran users will have a similar setup, this creates numerous problems.
1. Schema standardization. If we connect the same source for different customers, often different table schemas will be delivered to our destination. Columns will appear in one instance but not another. Column datatypes will be different between instances. Tables may be missing entirely. This problem required us to write a series of very complicated custom scripts to standardize the data delivery.
2. Pricing transparency. Fivetran is very opaque about pricing. Daily summaries of row usage by table are provided, but we often incur large charges where Fivetran is unable to explain why those charges were incurred. The lack of pricing auditability is a big issue.
3. Standard tables. This is a new feature that Fivetran began rolling out mid-2024 which will drastically run up our Fivetran costs if we aren't watching carefully. They are turning on dozens of "standard reports" for common connectors that may increase our usage (and costs) by 5-10x. Currently these cannot be programitcally disabled with the Fivetran REST API.
4. Data delivery control. While we can control database and schema names from Fivetran, we cannot change the behavior of 1 Destination to 1 Database and 1 connector to 1 schema. This has shoehorned us into an unsustainable architecture as we grow.
5. Customer support is below average. If an issue moderate to hard they will close your ticket and not address it.
1. Schema standardization. If we connect the same source for different customers, often different table schemas will be delivered to our destination. Columns will appear in one instance but not another. Column datatypes will be different between instances. Tables may be missing entirely. This problem required us to write a series of very complicated custom scripts to standardize the data delivery.
2. Pricing transparency. Fivetran is very opaque about pricing. Daily summaries of row usage by table are provided, but we often incur large charges where Fivetran is unable to explain why those charges were incurred. The lack of pricing auditability is a big issue.
3. Standard tables. This is a new feature that Fivetran began rolling out mid-2024 which will drastically run up our Fivetran costs if we aren't watching carefully. They are turning on dozens of "standard reports" for common connectors that may increase our usage (and costs) by 5-10x. Currently these cannot be programitcally disabled with the Fivetran REST API.
4. Data delivery control. While we can control database and schema names from Fivetran, we cannot change the behavior of 1 Destination to 1 Database and 1 connector to 1 schema. This has shoehorned us into an unsustainable architecture as we grow.
5. Customer support is below average. If an issue moderate to hard they will close your ticket and not address it.
What problems is the product solving and how is that benefiting you?
Fivetran gives us quick access to data from common APIs.
showing 1 - 10