Move ContentDocuments, ContentVersions, and legacy Attachments between Salesforce orgs at bulk scale — with metadata preservation, real-time progress, and per-file audit reporting.
Salesforce gives you no native bulk file transfer between orgs. Manual exports lose metadata, break sharing, and offer zero progress visibility. EKE Services Salesforce File Migration replaces that.
Migrate only the files you need. Filter by creation date and parent object type — Account, Contact, Case, Opportunity, plus any custom object — to scope precisely. No more all-or-nothing migrations that overshoot the project.
Watch a live dashboard as files move file-by-file. Counts update in real time so you know whether the migration is healthy, throttled, or silently failing — not staring at a spinner for six hours.
Large migrations distribute work across configurable parallel workers, processing thousands of files concurrently. Semaphore-based concurrency control respects Salesforce API rate limits while maximizing throughput. Bulk API 2.0 is used automatically for high-volume operations with REST fallback for precision.
Every job produces a downloadable report: source file ID, target file ID, parent record, file size, and status (success, skipped, or error with reason). Hand it to stakeholders for sign-off or attach it to your project audit trail.
File ownership, sharing visibility, ContentDocumentLink associations, and custom file metadata fields all transfer to the destination org. Pre-migration validation surfaces mapping issues before any data moves.
Review past migrations, download previous reports, and re-run failed jobs without reconfiguring from scratch. The tool resumes from per-file status, so successful uploads aren't repeated on retry.
Acquired company runs on its own Salesforce org. Files from the acquired org's Accounts, Cases, and Opportunities need to land alongside the parent records once those are migrated. File Migration handles the second half of that workflow once Data Migration has aligned the records.
Sandbox refreshes copy records but not their files. After a Partial or Full Copy refresh, use File Migration to bring across attachments for the records you actually need to test against — without copying the entire production file store.
Older orgs accumulated files as legacy Attachments (00P). Many teams want to migrate these to modern ContentVersion records (069) — either within the same org or as part of a move to a new org — to align with the modern Files architecture and gain ContentDocumentLink sharing.
Salesforce File Migration is the process of moving ContentVersion files, legacy Attachments, and their parent-record relationships between Salesforce orgs while preserving metadata. You need it during org consolidations, M&A integrations, sandbox refreshes seeded with production files, or org splits.
Yes. The tool migrates ContentVersion records (069 ID prefix), ContentDocumentLink sharing relationships, and legacy Attachments (00P prefix). Each file is classified at scan time so you can target a migration to one type or both. See our ContentVersion vs. Attachment guide for the difference.
Migrations distribute work across configurable parallel workers with semaphore-based concurrency control. The tool uses Salesforce Bulk API 2.0 for high-volume operations and falls back to REST API for precision. Built-in rate limiting respects per-org daily API limits, so you won't blow your daily allotment mid-migration.
Every file's status is tracked in the job's CSV report (success, skipped, or error with reason). Failed jobs can be re-run without reconfiguring — the tool resumes from where it left off based on the per-file status, so you don't re-upload files that already succeeded.
Most org-to-org projects need more than just file movement.
Move structured records — Accounts, Contacts, Opportunities, custom objects — with schema comparison, automatic field creation, and dependency-aware ordering. Run before File Migration so files have parents to attach to in the target org.
Learn more →Once your files have landed in the target org, archive older ones to S3 to keep storage costs down — with custom Salesforce tracking objects so archived files remain discoverable.
Learn more →Tell us about your source and target orgs, file volume, and timeline. We'll show you the tool against a representative dataset.