---
schema_version: "1"
id: 191bc6b226f29b1bcd5eff731a90a9cd076ea5f48284c9beffddb7a14b4e9564
title: Move Enhanced SMS Channel Metadata to Sandbox
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/messaging_move_sms_channel_metadata_sandbox.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.messaging_move_sms_channel_metadata_sandbox.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 882463b3518b608af2057a4954c64de6cbdbd3f99f8c58aa4afedc2370c16381
description: If you have configured enhanced SMS channels, you can move their configurations from a production org to a sandbox org for testing or development, from sandbox to sandbox, or from sandbox to production. These steps apply for enhanced long code, toll-free long code, and short code channels.
products:
  - Service Cloud
  - Digital Engagement
release: "264"
---
# Move Enhanced SMS Channel Metadata to Sandbox

If you have configured enhanced SMS channels, you can move their configurations from a production org to a sandbox org for testing or development, from sandbox to sandbox, or from sandbox to production. These steps apply for enhanced long code, toll-free long code, and short code channels.

To move your SMS channel configurations to the destination org, retrieve the metadata by using a package.xml manifest file. You can then deploy it to the target org. Also, you can either perform a [Sandbox refresh](https://help.salesforce.com/s/articleView?id=platform.data_sandbox_refresh.htm&type=5&language=en_US) or perform Metadata API operations by using a developer tool. The tools can be Salesforce CLI, Salesforce Extensions for VS Code, or browser extensions like Salesforce Bench Press.

For demo purposes, here we’re showing how to move metadata from production to sandbox using the Salesforce Bench Press extension.

For a better user experience, when moving your metadata, make sure that you perform these prerequisites.

- [Set Up Routing for Messaging Channels in Service Cloud](https://help.salesforce.com/s/articleView?id=service.messaging_omnichannel_routing.htm&type=5&language=en_US).
- Make sure that in the destination org, you have a similar routing metadata present.
- Make sure that you deactivate the SMS channel in your source org before you activate it in your destination org and vice versa. An SMS channel can only be active in one org at a time.

## Step 1: Find the Developer Name of Your Enhanced SMS Channel

1. In your source org, from Setup, in the Quick Find box, enter Messaging Settings, and then select **Messaging Settings**.
2. Under the Channels section, locate the specific SMS channel you want to migrate.
3. Click the channel name to view its details.
4. Copy the value in the Developer Name field.

## Step 2: Create the package.xml File

1. Open a plain text editor (like Notepad or VS Code) on your computer.
2. Paste this XML code, replacing YOUR\_DEVELOPER\_NAME with the Developer Name you copied in the previous step.
    
    ```
    <?xml version="1.0" encoding="UTF-8"?>
    <Package xmlns="http://soap.sforce.com/2006/04/metadata">
        <types>
            <members>YOUR_DEVELOPER_NAME</members>
            <name>MessagingChannel</name>
        </types>
        <version>65.0</version>
    </Package>
    ```
3. Save the file to your computer as package.xml.
    
    By specifying the exact Developer Name, your retrieved.zip file from the Salesforce Bench Press extension will only contain the metadata for that single SMS channel. This file ensures a clean and conflict-free deployment to your destination org.

## Step 3: Retrieve the Metadata from Your Production Org

1. Log in to your source org.
2. Open the Salesforce Bench Press extension.
3. Select the **Metadata** tab.
4. On the Retrieve subtab, under Package XML, click **Choose file**, and then select your package.xml file.
5. Click **Retrieve**.
6. To monitor your request, select the **Status** subtab.
7. When the status changes to Succeeded, click **Fetch**.
8. Click **Download**, and then save the ZIP file to your computer.
9. Extract the downloaded ZIP file and make necessary modifications to the SMS channel files for your destination environment. Make sure that the `isoCountryCode` field contains a valid country code. For example, `isoCountryCode=US`.
10. Compress the files into a new deployment ZIP file.

## Step 4: Deploy the Metadata to Your Sandbox Org

1. Log in to your destination org.
2. Open the Salesforce Bench Press extension.
3. Select the **Metadata** tab, and then select the **Deploy** subtab.
4. Under File, click **Choose file**, and then select your deployment ZIP file.
5. Select **Single Package**.
6. Under Testing, select **None**.
7. Click **Deploy**.
8. Select the **Status** subtab, and then click **Update** to refresh the operation status.
9. When the status changes to Succeeded, from Setup, in the Quick Find box, enter Messaging Settings, and then select **Messaging Settings**.
10. Select the SMS channel that you deployed.
11. Click **Activate Channel**.
    
    If an incoming message doesn't create a messaging session, deactivate the SMS channel and reactivate it.