“Fivetran will give you an estimate of MAR during your 14 day free trial. I suspect, based on your comment re: “basic employee data” you’ll be below 500K MAR, and will qualify for the free tier.”
“I've never tried fivetran, open sweat solutions are what I use here, apache hop Airbyte, pentaho and python, no problem extracting several times a day.”
“fivetran's pricing can be tricky. free tier is limited, and with consistent usage, fees might creep up. consider sticking with python or explore other affordable etl tools.”
“Currently using Python to extract data from our HR tool Personio through REST API. Now I saw that fivetran is offering a connector, so I am thinking about switching to easen the extraction process.”
“You’re right that History Mode aims to model SCD2, but in practice it’s closer to a lossy implementation. It tracks versioned rows and soft deletes, but lacks true bi-temporal semantics, no valid\_from/valid\_to, just \_fivetran\_synced snapshots.”
“If Fivetran acquires dbt Labs, companies using dbt but not Fivetran could face vendor lock-in, reduced focus on standalone dbt features and pressure to adopt Fivetran’s ecosystem to stay fully compatible. This may limit flexibility, force reevaluation of their data stack and push them to consider alternative solutions.”
“They will probably get some fivetran equity to stay on. Probably not generational wealth exit but should be comfy to buy a big house in Philly suburbs.”
“Fivetran doesn't need to save money or anything. They need to be pretty enough to IPO. Buy dbt labs, corner the market, assume their ARR looks pretty for IPO and exit.”
“Since the exorbitant price changes in march, many SF reps are looking for alternatives. Fivetrans pricing is now becoming a drag on consumption. Not surprising FT had to do something, they raised at a crazy valuation at the peak of 2021 which they’re unlikely to ever hit again in this lifetime.”
“Haha me too, dbt is very popular in EU, Ofcourse dbt core not cloud, but I have heard any of the companies I have been working with or interviewed for use Fivetran.”
“The acquisition of SQLMesh not long ago puts some interesting technical glue in the middle but they would benefit greatly from the dbt customer base.”
“It’s the only viable alternative to dbt.Of late fivetran’s service for us has been terrible. Connectors failing. Support taking weeks to fix things. I guess we will see what they do with them?”
“They will do exactly what dbt did. Push hard as open-core then when they have enough marketshare, rug pull and begin to "extract value." It is the tried and true playbook.”
“Fivetran will save you setup and maintenance pain, but you're right that the post-load transform model kills you for PII compliance. There's just no way around that unless you front it with a proxy or pre-processor, which kinda defeats the point of Fivetran.”
“Fivetran works great for many SAAS apps, has tons of connectors, great monitoring, keeps track of schema changes on the Saas Vendor side, and handles the changes automatically. They're close to 0 intervention when it comes to managing schema changes.”
“If you aren’t looking to code up your own internal data extraction solution or don’t have access to a reasonably sized team of developers to build it all, Fivetran will do most of what you’ve specified. It does field masking on the fly, has native connectors for business applications like those and can perform high volume extracts for very chatty databases.”
“Fivetran handles retries better but if something silently fails or rows get dropped, you may not know until you are paged. We had a few late night surprises there.”
“Fivetran's pricing became quite high after they raised their rates, and that pushed us to look for alternatives. I’d say both tools did the job, but [Skyvia tool] (https://skyvia.com/) offered a simpler and more cost-effective pricing model.”
“Fivetran seems quick to set up with solid connectors but their transforms (like PII masking) happen post load which breaks our compliance rules. SCD2 would mean custom dbt jobs, adding cost and complexity.”
“I remember waiting for days for Fivetran to respond to support tickets, which cost us a fair bit of revenue a couple times. Hevo's support was definitely a lot more responsive.”
“The MAR model already catches a lot of teams off-guard, and adding per-connector pricing just compounds it. Curious: when you moved to Hevo, did you notice any differences in connector reliability or support compared to Fivetran?”
“The problem with usage based pricing is that it seems low at start and then it increases rapidly as you scale. You will see this with other products like Hubspot as well.”
“Fivetran has a huge library of connectors however so it might still be the feasible option if OP needs it to connect to tools others are not using. (I don't see it being the case here).”