---
schema_version: "1"
id: 0616208b8be4f2c9dff612de6016c2ca6fde32a8fff36bc4516590467ad25ac7
title: Deploy Sandbox Changes in Marketing Cloud Next
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mktg_admin_setup_sandbox_deploy_changes.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mktg_admin_setup_sandbox_deploy_changes.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: c55b69a44613933cbec677752b3cf18a6e192553c213436e3a9866c03e678d64
description: After you make changes in a sandbox, deploy those changes back to the production org or to another sandbox by using Salesforce Platform DevOps features.
products:
  - Marketing
release: "264"
---
# Deploy Sandbox Changes in Marketing Cloud Next

After you make changes in a sandbox, deploy those changes back to the production org or to another sandbox by using Salesforce Platform DevOps features.

### Required Editions

[View supported editions](https://help.salesforce.com/s/articleView?id=mktg.mktg_editions.htm&release=264.0.0&type=5 "Marketing Cloud Next is available in Growth and Advanced editions, and requires Salesforce Enterprise or Unlimited editions. Some features are limited by edition or purchased add-on. All functionality is available in Lightning Experience only.").

<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="d83246e52">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d83246e52 ">To create a sandbox:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d83246e52 ">
              <p>Manage Dev Sandboxes (Developer or Developer Pro only)</p>
              <p>OR</p>
              <p style="margin-bottom:0;">Manage
                Sandboxes (all sandbox types)</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d83246e52 ">To deploy <span>Data 360</span> objects:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d83246e52 "><span>Data Cloud Architect</span></td>

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

Some things in the sandbox aren't promoted. The schema, logic, and rules that you create in a sandbox are promoted, but the underlying data isn't. For example, you can promote and reuse the identity resolution rulesets you created, but not the unified individuals themselves. You need to re-create those related records.

Sandboxes don't promote these items:

- Sending and engagement history
- Segment populations or lists
- Ingested data
- Calculated insights, logs, and reporting data
- Campaign records
- Brief records
- Subscription and consent records
- Contact and lead records

Make sure that you deploy components in the right order. Features and assets have internal dependencies that are validated at deployment time. If the dependencies aren't met, the deployment fails. For example, if a flow references a Data 360 object or a content template, that object or template must be deployed before the flow can be deployed.

Always deploy components in this order:

1. Deploy Data 360 objects.
    1. Select these objects for deployment: segments, DMOs, DLOs, identity resolution rulesets, data graphs, data streams, calculated insights, data actions, Personalization Points, recommenders, and engagement signals. See [Deploy Data 360 Changes from a Sandbox](https://help.salesforce.com/s/articleView?id=data.c360_a_data_cloud_sandbox_deploy.htm&language=en_US).
    2. After deploying to the target org, activate or publish the objects.
2. Deploy marketing objects.
    1. In the MarketingObject component, select the marketing objects.
    2. Select **View/Add Dependencies**, then select all the columns that belong to the added MarketingObject.
3. Deploy marketing content.
    1. In the Digital Experience component, select content records, email templates, brand, and images.
    2. In the Digital Experience Bundle component, select the CMS workspace.
        
        Deploy content records to the same CMS workspace in the target org. If the CMS workspace is already available in the target org, skip this step.
    3. After deploying to the target org, publish your content.
4. Deploy marketing flows.
    1. Make sure the flow status is draft.
    2. In the Flow Definition component, select the flow.
    3. After deploying the flow to the target org, activate the flow.

You can use any of these methods to move changes from a sandbox to production or another sandbox.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d83246e256">Method</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d83246e259">resources</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Method" class="slds-cell-wrap" style="vertical-align:top;" headers="d83246e256 ">Change Sets</td>

            <td data-label="resources" class="slds-cell-wrap" style="vertical-align:top;" headers="d83246e259 ">
              <ul>
                <li><a href="https://help.salesforce.com/s/articleView?id=platform.changesets.htm&amp;language=en_US" target="_blank">Change Sets</a></li>

                <li><a href="https://help.salesforce.com/s/articleView?id=platform.deploy_connection_parent.htm&amp;language=en_US" target="_blank">Connect Organizations for
                    Deployment</a></li>

                <li><a href="https://help.salesforce.com/s/articleView?id=platform.changesets_about_outbound.htm&amp;language=en_US" target="_blank">Outbound Change Sets</a></li>

                <li><a href="https://help.salesforce.com/s/articleView?id=platform.changesets_about_inbound.htm&amp;language=en_US" target="_blank">Inbound Change Sets</a></li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Method" class="slds-cell-wrap" style="vertical-align:top;" headers="d83246e256 ">DevOps Center</td>

            <td data-label="resources" class="slds-cell-wrap" style="vertical-align:top;" headers="d83246e259 "><a href="https://help.salesforce.com/s/articleView?id=platform.devops_testing_improve_release_quality_with_devops_testing.htm&amp;language=en_US" target="_blank">Improve Release Quality with DevOps
                Testing</a></td>

          </tr>
          <tr class="">
            <td data-label="Method" class="slds-cell-wrap" style="vertical-align:top;" headers="d83246e256 "> Metadata Retrieve and Deploy</td>

            <td data-label="resources" class="slds-cell-wrap" style="vertical-align:top;" headers="d83246e259 ">
              <ul>
                <li><a href="https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_intro.htm" target="_blank">Understanding Metadata API</a></li>

                <li><a href="https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_file_based_calls_intro.htm" target="_blank">File-Based Calls</a></li>

                <li><a href="https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_digitalexperiencebundle.htm" target="_blank">Digital Experience Bundle</a></li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Method" class="slds-cell-wrap" style="vertical-align:top;" headers="d83246e256 ">CLI Retrieve and Deploy</td>

            <td data-label="resources" class="slds-cell-wrap" style="vertical-align:top;" headers="d83246e259 "><a href="https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_intro.htm" target="_blank">Salesforce CLI Setup Guide</a></td>

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

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mktg_all-264-0-0-production-enus/e92be4e1-4bef-47a5-a11d-95f4ea1f7d7a/images/icon_note.png)

Note After content is deployed to the target org, its status is Draft, even if the status was Active or Published in the source org.