Here is the outbound side of a change set deployment, from building the package in your sandbox to handing it off as an inbound change set in the target org. Do the work in the source org where your changes already exist and are tested.
- Open Outbound Change Sets
In the source org, go to Setup and type Outbound Change Sets in the Quick Find box. Select it, then click New to start a change set. Give it a clear name and a short description so reviewers know its purpose.
- Add your components
Click Add on the change set detail page. Pick a component type, select the specific items you want to deploy, and click Add to Change Set. Repeat for each type. The set stays editable until you upload it.
- Resolve dependencies
Click View/Add Dependencies to see direct and indirect components your selections rely on. Add any that do not already exist in the target org, then review the full list once more before uploading.
- Upload to the target org
Click Upload and choose the connected target org. Once the upload completes, the change set is locked and appears in the target as an inbound change set. Hand off to a target-org admin to validate and deploy.
A descriptive name and a one-line description that tell reviewers what the package contains and why it exists.
The metadata items you add by type, such as custom fields, Apex classes, page layouts, and custom metadata types.
The dependency tool that surfaces related components so the deployment does not fail on a missing reference.
The connected org you upload to, selected from the deployment connections that have authorized inbound change sets.
- An uploaded change set is locked. To fix a missing component, clone the set, add the piece, and upload the clone.
- The target org must authorize inbound change sets from your org first, or it will not appear as an upload destination.
- Deploying Apex to production runs local tests by default and must meet the code coverage requirement, so validate before the real deploy.