Overall Satisfaction with Dataloader.io
As a Salesforce Admin, I use it pretty regularly. I have an assistant who I am teaching to use it as well. We have a massive database with millions of records so we have to pretty frequently do updates on lots of records at the same time. It helps us save an insane amount of time. I also use it to export data out of and then upload the data back into Salesforce.
- Mass manipulate data into Salesforce
- mass export data out of Salesforce
- Save so much time for us and is extremely accurate.
- It looks a little outdated- could use a refresher
- It's particularly expensive-hard to convince admins to pay for the better versions
- I work for two orgs and sometimes it can be difficult to switch back and forth between the dataloaders.
- We still have the free version so positive ROI!
- Don't really see it as increasing revenue, but it does save a bunch of time, which allows me to do other things
- I'd have to see the enterprise version to make a better assessment. It is definitely extremely a helpful too.
Salesforce is attached to Dataloader.io and is easy to access through Salesforce. They also have a robust free version that most smaller businesses will find perfectly acceptable. I have only find some situations in which I needed the more expensive version. It is less helpful for exporting data out of Salesforce.
Do you think Dataloader.io delivers good value for the price?
Are you happy with Dataloader.io's feature set?
Did Dataloader.io live up to sales and marketing promises?
Did implementation of Dataloader.io go as expected?
Would you buy Dataloader.io again?
I think it's extremely useful any time you have to change records with the same data. Very useful when you also need to upload data into Salesforce. Also, very useful when you need to do the combination. The only issue that you can run into, and it's no fault of Dataloader.io's, is when you have to manipulate a bunch of records, sometimes the record id's can get a little mixed up and you can accidentally update the wrong records. You have to be careful not to do that and identify the duplicates before hand. I think it's always appropriate and will use it for records of more than 20 honestly.