Dataloader.io vs Domo comparison

"DataLoader is cost-effective since it is free."

"I find DataLoader's ability to easily integrate with external keys valuable, which is a bit more challenging with DBM."

"he product’s most valuable feature is ease of access."

"The ETL tools they have in Redshift are pretty awesome... I can work in Redshift to get the data from AWS and work in Redshift, in Domo, to create Transforms and the data structure we need..."

"The best thing is that the data storage is pretty much free. I can store as much data as I want, from different sources."

"In general, Domo is very powerful and very easy to use, relatively speaking."

"The ability to create custom connectors was useful because you never know, with customers, what platform they want to utilize or what data they have. It gave us a lot of flexibility in being able to bring data in from different places."

"Using the "cards" which function as preconfigured reports or views. I use many of them simultaneously on an organized page, with filters that allow me to see high-level information as well as subsets across the dataset, in a few clicks. Many Excel-challenged users love to use this product for its simplicity."

"The best feature of Domo is that it's completely on the cloud. I also like that you can handle data end-to-end without having to depend on multiple tools. Another specific feature I like the most about Domo is Magic ETL because, through it, you can do all your expression, transformation, and loading activities very smoothly. The tool also follows the lineage concept, so you can understand what kind of transformations took place on a particular data set. You can find end-to-end data from the source until it has become the final output or the final data set. Whatever happened to a particular data set, you can understand it through the Domo lineage, and that isn't possible in most of the tools available in the market, but in Domo, that's available. The tool is also solid and because it's on the cloud, it uses multiple data engineering in the backend and multiple algorithms in the back, behind the scenes, resulting in a great performance. For example, if an end user such as the CEO or COO opens a report or the dashboard and it takes more than ten seconds, the end user won't be interested in looking at that report or dashboard, but Domo enables better performance and there's usually no performance issues from that tool."

"The dashboarding itself was pretty easy. So both the front and the back end were positive in this case."

"It has the best GUI. And it already has an ETL tool embedded in it..."

"Dataloader has limitations, including constraints with file sizes and transactions. Additionally, at times it can be slow, and when integrating DBM, we find it more complex than Dataloader."

"DataLoader has limitations, including constraints with file sizes and transactions."

"We need help with large data migrations. It only works well for a few thousand records or less than a million records."

"Domo or any other BI tool has room for improvement, in particular, in the calculations. User-guided material isn't available for calculations. The tool, though user-friendly, could also be more customizable, especially when you're building a dashboard. Data integration could also be improved in Domo because even if the tool connects to multiple data sources, some hiccups still arise and need to be addressed."

"I would like to see more dashboard creation options."

"It's quite slow. We are using about 2,000,000 rows of data. Creating certain reports takes almost a couple of minutes, which should not be the case."

"The preconfigured apps need to be more relevant to allow one, out of the box, to load data in order to use pre-set reports/views."

"The ETL way of storing is not up to mark. You have to rely on the naming convention that you're using in Domo because there are no folder systems where you can collate all your workflows and put them into separate folders. A folder system should be there so you can easily identify how you are working. Once you want to make some changes to your ETL, then you can see the whole lineage, identifying what is there and not there."

"I would like to see better data intake."

"They could use more charts. They have had a very limited number of charts we can use. I believe, now, there are somewhere around 30 of them, but they could definitely use some more options."

"It is expensive."

"The product is inexpensive and economical."

"No matter if you're a developer or an end-user, the licensing cost is around $12 per user per month."

"I think it is reasonable."

"They've built an "app economy." Some of them are really expensive, so they're not for startups and smaller companies. They're more like enterprise tools. We couldn't afford some of them, because they were so crazy expensive. But if I was working for a bank, insurance company, or some bigger corporation then, for sure, you could justify those prices... It was silly expensive back then and it probably still is, or even more expensive."

"The pricing differs from customer to customer, depending on the package."

"I'm not sure about pricing, but I believe Domo is quite costly. Prior to joining this organization, I had a Domo license with my former employer and I think that license was around $500 to $600 annually. That was for a single license. I think it varies, depending on the organization that is acquiring Domo."

"The price that they offered was around $200 per user license. It was pretty cheap at that time compared to other companies. I think they have revamped their pricing structure since then."

"The solution is expensive compared to one of its competitors."

"I believe that the investment in Domo was worthwhile because it allowed for the organization to jump in quickly, with little training. There are different plans available based on the requirements."