Salesforce Change Sets: A Step-by-Step Guide for Admins

Diagram of an outbound change set moving a custom field and validation rule from a sandbox to a production org

Salesforce change sets are how admins send Setup customizations from one org to another, usually from a sandbox to production. You build an outbound change set in the org that holds the change, upload it, and deploy the inbound change set in the org that receives it. This guide walks through each step, the limits Salesforce documents, and a checklist to run before you click Deploy.

Salesforce's own Change Sets documentation puts the purpose plainly: "Use change sets to send customizations from one Salesforce org to another." Everything below is based on Salesforce's public Help pages, linked where each fact comes from, so you can confirm the current wording in your own org.

What Salesforce change sets can and cannot do

A change set has two sides. In the sending org you create an outbound change set. Once you upload it, the receiving org sees it as an inbound change set, and the changes take effect only after someone deploys it there. Salesforce also states that you can deploy an inbound change set as a whole but not component by component.

Four rules decide whether change sets fit a given job:

  • Related orgs only. Change sets move between orgs that are connected through a deployment connection. The deployment connections article says you cannot create connections between arbitrary orgs: connections exist between a production org and its sandboxes, and between those sandboxes.
  • Edition and permissions. The overview lists Enterprise, Performance, Professional, Unlimited and Database.com editions. Sending needs the Create and Upload Change Sets permission, and deploying needs Deploy Change Sets together with Modify Metadata Through Metadata API Functions.
  • Only supported components. The components article says the available components vary by experience and edition. Components that are not on the list cannot be sent by change set and must be migrated manually.
  • No delete, no rename, no undo. The best practices article says you cannot use change sets to delete or rename components, and that a change set is limited to 10,000 files. The implementation tips add that a change set deploys in a single transaction, so a failure rolls everything back, and that a successful deployment cannot be rolled back.

The components list is long. It includes familiar admin building blocks such as custom objects, custom fields, validation rules, flows, permission sets, Lightning pages, reports and email templates. Check the current list for your edition before you plan a release around a component you rarely move.

Before you build: connection, authorization and permissions

Three things have to be true before the first click. Skipping them is the most common reason a first change set stalls.

  1. The deployment connection exists. Production and its sandboxes show up on the Deployment Connections page in Setup.
  2. The target org allows uploads. A connection alone is not enough. The deployment connections article says each org must be authorized to send and receive change sets, and the implementation tips say an administrator in the target org must authorize uploads across the connection.
  3. Your user has the right permissions. You need the sending permission in the source org. Whoever deploys in the target org needs the deploy permissions listed above.

Also check the calendar. The implementation tips note that uploading and authorizing are unavailable while production is in maintenance, although you can still build outbound change sets.

How to build, upload and deploy a change set, step by step

The steps below follow Salesforce's Help articles for creating an outbound change set, selecting components, adding dependencies, uploading, validating and deploying. Run the first four steps in the source org and the last two in the target org.

  1. Open Outbound Change Sets. From Setup, enter Outbound Change Sets in the Quick Find box, then select Outbound Change Sets. Click New to start a change set.
  2. Add your components. Open the change set and click Add. Choose the type of component and the components you want, then click Add to Change Set. If you need profile settings, click Add Profiles. Salesforce notes that profile settings cannot be added in Professional Edition.
  3. Add the dependencies. Click View/Add Dependencies, select the dependent components you want to send, then click Add to Change Set. Salesforce advises adding them unless the same components already exist in every target org. Expect unexpected entries: outbound change sets include direct and indirect dependencies. If a change set has more than 2,500 dependencies, the Component Dependencies page shows only the first 2,500.
  4. Upload it. From Outbound Change Sets, click Upload next to the change set, select the org you are sending it to, and click Upload. Salesforce says you cannot edit or recall a change set after upload. If you forgot something, use Clone, add what is missing and upload the clone. Outbound change sets expire six months after upload and are then permanently deleted.
  5. Validate in the target org. Sign in to the target org. From Setup, enter Inbound Change Sets in the Quick Find box, then select Inbound Change Sets. Click Validate next to the change set, and when validation finishes click View Results. Salesforce says a successfully validated change set can sometimes qualify for a quick deployment.
  6. Deploy. On the same Inbound Change Sets page, click Deploy next to the change set. To review the contents first, click the change set name, then click Deploy. If a deployment fails, you must restart it manually, because Salesforce does not restart a failed validation or deployment for you.

A worked example: moving a field and its validation rule

Say you built a custom field and a validation rule on an object in a sandbox, and sales users need to see the field in production. Here is how that looks as a change set:

  1. Create an outbound change set with a name that describes the change, such as the object name and the purpose of the field.
  2. Add the Custom Field and the Validation Rule. Both are on the components list.
  3. Add the Permission Set that grants access to the field if users get their access that way. Permission Set is also on the list.
  4. Click View/Add Dependencies and review what Salesforce suggests. If you were moving a new custom object, the best practices article warns that you must add the object and every one of its fields, or the object deploys empty.
  5. Upload, validate and deploy in the order above, then open a record in the target org and confirm the field and the rule behave as they did in the sandbox.

The same pattern works for most small releases: one change set per change, a name a colleague can read six months later, and a short test of the result in the target org.

Test runs and code coverage

If your change set includes Apex, tests matter. The best practices article says that when you deploy Apex to production, all local Apex tests in that org run by default, and that tests do not run automatically when the target is a sandbox. The deployment article adds that Salesforce requires at least 75% of your code to be covered by unit tests before you can deploy it to a production org, and that this requirement is not enforced in sandbox or Developer Edition orgs. If your release is flows, fields and permission sets only, you are in simpler territory, but validating first is still the cheapest way to find a missing dependency.

Validation has a cost too. The best practices article says the originating org is locked while it validates an outbound change set and the target org is locked while it deploys an inbound one, so plan big deployments around production and sandbox maintenance schedules.

A checklist to run before you click Deploy

  • The change was built and tested in a sandbox first. Our guide to Salesforce sandbox best practices covers choosing a sandbox type and validating changes before production.
  • The change set holds every interdependent component that does not already exist in the target org.
  • Any custom object in the set comes with all of its fields.
  • Permission sets or profile settings are included if users need access on day one.
  • You validated the change set in the target org and read the results.
  • Apex tests and the 75% coverage requirement are sorted out if the set includes code and the target is production.
  • Someone knows what to do if the release needs reversing, because Salesforce says a successful deployment cannot be rolled back. In practice that means a second change set or a manual fix.
  • The change is recorded in your change log. Our Salesforce change management checklist for admins and small teams shows how to track intake, approval and rollback around each deployment.

Common change set problems and how to avoid them

A missing dependency. Salesforce says each outbound change set should contain every interdependent component that does not exist in the target org, or the deployment fails. Always run View/Add Dependencies before you upload. Because you cannot change a change set after upload, adding a forgotten component means cloning.

Waiting on a large dependency tree. The implementation tips warn that opening a change set whose components have many dependencies can take several minutes. Keep sets focused instead of bundling a whole quarter of work into one.

Field type changes. The best practices article warns that changing a field type can delay a deployment for a long time, because many records may need to change. Salesforce suggests applying that kind of change manually after deployment as an alternative. Salesforce's article on validating adds that Validate does not support changing a field from Master-Detail to Lookup or the other way round, and recommends a full deployment to a test sandbox for those changes.

Users that do not match. The implementation tips say usernames are matched in the destination org, and that a sandbox suffix such as ".test" is ignored during deployment.

Things change sets cannot do. You cannot delete or rename components, standard objects cannot be included, and anything outside the supported components list moves by hand. When your release needs one of those, plan a manual step in the release notes, or ask your developers whether another deployment route is already in use.

Where change sets fit in a wider admin routine

Change sets are a transport tool. They do not tell you what to change, who approved it or whether it worked. The admins who get the most from them pair a sandbox, a short written release note and a quick check in the target org after every deployment. That discipline also makes the work easy to hand over and easy to audit later.

Cirra AI is building Cirra Admin to support admins with routine Salesforce setup work like this. Today, Cirra AI's Salesforce Admin MCP Server builds and changes components such as fields, validation rules and flows from the AI client you already use, working as the connected user within that user's permissions. You can read more about how Cirra AI supports Salesforce admins. Whatever tools you use, the Salesforce documentation linked above stays the source for what change sets do. Menu names and limits can change between Salesforce releases, so confirm each path in your own org before you rely on it.

Frequently asked questions

What is a Salesforce change set?

A Salesforce change set is a package of customizations that you send from one org to another. You create it as an outbound change set in the sending org, upload it, and deploy it as an inbound change set in the receiving org.

Can I undo a Salesforce change set deployment?

No. Salesforce says a successful change set deployment cannot be rolled back. A change set deploys in a single transaction, so a failed deployment rolls back completely. To reverse a successful release, you need a new change set or a manual fix.

Which orgs can I send a Salesforce change set between?

You can send change sets between a production org and its sandboxes, and between those sandboxes, when a deployment connection exists and the receiving org has authorized uploads. You cannot create connections between arbitrary orgs.

Share the Post:

Related Posts