---
schema_version: "1"
id: fac9c7bfb7e79002840290d434e646a0362733e7f4c5c7537d375a0ceac5ebee
title: Move Standard Messaging Channels from Salesforce Classic to Lightning Experience
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/messaging_transition_to_lex.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.messaging_transition_to_lex.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a397b2901fb773ef3c267d83830d185f979fb7230c789be9f73971b975e4dcbe
description: Messaging in Salesforce Classic depends on the LiveMessage managed package, while Messaging in Lightning Experience uses standard Salesforce objects and features. Learn how to move standard SMS or Facebook Messenger channels to Lightning Experience before upgrading them to enhanced channels.
products:
  - Service Cloud
  - Digital Engagement
release: "264"
---
# Move Standard Messaging Channels from Salesforce Classic to Lightning Experience

Messaging in Salesforce Classic depends on the LiveMessage managed package, while Messaging in Lightning Experience uses standard Salesforce objects and features. Learn how to move standard SMS or Facebook Messenger channels to Lightning Experience before upgrading them to enhanced channels.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <tbody>
          <tr class="">
            <td class="slds-cell-wrap" colspan="2" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=service.messaging_editions.htm&amp;type=5&amp;language=en_US" target="_blank">View supported editions.</a></td>

          </tr>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;">
              <a name="messaging_transition_to_lex__d654e1121"><!-- --></a><span style="vertical-align:text-bottom;display:inline-block;"><img style="margin-bottom:0;" id="messaging_transition_to_lex__d654e1121" src="https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_channels-264-0-0-production-enus/f3c4b3d2-ff86-4f7c-9fe2-3d8b23d35109/resources-global/_corporate/images/checkmark.png" alt="Checkmark"></span>
              <strong>This article applies to:</strong>
            </td>

            <td class="slds-cell-wrap" style="vertical-align:top;">Standard SMS channels</td>

          </tr>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;">
              <span style="vertical-align:text-bottom;display:inline-block;"><img style="margin-bottom:0;" src="https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_channels-264-0-0-production-enus/f3c4b3d2-ff86-4f7c-9fe2-3d8b23d35109/resources-global/_corporate/images/crossmark.png" alt="X icon"></span>
              <strong>This article doesn’t apply to:</strong>
            </td>

            <td class="slds-cell-wrap" style="vertical-align:top;">Enhanced In-App Chat, Enhanced Web Chat v1, Enhanced Web Chat v2, Enhanced
              WhatsApp, Enhanced Facebook Messenger, Enhanced SMS, Enhanced Apple Messages for
              Business, Enhanced LINE, and Bring Your Own Channel</td>

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

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_channels-264-0-0-production-enus/f3c4b3d2-ff86-4f7c-9fe2-3d8b23d35109/images/icon_important.png)

Important LiveMessage in Salesforce Classic and Digital Engagement in Lightning Experience can’t run concurrently in the same production org. We recommended testing a complete sandbox implementation of Messaging in Lightning Experience before you complete the transition.

1. Get Digital Engagement.
    1. To access Messaging in Lightning Experience, purchase the Digital Engagement add-on. Contact your Salesforce account executive to learn more.
    2. Log into your production org to verify that Digital Engagement has been added. From Setup, enter Company Information in the Quick Find box, and select **Company Information**. Verify that the Messaging and Service Cloud User licenses are listed and reflect the total number of licenses that you purchased.
2. (Optional) Set up Messaging in a sandbox org. For help, see [Test Your SMS Channel](https://help.salesforce.com/s/articleView?id=service.messaging_test_sms.htm&release=264.0.0&type=5 "Test your new short code or long code Messaging channel to ensure that it’s working the way you expect. Using a sandbox is optional, but a good idea.") and [Test Your Facebook Messenger Channel](https://help.salesforce.com/s/articleView?id=service.livemessage_test_channels.htm&release=264.0.0&type=5 "Test your Facebook Messenger channel to ensure that it’s working the way you expect. Using a sandbox is optional, but a good idea.").
3. Set up messaging permissions and turn on Messaging. For help, see [Get Started with Messaging](https://help.salesforce.com/s/articleView?id=service.messaging_prepare.htm&release=264.0.0&type=5 "Ready to set up a Messaging channel in Salesforce? First, turn on Messaging in Setup and give service reps and supervisors access. Then, configure your routing preferences and add Messaging to the Service Console.").
4. File a case in [Salesforce Help](https://help.salesforce.com) to migrate your messaging channels from Salesforce Classic to Lightning Experience.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_channels-264-0-0-production-enus/f3c4b3d2-ff86-4f7c-9fe2-3d8b23d35109/images/icon_note.png)
    
    Note Filing a case simply lays the groundwork for the migration; it doesn't automatically switch your implementation to Lightning.
    
    Include this information in your case:
    
    - Topic: Agentforce Service
    - Category: Messaging
    - Subject: Lightning Migration for <Organization Name>
    - Org ID of the org that you want to migrate to Lightning Experience
    - (For SMS channels) Every phone number (long code and short code) that you want to migrate. Indicate whether you want to seek exceptions or enable more numbers.
    
    Salesforce sets up your phone numbers in Lightning Experience within 72 business hours. We'll give you information about the next steps.
    
    After you file your case, continue preparing your Messaging configuration in Lightning Experience (steps 5 and 6) while you wait for your channels to be migrated. When your case is closed, your phone numbers appear on the Messaging Settings page in Lightning Experience, but messages continue to be routed through Salesforce Classic. When you're ready to switch to Lightning Experience routing, move on to step 7.
5. Create your channels.
6. Configure routing in Omni-Channel. Skip this step if you currently use Omni-Channel for LiveMessage. But if you use the LiveMessage widget to monitor your queues, you must set up Omni-Channel.
    
    1. Follow the instructions in [Omni-Channel for Administrators](https://help.salesforce.com/articleView?id=service_presence_intro.htm&language=en_US). Assign the Messaging Session object to your queue.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_channels-264-0-0-production-enus/f3c4b3d2-ff86-4f7c-9fe2-3d8b23d35109/images/icon_note.png)
    
    Note The LiveMessage session (Installed Package: LiveMessage for Salesforce) object is a remnant of Classic LiveMessage. You can ignore it.
7. Convert your automated triggered messages to messaging notifications. For instructions, see [Set Up Automatic Message Notifications](https://help.salesforce.com/articleView?id=livemessage_automatic_message_notifications.htm&language=en_US).
8. Copy or document any processes and data that reference classic LiveMessage’s custom objects. While this step isn't required, the information can be useful. After messaging traffic is cut over and your classic LiveMessage licenses expire, access to its custom objects, data, and associated processes is blocked.
9. ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_channels-264-0-0-production-enus/f3c4b3d2-ff86-4f7c-9fe2-3d8b23d35109/images/icon_important.png)
    
    Important Everything beyond this point can affect your service. Proceed only when you’re ready to fully migrate to Messaging in Lightning Experience.
    
    File a new case in [Salesforce Help](https://help.salesforce.com) to switch SMS traffic from classic LiveMessage to Messaging in Lightning Experience.
    
    Include this information in your case:
    
    - Topic: Service Cloud
    - Category: Messaging
    - Subject: Lightning Migration for <Organization Name>
    - Org ID of the org that you want to migrate. Specify that you must schedule the cutover of your numbers from classic LiveMessage to Lightning Experience.
    - Every phone number that you want to migrate, including long code and short code numbers. Indicate whether you plan to seek exceptions or want to enable more numbers.
    
    When your case is accepted, a service rep offers you a few time slot options for the conversion. When the conversion occurs during your scheduled time slot, messaging traffic moves to your new Lightning Omni-Channel queue. It can take up to 4 hours for carriers to accept the traffic routing updates. In the meantime, check both consoles for message delivery.
10. Migrate your Facebook channels.
    1. If your Facebook channel is live in Salesforce Classic, remove the association between your Facebook page and the LiveMessage app.
        
        1. Log in to Facebook.
        2. Select the Facebook page that you want to migrate.
        3. Navigate to the page setup screen and remove the Facebook page from the LiveMessage app.
    2. Associate your Facebook page with your Lightning org. For help, see [Create a Facebook Messenger Channel](https://help.salesforce.com/s/articleView?id=service.livemessage_setup_facebook_messenger_channels.htm&release=264.0.0&type=5 "Let customers get help from your business using Facebook Messenger. Customers send messages to your Facebook page, and service reps reply from the Service Console. To control how incoming messages are routed, link an Omni-Channel flow or routing configuration to your Facebook Messenger channel.").
11. Change your Omni-Channel configuration. If you already use Omni-Channel in Salesforce Classic, update your queue configurations and swap out LiveMessage Session (Installed Package: LiveMessage for Salesforce) for Messaging Session. Omni-Channel doesn't work properly if you have both Salesforce Classic and Lightning Experience configured to use it.

#### See Also

- [Compare Messaging Channel Capabilities](https://help.salesforce.com/s/articleView?id=service.livemessage_managed_package_lex_differences.htm&release=264.0.0&type=5 "Explore the capabilities of Messaging channels in Agentforce Service (formerly Service Cloud).")
- [What’s Messaging?](https://help.salesforce.com/s/articleView?id=service.messaging_introduction.htm&release=264.0.0&type=5 "Seventy-five percent of adults want to communicate with brands the same way they do friends and family—through messaging. Messaging in Agentforce Service (formerly Service Cloud) provides a rich, efficient conversation experience for customers, service reps, and supervisors.")