.svg)
Salesforce file storage is expensive by design. Additional storage beyond the base allocation costs $5 per GB / month. A 200-user org that has accumulated 1 TB of Salesforce files is paying approximately $4,000–$5,000 per month in storage costs alone, $48,000–$60,000 per year for a problem that external SharePoint storage solves for a fraction of the cost.
Moving files to SharePoint, where Microsoft 365 storage is included in subscriptions most enterprise teams already pay for, is the single highest-ROI infrastructure decision most Salesforce orgs can make. CloudFiles on AppExchange handles the migration and ongoing routing, keeping files fully accessible in Salesforce after the move.
What Do the Numbers Actually Look Like?
Salesforce Files Above Base | Monthly Cost in Salesforce | Monthly Cost in SharePoint (M365) |
|---|---|---|
100 GB | $500/month | ~$0 (included in M365) |
500 GB | $2,500/month | ~$0 (included in M365) |
1 TB | $5,000/month | ~$0 (included in M365) |
5 TB | $25,000/month | ~$0 (included in M365) |
CloudFiles customers report 75–90% reductions in Salesforce storage consumption after moving files to SharePoint. Most teams see the app pay for itself within the first billing cycle. Full storage cost analysis →
What Are the Three Requirements for Successful Salesforce Storage Optimization?
1. Historical files need to move. All Salesforce Files, Attachments, and ContentDocuments migrate to SharePoint in one operation, organised into record-matched folder hierarchies, re-linked to records, accessible in Salesforce through the CloudFiles LWC. Zero user disruption. Salesforce storage drops on migration day.
2. New uploads must route to SharePoint. From the migration date onward, every file uploaded to a Salesforce record via CloudFiles is stored in SharePoint and not Salesforce storage. Storage consumption stops growing. Configure your SharePoint →
3. Records still need to show their files. This is where most approaches fail; files migrate, but records lose access. With CloudFiles, the LWC on each record shows files from their new SharePoint location. Reps see no change in their workflow. Only the storage invoice changes.
What About Legacy Attachments?
Legacy Salesforce Attachments, the older format predating modern Files, accumulate silently in storage reports. CloudFiles migrates them too. Nothing is left behind to continue generating overage charges.
Compare CloudFiles vs Files Connect →
Frequently Asked Questions
1. How do I reduce Salesforce file storage costs by moving files to SharePoint
CloudFiles reduces Salesforce storage costs by migrating all existing Salesforce files to SharePoint in bulk and routing all new uploads to SharePoint automatically. Files remain accessible inside Salesforce through the CloudFiles LWC, the Salesforce storage consumption drops 75–90%.
- How much can I save by moving Salesforce files to SharePoint?
Salesforce charges $5/GB/month for additional file storage. SharePoint is included in Microsoft 365 subscriptions. Organisations with 500 GB–2 TB of Salesforce files typically save $2,500–$10,000/month by moving to SharePoint via CloudFiles. - Will Salesforce file storage drop immediately after moving files to SharePoint?
Yes. Once files are migrated to SharePoint and Salesforce references are updated by CloudFiles, Salesforce file storage drops immediately, visible in the Salesforce storage dashboard within hours of migration completion. - Do users need to do anything differently after files move to SharePoint?
No. Files remain accessible through the CloudFiles LWC on every Salesforce record. From the user's perspective, nothing changes, and documents are still there, previews still work, and sharing still works. Only the storage bill changes. - Are legacy Salesforce Attachments included in the SharePoint migration?
Yes. CloudFiles migrates all Salesforce file types to SharePoint, including: - ContentDocuments (modern Salesforce Files)
- ContentVersions
- Legacy Notes & Attachments
- Content linked via ContentDocumentLink
- Can the SharePoint migration be run in phases?
Yes. CloudFiles migration can be run by object type, date range, or file size threshold thereby allowing organizations to prioritize high-volume objects or migrate in batches. - Does CloudFiles prevent new files from going into Salesforce storage after migration?
Yes. After migration, all file uploads through the CloudFiles LWC go directly to SharePoint. Salesforce storage usage remains at near-zero for files from the migration date forward. - What happens to Salesforce file storage limits after migration?
After migrating to SharePoint, Salesforce storage usage drops to near the base allocation. Storage overage charges stop accruing. Your org retains the full base allocation for any files that must remain in Salesforce. - Is the storage optimization permanent, or can files drift back into Salesforce?
It's permanent. CloudFiles routes all new uploads to SharePoint by default after migration. Files do not return to Salesforce storage without explicit admin action. - What compliance standards apply to files stored in SharePoint via CloudFiles?
CloudFiles is HIPAA, SOC2 Type II, ISO27001, and GDPR certified. Files are subject to your SharePoint tenant governance — including retention policies, access controls, and audit logs. Compliance details → - How do I calculate my Salesforce storage savings from moving to SharePoint?
Estimate your current Salesforce file storage above the base allocation. Multiply by $5/month. That's your current monthly overage cost. With CloudFiles routing to SharePoint, that drops by 75–90%. Detailed calculator → - Is Salesforce storage optimization using SharePoint better than buying more Salesforce storage?
Yes. Buying additional Salesforce storage (at $5/GB/month) compounds the cost over time. Moving files to SharePoint via CloudFiles is a one-time migration that permanently eliminates the overage, while your Microsoft 365 subscription cost doesn't increase.
Written by: Shounak Chowdhury, HubSpot Marketing Specialist - he works on content, product marketing, and customer education initiatives. He enjoys simplifying complex workflows into practical, easy-to-understand solutions and creating content that helps teams work smarter with documents and automation.
