Salesforce change sets and their hidden limits
The Gearset blog post explains how Salesforce change sets move metadata from a sandbox to a production org through a deployment connection, using the Metadata API. It describes limits including no org-to-org moves across unrelated orgs, manual component selection, a dependency tool that misses indirect links, locked uploads that must be cloned and re-uploaded, and profile deployments that overwrite target permissions.
What changes for platform teams
Platform teams running Salesforce release pipelines should expect change sets to need manual dependency review, full rebuilds after any fix, and careful handling of profile metadata. The post is a vendor article promoting an alternative deployment tool, so its framing is not independent evidence.
Read the original at Gearset Blog ↗
written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules