Cloudingo vs DemandTools

• The automation engine is extremely powerful. I have over 500 fields on some objects and I want to do different things with that data depending on what the master record is. I was able to configure Cloudingo do all this. i.e. set it and forget it and I just get an emailed report.
• Visualization of the problem areas is completely unique. Cloudingo has a dashboard concept with tiles and those tiles represent ways of looking at the data and potential duplicate records.
• Innovate - every suggestion I've given them they have implemented and then some. Cloudingo really pushes the pace and I am always thankful when new releases come out because they put in cool stuff that I would have never thought of.

Read full review

• Report/Find IDs is the hidden gem of DemandTools. It is basically a super fast vlookup against your entire database. Easily add data to a report or find the records that match a list. I used this feature extensively when migrating data to a new org to do a compare numbers.
• Data export by object is so easy and the ability to pull data from any related object is powerful. I find myself using data export more then running reports in SF because it's so much faster and hugely flexible.
• Every module has clear steps and in-line help.

Read full review

• I wish there were a few more merge operators. You can set merge rules based on "equals", "oldest date", etc., but there is no "contains" operator.
• Hard to use. The platform is just very complex. Not sure how you'd get around this though since this type of mass action is very involved.
• The price difference between the standard package and the pro package is a very big jump. But it has to be since the pro uses a REST API.

Read full review

• Information overload for new users, due to the large number of things DemandTools can do (not inherently a bad thing, but still a challenge early-on).
• In a similar fashion, it's hard to determine what DemandTools can and can't do out-of-the-box.
• Hard to find documentation that gives a high-level overview of whether DemandTools can do what you want to attempt or not.

Read full review

• Neglected and not used due to destructive automation
• Fear of cleaning up data
• Not wanting a human to do proper cleansing

Read full review

• A positive impact that I see from using DemandTools is that we have less of a need for man-power. Before DemandTools, I deduped records and changed records using native Salesforce products. I just deleted 100,000 records in 5 minutes with DemandTools and to duplicate that function in Salesforce would take much longer and would actually be a more troublesome task to complete.
• A negative impact that I see is that there are several bundled products that come with the package that we do not need. When we first signed on with DemandTools several years ago, the price was much more reasonable. Since being bought by Validity, DemandTools is now bundled into a larger package with other products and the price more than doubled. We've expressed that we have no need for additional products at this time, but everything is within a bundle. I've utilized multiple packages where those add-on functions can be purchased for an additional price and that's what I think Validity should go back to for their customers.
• All-in-all, I'm a big advocate of DemandTools and I think it is a vital package for our institution. I personally could not do my job as efficiently as I do without this product.

Read full review