---
schema_version: "1"
id: 6929a951d348f5cfacf36fc739258ac382020e78590f74398d5c6f11be747ef8
title: Work with Enhanced CMS Content in the Translation Lifecycle
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/cms_translation_lifecycle.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.cms_translation_lifecycle.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 94a2e7a64be83b7d0e6808372eab3fe50213755d38aa193296f77fb6dfbbf900
description: When your enhanced CMS workspace is set up with multiple languages, you can offer translated content and manage all versions of your content from your enhanced CMS workspace. Identify content to be translated, export it for your localization partner, import the translated content, and publish it to CMS channels.
products:
  - Salesforce CMS
  - Cross Cloud
release: "264"
---
# Work with Enhanced CMS Content in the Translation Lifecycle

When your enhanced CMS workspace is set up with multiple languages, you can offer translated content and manage all versions of your content from your enhanced CMS workspace. Identify content to be translated, export it for your localization partner, import the translated content, and publish it to CMS channels.

### 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: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</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="d5824e66">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d5824e66 ">To export and import content in a CMS workspace:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d5824e66 ">A CMS workspace contributor role of content admin or content manager</td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d5824e66 ">To export and import content with taxonomy tags in an enhanced CMS
              workspace:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d5824e66 ">
              <p>A CMS workspace contributor role of content admin or content
                manager</p>
              <p>AND</p>
              <p style="margin-bottom:0;">View Content Taxonomy</p>
            </td>

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

Managed content and variants of managed content items are counted as one content record. For example, a managed content item with three translations is counted as one record against your license.

The translation lifecycle for content in a CMS workspace is different from the lifecycle for content in an enhanced CMS workspace. When you import translated content to an enhanced CMS workspace, language variants are created for each translation language.

For example, a managed content item is of content type News and a default language of English. When you translate the News content into other languages such as Spanish, Japanese, and French, a managed content variant for each language is created.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-communities_managed_content-264-0-0-production-enus/8b149fc1-875c-4018-8e9e-2843a2196457/images/icon_note.png)

Note You can't export and import translations across different orgs. To add translations to the target org, you can export the content from the target org, translate it, and then import the translated content back into the target org. Or, you can translate the content in the source org, export the content with the translation, and then import the content with the translation into the target org.

1. In Lightning Experience, from the App Launcher, open the Digital Experiences app (previously named Salesforce CMS).
2. Identify content to export for translation.
    1. In an enhanced CMS workspace, select one or more content items.
3. Export content for translation from the enhanced CMS workspace.
    1. In an enhanced CMS workspace, click **Manage** | **Export**.
    2. Select languages from the Available Languages column and use the arrows to add or remove them from the Languages to Export column. Click **Export**.
        
        The selected content is exported to a separate .xlf file for each enhanced CMS workspace language. Depending on the amount of content that you export, the process can take time to finish. You receive a notification email with a link to download a .zip archive of the .xlf files.
    3. Send the downloaded files to your localization service.
4. Import translated content to an enhanced CMS workspace.
    1. Take the .xlf file from your localization service and create a .zip archive. Keep the .zip archive locally available.
    2. In the enhanced CMS workspace, click **Manage** | **Import**.
    3. Use the file selector to navigate to the .zip archive and select your file.
        
        A confirmation message notifies you when the import is in process. After the import is complete and the content variants are added to your workspace in Draft status, you receive a confirmation email.
5. View and manage your translated content in an enhanced CMS workspace.
    1. In an enhanced CMS workspace, locate your managed content.
    2. To view translated content variants, click the content title. From Content Variant Details, select the translated variant from the Languages dropdown menu.
    3. After you review the content variants and everything is ready, publish the managed content.
        
        The managed content and the content variants publish at the same time. If you publish a content variant, the managed content in the workspace’s default language publishes too, but other variants remain in their current status.
    4. To unpublish the content variants, unpublish the managed content. The content variants return to Draft status.
    5. To delete a content variant, delete the managed content.