---
schema_version: "1"
id: 4f9197f2eecb959a83d3833367993360dfabff6c3ac7d9e521bf67d7578664e2
title: Change Sets
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/changesets.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.changesets.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 1e5528afdb31fc0a4c2817e3cb79ac7c1afddc19d8393c4ca199c1c8047eeb68
description: Use change sets to send customizations from one Salesforce org to another. For example, you can create and test a new object in a sandbox org, then send it to your production org using a change set. Change sets can contain only modifications you can make through the Setup menu. For example, you can’t use a change set to upload a list of contact records. Change sets contain information about the org. They don’t contain data, such as records.
products:
  - Salesforce Platform
release: "264"
---
# Change Sets

Use change sets to send customizations from one Salesforce org to another. For example, you can create and test a new object in a sandbox org, then send it to your production org using a change set. Change sets can contain only modifications you can make through the Setup menu. For example, you can’t use a change set to upload a list of contact records. Change sets contain information about the org. They don’t contain data, such as records.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Professional</strong>, <strong>Unlimited</strong>, and <strong>Database.com</strong> Editions</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
      <colgroup>
        <col style="width:50%">
        <col style="width:50%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d13157e76">User Permissions
            Needed</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d13157e76 ">To edit deployment connections:</td>

          <td class="slds-cell-wrap" id="changesets__perm_edit_connection" style="vertical-align:top;" headers="d13157e76 ">
            <p>Deploy Change Sets </p>
            <p style="margin-bottom:0;">AND</p>
            <p style="margin-bottom:0;"> Modify Metadata
              Through Metadata API Functions</p>
          </td>

        </tr>
        <tr class="">
          <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d13157e76 ">To use outbound change sets:</td>

          <td class="slds-cell-wrap" id="changesets__perm_outbound_changesets" style="vertical-align:top;" headers="d13157e76 ">Create and Upload Change Sets</td>

        </tr>
        <tr class="">
          <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d13157e76 ">To use inbound change sets:</td>

          <td class="slds-cell-wrap" id="changesets__perm_inbound_changesets" style="vertical-align:top;" headers="d13157e76 ">Deploy Change Sets AND Modify Metadata Through
            Metadata API Functions </td>

        </tr>
      </tbody>
    </table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-deploy_sandboxes-264-0-0-production-enus/654e51d1-6795-49fe-bd43-b5385950cf4a/images/icon_note.png)

Note To deploy metadata and configuration simulateneously, use DX Inspector. See [Deploy Metadata and Data from DX Inspector](https://help.salesforce.com/s/articleView?id=platform.code_tools_deploy_metadata_and_data.htm&language=en_US).

When you want to send customizations from your current org to another org, create an outbound change set. After you send the change set, the receiving org sees it as an inbound change set.

Sending a change set between two orgs requires a deployment connection. Change sets can only be sent between orgs that are affiliated with a production org. For example, a production org and a sandbox, or two sandboxes created from the same org can send or receive change sets.

- **[Permission Sets and Profile Settings in Change Sets](https://help.salesforce.com/s/articleView?id=platform.changesets_perm_sets_profiles.htm&release=264.0.0&type=5)**  
    Developers can use permission sets or profile settings to specify permissions and other access settings in a change set. When deciding whether to use permission sets, profile settings, or a combination of both, consider the similarities and differences.
- **[Components Available in Change Sets](https://help.salesforce.com/s/articleView?id=platform.changesets_about_components.htm&release=264.0.0&type=5)**  
    The components available for a change set vary by experience and edition. Also, some components have dependencies on corresponding features.
- **[Restrictions for Approval Processes in Change Sets](https://help.salesforce.com/s/articleView?id=platform.changesets_restrictions_approval_process.htm&release=264.0.0&type=5)**  
    Understand these restrictions before you include approval processes in change sets.
- **[Change Sets Implementation Tips](https://help.salesforce.com/s/articleView?id=platform.changesets_implementation_notes.htm&release=264.0.0&type=5)**  
    Review these tips before you implement your change sets.
- **[Change Sets Best Practices](https://help.salesforce.com/s/articleView?id=platform.changesets_best_practices.htm&release=264.0.0&type=5)**  
    Review these best practices about dependencies, validation, and access settings.
- **[Inbound Change Sets](https://help.salesforce.com/s/articleView?id=platform.changesets_about_inbound.htm&release=264.0.0&type=5)**  
    An inbound change set is a change set that has been sent from another Salesforce org to the org you are logged in to. A change set must be deployed for the changes to take effect. You can deploy the contents of an inbound change set as a whole but not on a component-by-component basis.
- **[Outbound Change Sets](https://help.salesforce.com/s/articleView?id=platform.changesets_about_outbound.htm&release=264.0.0&type=5)**  
    An outbound change set is a change set created in the Salesforce org in which you are logged in and that you want to send to another org. You typically use an outbound change set for customizations created and tested in a sandbox and that are then sent to a production org.

#### See Also

- [Deployment Connections for Change Sets](https://help.salesforce.com/s/articleView?id=platform.changesets_about_connection.htm&release=264.0.0&type=5 "A deployment connection is required between two Salesforce orgs to send change sets from one org to another. You can’t create deployment connections between arbitrary orgs. Instead, you create connections between all orgs affiliated with a production org. For example, if you have a production org and two sandboxes, a deployment connection is created between production and each sandbox. Also, a deployment connection is created between the two sandboxes.")
- [Special Behavior in Deployments](https://help.salesforce.com/s/articleView?id=platform.deploy_special_behavior.htm&release=264.0.0&type=5 "Use the information here to determine what to include in your deployment and how the changes appear in the destination.")
- [Release Management Video: From Sandbox to Production How To Series (Salesforce Classic)](https://salesforce.vidyard.com/watch/yuOAaYF_-vtWigiqXxndVQ)