Change set file limit and splitting large deployments
Key Takeaway
When a change set goes over the 10,000-file limit, move the email templates, dashboards, and reports into separate change sets. Each change set must still include every interdependent component that doesn't already exist in the target org.
A change set moves metadata from one Salesforce org to another, for example from a sandbox to production. Each change set has size limits, so a large release sometimes has to be split into several change sets. To split a release well, you need to know three things: the limits, which components are easiest to move into their own change set, and which components each change set still has to carry.
Change set limits
Change set components are represented as metadata XML files. A change set has two limits on its files and one guideline on its components.
| Amount | Kind | |
|---|---|---|
| Files | Up to 10,000 | Limit |
| Total file size | Up to 400 MB | Limit |
| Components | Under approximately 5,000 | Guideline |
The component guideline is separate from the 10,000-file limit, so check both when you plan a release.