The initial setup was very straightforward. It took some 20 minutes.

The solution is a typical SaaS product so setup is fairly easy. You get a web URL, login credentials, and you are in. There are baby steps and good guidelines for getting up and running. I can't say setup is different than any other kind of tool for the same purpose, but the solution does the heavy lifting here. 

I am a tech geek with a lot of senior level experience and I find the setup to be intuitive and easy. It might be a bit more difficult for new users who are not heavily involved in the data world. 

I rate setup a ten out of ten. 

The solution is not easy to setup for a startup and SME but if an enterprise wants to do everything hands-on, it's okay for them. The deployment takes a couple of weeks to complete. Two people are needed for implementation.

I wasn't involved with setting up Fivetran, but I'm told it was straightforward. You have to set up a hub and then install it. If you have an on-prem database, it's better to install an agent. That will help with encryption, data transfer, compression, and other things. You can do it without an agent, but the agent will help. We have agents installed on all our data sources. Updates are also easy. We only need to stop the instance while installing the newest version and restart it. 

The initial setup was not that simple because our database sources had a very old configuration, which in some cases could not be changed.

It was straightforward.

We did not do any deployment at all. We started around six months back, and we are just in the early stages of doing a proof of concept. 

Installing the software is really straightforward. Getting your replication stream working is a little bit more complicated, but it is not overly complicated.

The initial setup is the easiest of all the data integration solutions. We don't need to do much; I have only done it with Snowflake and Databricks. We just need to set up a target or destination or protocol destination, which is really easy. On the left side, we have all the information we need to provide to Fivetran. On the right side, they have step-by-step documentation or procedures on how to find this or how to do that, even for connecting to data sources. Fivetran always gives us step-by-step instructions on how to do this, and Fivetran usually has fewer than 15 steps.

Step one was connecting to them, then opening up ports to our cloud, verifying connections, connecting to our different databases from source destinations, testing, and implementing. Obviously, with the initial onboarding there's also security and things like that. 

The initial deployment was fairly small, so it didn't take a particularly long time, maybe a week on and off, in terms of just working with the team and opening ports and connecting. We're on AWS, so some of it was on our side having to do IM rolls and whitelisting.

From a day-to-day perspective of onboarding new ones, it's really just pointing towards sources, then the destinations, and then just doing verifications. Day-to-day is pretty easy. 

The initial setup is very easy. It is not that complex. I was part of the deployment process. It is still ongoing. We are not running production for now.

The product is cloud-based. The deployment process is very straightforward. We get the data from different websites and integrate it into our database. We just sync the data on a daily or weekly basis. We needed two people for the deployment. It took two to three days to deploy the tool.

Fivetran is very easy to set up. It's a matter of having the connection information of each one of the endpoints you want the ETL through. The solution is very comprehensive and easy to set up. It even gives you assistance on where to find the information that you might need, depending on the data source. It has pre-built connectors for the most common data sources, so it also helps you expedite that process if you are not super tech-savvy.

Fivetran's deployment is simple. 

The initial setup was straightforward because we had all the required documentation.

The initial setup was straightforward. 

The initial setup was complex. We had quite a few data sources, so the database replication was quite in-depth and we had quite a few environments that needed to be refreshed.