The pattern: authorize Dataloader.io against the org, configure the job (operation, source, mapping, schedule), monitor results, iterate on errors. The cloud-based workflow eliminates most friction of the desktop Data Loader; admins who switch typically do not go back.
- Open Dataloader.io and authorize against the org
dataloader.io or Setup, Integrations, Dataloader.io. OAuth the org. Multiple orgs supported per Dataloader.io account.
- Pick the operation: Insert, Update, Upsert, Delete, Export
Operation-driven wizard. Pick the right operation; mistakes (Insert when Upsert was intended) produce duplicates.
- Pick the target object and source CSV
Object first, then source. CSV from local upload or cloud storage (Dropbox, Box, FTP, SFTP). Cloud storage enables recurring jobs.
- Map CSV columns to Salesforce fields
Auto-map suggests based on column names; manual mapping for non-standard names. Validate before running; mismatches produce row-level errors.
- Configure options: batch size, parallel mode, error behavior
Defaults work for most operations. Tighten batch size or switch to Serial for locking-prone scenarios.
- Run the job and monitor in the browser
Dataloader.io shows progress in real time. Per-record results download as CSV on completion.
- Schedule recurring jobs as needed
For recurring loads, configure the job once with cloud storage source and schedule. The job runs automatically; admins monitor through job history.
Insert, Update, Upsert, Delete, Export. Drives every other wizard step.
Local CSV upload or cloud storage (Dropbox, Box, FTP, SFTP).
One-time or recurring (hourly, daily, weekly, custom cron).
Record limit and feature availability vary by tier.
Per-job tuning for throughput and locking behavior.
- Free tier caps at 10,000 records per month. Production-volume usage requires Pro or Enterprise.
- Scheduled jobs require a Pro tier or above. Free tier supports only one-time runs.
- OAuth authorization persists. Connected Apps OAuth Usage shows Dataloader.io as an authorized app; treat it as a Connected User for security audit.
- Cloud storage integration requires the storage account credentials. Misconfigured credentials produce silent job failures.
- Per-record results persist in job history but not indefinitely. Download or ship to long-term storage if compliance requires.