No more typing reviews! Try our Samantha, our new voice AI agent.

CloverETL vs dbt comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 19, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

CloverETL
Ranking in Data Integration
58th
Average Rating
7.0
Reviews Sentiment
6.8
Number of Reviews
2
Ranking in other categories
Data Visualization (35th)
dbt
Ranking in Data Integration
11th
Average Rating
8.0
Reviews Sentiment
6.6
Number of Reviews
11
Ranking in other categories
Data Quality (5th)
 

Mindshare comparison

As of August 2026, in the Data Integration category, the mindshare of CloverETL is 0.8%, up from 0.3% compared to the previous year. The mindshare of dbt is 1.5%, down from 2.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Data Integration Mindshare Distribution
ProductMindshare (%)
dbt1.5%
CloverETL0.8%
Other97.7%
Data Integration
 

Featured Reviews

it_user856614 - PeerSpot reviewer
Lead Programmer at a healthcare company with 10,001+ employees
Very easy to schedule jobs and monitor them, however we run out heap space even with a high allocation
Flexibility: We can bring in data from multiple sources, e.g., databases, text files, JSON, email, XML, etc. This has been very helpful Connectivity to various data sources: The ability to extract data from different data sources gives greater flexibility. Server features for scheduler: It is…
Harshwardhan Gullapalli - PeerSpot reviewer
AI Engineer at a educational organization with 51-200 employees
Data pipelines have improved financial accuracy and now build transparent audit-ready reports
As for something I wish we had, dbt's native support for Python transformations came later, and we did some complex financial classification calculations that felt clunky in pure SQL. We ended up writing Python in our n8n workflows and then fed the results back into dbt, which created a bit of a split-brain situation. If we would have had dbt Python models earlier, we could have kept that logic unified. Managing multiple reporting standards was our biggest operational pain point with dbt. We were running UAE corporate tax compliance and IFRS disclosure workflows simultaneously for different clients, and dbt does not have a native concept of multi-tenant or multi-standard project organization. Everything lives in one flat structure, so we had to build more conventions: separate schema folders for IFRS models versus UACT models, custom macros to tag models by compliance regime, and environment variables to control which set of transformations run for which client.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Key features include wealth of pre-defined components; all components are customizable; descriptive logging, especially for error messages."
"Familiar, intuitive GUI coming from a Java development background, in-depth, descriptive, and well-laid-out documentation, responsive support through forums directly from Clover staff, a wealth of customizable pre-defined components, descriptive logging for error messages, and ease of install with a light footprint make it very effective to use."
"We switched to CloverETL because of its flexibility to connect to various data sources and no dependence on native language and ease of use."
"Server features for scheduler: It is very easy to schedule jobs and monitor them. The interface is easy to use."
"No dependence on native language and ease of use.​​"
"Connectivity to various data sources: The ability to extract data from different data sources gives greater flexibility."
"dbt has positively impacted my organization by allowing us to create our data pipelines much faster, going from ingestion of data to creating a data product in weeks instead of months, and we can do it in-house with the skillset we already have."
"The product is developer-friendly."
"There is operational efficiency achieved, and data quality and governance have also been achieved with modular SQL and version controlling, which reduced duplication of data and data errors."
"It is very convenient because at the end, I have the opportunity to orchestrate all my transformations in just one single place, rather than having them spread out."
"The most concrete outcome was a significant reduction in data errors reaching our downstream AI models, and after implementing dbt's testing layer, we caught roughly 70% of those issues at the transformation stage itself, before they ever touched the model."
"Overall, I find dbt to be optimized compared to other tools."
"dbt has positively impacted my organization by allowing us to expand the ceiling of complexity because once we have written the SQL, we can manage significantly more complexity since we are not spending all of our time doing it ourselves."
"I would say the best feature or the most desirable feature for dbt is the ability to write everything in code."
 

Cons

"Its documentation could be improved.​"
"​Resource management: We typically run out of heap space, and even the allocation of high heap space does not seem to be enough.​"
"Needs easier automated failure recovery, more and more intuitive auto-generated or filled-in code for components, and easier or more automated sync between CloverETL Designer and CloverETL Server."
"Dbt is not as stable as preferred, as it has had a few outages in the current year itself, so improvement should be made in the outages section as it is not stable."
"If you compare the cost of those packages with dbt alone, it is more expensive to use dbt alone."
"Every upgrade is a little bit of a risk for us because we do not know if the workarounds that we developed will be available for the next version."
"Since dbt has a license cost, if a company is small and does not have much budget, they can explore other tools because there are other tools that provide the same functionality at a lower cost."
"The initial setup of dbt is somewhat complex."
"dbt can be improved as I find the co-pilot in dbt is not very good, and my team has tried using it but opted to move off it and use other co-pilots such as GitHub."
"If you want to use more advanced or more complicated SQL features, they are not supported right now by Dbt, so that can be a challenge."
"The solution must add more Python-based implementations."
 

Pricing and Cost Advice

Information not available
"The solution’s pricing is affordable."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
909,948 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
26%
Manufacturing Company
12%
Comms Service Provider
9%
Computer Software Company
9%
Financial Services Firm
16%
Comms Service Provider
7%
Manufacturing Company
7%
Computer Software Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise3
Large Enterprise6
 

Questions from the Community

Ask a question
Earn 20 points
What is your experience regarding pricing and costs for dbt?
My experience with pricing, setup cost, and licensing for dbt is that dbt is open source for its core modules, so the pricing, setup, and everything was really good.
What needs improvement with dbt?
dbt can be improved by introducing Python. Ideally, I would want to be able to orchestrate across the DAG and have both Python and SQL combined. The last time I used it, it was not able to visualiz...
What is your primary use case for dbt?
My main use case for dbt is data pipelines. I build data transformations and usually construct analytics pipelines.
 

Overview

 

Sample Customers

IBM, Oracle, MuleSoft, GoodData, Thomson Reuters, salesforce.com, Comcast, Active Network, SHOP.CA
Information Not Available
Find out what your peers are saying about CloverETL vs. dbt and other solutions. Updated: August 2026.
909,948 professionals have used our research since 2012.