Fivetran vs Stitch, a Talend company

• Quick replication of data with minimal lag.
• Automated reporting if data is out of date.
• The customer support team is relatively good.

Read full review

• Stitch does one thing and does it well: turn the data ingestion from third-party APIs into a one-click task
• It makes all that data into a proper schema as a bonus

Read full review

• A full schema refresh takes us two-three days and knocks us offline from monitoring up-to-date business KPIs, running updated analyses, etc. This is likely due to us having massive amounts of data (from a count(1) perspective, not size of tables perspective).
• There's little to no progress estimate on the front end UI to see how long this refresh might take and you need to enable back end logging in Amazon to see where it's at in the sync process and derive rough estimates of completion time.

Read full review

• Stitch is not good at replicating document stores like MongoDB to relational databases. To be fair, this is a difficult task. Stitch flattens the objects, but the result is unwieldy.
• Stitch cannot replicate the same source to multiple sinks, which is inconvenient if you want to replicate some of a datastore's tables to Redshift and others to Redshift Spectrum, for instance.

Read full review

• I don't think about ETL (Extract, Transform and Load).
• I don't process any ETL, it's set it and forget it.

Read full review

• It has enabled the company to get new insights by joining together datasets that were previously stored in different places.
• It has saved weeks of work that were used to do more profitable activities than building intregations.
• It has allowed us to import in the company's data warehouse all the conversations that the customer service agents have had with the customers in case of a potential argument.

Read full review