Practical guides to Salesforce file migration, data migration, and storage cost reduction — written by Salesforce practitioners, not marketing teams.
Start here. Each article is a deep, standalone reference for one common Salesforce migration or storage problem.
An end-to-end walkthrough of moving ContentDocuments and legacy Attachments between Salesforce organizations: the file model, the eight steps of a clean migration, common failure modes, and how to verify a successful run.
Before you migrate, you need to know what you have. SOQL queries for counting ContentVersions, Attachments, and Notes; how to classify files by type; how to break counts down by parent object; and a worked example for scoping a migration.
A practical guide to Salesforce data and file storage pricing, why it grows faster than you'd expect, and the four strategies for shrinking it — with the trade-offs of each (deletion, archival, retention orgs, and tiering).
The Salesforce file model is unintuitive: four objects with overlapping responsibilities, two parallel systems for storing files, and confusing relationships. A clear reference for admins, developers, and anyone debugging a file-related issue.
Salesforce bills data storage and file storage separately, and the math behind each is unintuitive. A reference for what counts, how limits scale with your edition, and how to check your current usage before it triggers a warning.
If you're scoping a project and the guides above leave open questions, get in touch — we'll walk through your scenario.