---
schema_version: "1"
id: 2497a8390ba7e2065d67fe309a42a956469a976ac96640c75cd8383fa8ee6f21
title: Migrate Published Content to a Different Content Collection
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/mth_content_collections_migrate.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.mth_content_collections_migrate.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: e94519cd1b16a6ae1cf0f1c2dfea585c0c28d3135691cc1adac2389e613792d9
description: You can move your company’s existing learning content from one content collection to another. For example, maybe your company previously published content under your enablement site’s single namespace before multiple content collections became available. And now, you want to move content to a content collection for a specific audience.
products:
  - Sales Cloud
  - Sales Enablement
release: "264"
---
# Migrate Published Content to a Different Content Collection

You can move your company’s existing learning content from one content collection to another. For example, maybe your company previously published content under your enablement site’s single namespace before multiple content collections became available. And now, you want to move content to a content collection for a specific audience.

### 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: <strong>Enterprise</strong>, <strong>Performance</strong>, and <strong>Unlimited</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="d2366e63">User Roles and Permissions</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Roles and Permissions" class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e63 ">
              <strong>Enablement Site User Roles</strong>
            </td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e63 ">&nbsp;</td>

          </tr>
          <tr class="">
            <td data-label="User Roles and Permissions" class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e63 ">This topic supports these enablement site roles:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e63 ">
              <ul>
                <li>Salesforce Admins</li>

                <li>Release Managers</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="User Roles and Permissions" class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e63 ">
              <strong>Required System Permissions</strong>
            </td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e63 ">&nbsp;</td>

          </tr>
          <tr class="">
            <td data-label="User Roles and Permissions" class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e63 ">To access the Content Permissions Assistant page in Setup:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e63 ">View Setup and Configuration</td>

          </tr>
          <tr class="">
            <td data-label="User Roles and Permissions" class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e63 ">To create, edit, or delete content collections:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e63 ">Manage Content Collections</td>

          </tr>
          <tr class="">
            <td data-label="User Roles and Permissions" class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e63 ">To create or edit permission sets:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e63 ">Manage Profiles and Permission Sets</td>

          </tr>
          <tr class="">
            <td data-label="User Roles and Permissions" class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e63 ">To assign permission sets:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e63 ">
              <p>Assign Permission Sets</p>
              <p>AND</p>
              <p style="margin-bottom:0;">View Setup and Configuration</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="User Roles and Permissions" class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e63 ">To create and manage releases with Trailmaker Release:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e63 ">Manage Releases</td>

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

To migrate content to a different content collection, you publish two releases:

- One release to archive the existing content in the old content collection
- One release to republish the content in a new content collection

Moving content to a new content collection affects your learning experience in a few ways. We recommend that you carefully evaluate the impact of these considerations before you move any content.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:25%">
          <col style="width:75%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d2366e193">Consideration</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d2366e196">Details</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Consideration" class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e193 ">API Name</td>

            <td data-label="Details" class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e196 ">
              <p>Archived content remains associated with the old content collection and doesn’t
                transfer to the new content collection. When you republish the content, specify a new API
                name.</p>
              <p style="margin-bottom:0;">API names for content must be globally unique, so Trailmaker prevents you from
                adding content that reuses an API name to an unpublished release. Because the republished
                content's API name is new, and the content belongs to a new content collection, its URL is
                different. For more information about API names in URLs, see <a href="https://help.salesforce.com/s/articleView?id=sales.mth_api_names_on_mytrailhead.htm&amp;release=264.0.0&amp;type=5" title="Each content collection, release, trail, module, and unit on your enablement site has its own API name, which is a globally unique ID that references a content path in URLs.">API Names for Trails, Modules, and Units</a>.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Consideration" class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e193 ">URL</td>

            <td data-label="Details" class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e196 ">The archived content’s URL is no longer accessible, and the browser returns an error
              for learners who try to access it. Archived content isn’t automatically redirected to the
              new content collection URL.</td>

          </tr>
          <tr class="">
            <td data-label="Consideration" class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e193 ">References</td>

            <td data-label="Details" class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e196 ">
              <p>Because the migrated content uses a different URL, update any references to that
                content that still use the archived URL, such as:</p>
              <ul>
                <li>Trailmixes</li>
                <li>Resources in Salesforce, such as Learning Paths, in-app guidance, or automated
                  processes</li>
                <li>Your custom support resources, such as email templates or help articles</li>
              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Consideration" class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e193 ">Reports</td>

            <td data-label="Details" class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e196 ">If you install the Trail Tracker app for reporting on module completion, archived
              content is still included in your reports. To start reporting on content moved to a new
              content collection, update your reports and dashboards to include the new content.</td>

          </tr>
          <tr class="">
            <td data-label="Consideration" class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e193 ">Points and badges</td>

            <td data-label="Details" class="slds-cell-wrap" style="vertical-align:top;" headers="d2366e196 ">
              <p>If a learner earned points or badges from content that becomes archived, those points
                and badges remain attached to the learner’s profile, even after the archive operation is
                complete. If a learner completes the republished content in the new content collection,
                those points and badges are new, and get added to the learner’s profile.</p>
              <p style="margin-bottom:0;">If a learner
                loses access to the old content collection, they no longer see earned points or badges from
                that content collection on their profile. But, the learner didn’t actually lose those
                points or badges—they only lost permission to access the content that’s used to
                calculate their profile data. Other users can still see those completed points and badges
                on the learner’s profile—but only if those users still have access to the old
                content collection.</p>
            </td>

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

We also recommend that you review other [considerations for getting started with content collections](https://help.salesforce.com/s/articleView?id=sales.mth_content_permissions_considerations.htm&release=264.0.0&type=5 "Content collections provide flexibility for your company’s learning experience, but they also introduce complexity forenablement sites that have published content. If your company already has an enablement site, you can expand your learning experience by using content collections.").

1. In Salesforce, create the content collection that you want to migrate existing content to, and create a permission set that enables access to the content collection.
2. In Trailmaker Release, prepare a release that archives the existing content, and then publish the release.
3. In Trailmaker Release, prepare another release that republishes the content with the new content collection.
4. In Salesforce, add the appropriate users to the content collection’s permission set.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-mytrailhead-264-0-0-production-enus/0d6bc03d-58c7-47e8-89c9-5e00c98b5485/images/icon_note.png)

Note We recommend that you grant users access to specific content collections through their permission sets and disable the View All Content permission.

#### See Also

- [API Names for Trails, Modules, and Units](https://help.salesforce.com/s/articleView?id=sales.mth_api_names_on_mytrailhead.htm&release=264.0.0&type=5 "Each content collection, release, trail, module, and unit on your enablement site has its own API name, which is a globally unique ID that references a content path in URLs.")
- [Allow Learners to Access Enablement Site Content Collections](https://help.salesforce.com/s/articleView?id=sales.mth_content_permissions.htm&release=264.0.0&type=5 "Ensure that learners can access only the trails and modules that are relevant to their disciplines or job requirements. Create content collections for your different audiences, and then use permission sets to enable access to specific content collections. Only learners with permission to access a particular content collection can view and complete the trails and modules included in the collection.")
- [Considerations for Getting Started with Content Collections](https://help.salesforce.com/s/articleView?id=sales.mth_content_permissions_considerations.htm&release=264.0.0&type=5 "Content collections provide flexibility for your company’s learning experience, but they also introduce complexity forenablement sites that have published content. If your company already has an enablement site, you can expand your learning experience by using content collections.")
- [Examples of Content Collections](https://help.salesforce.com/s/articleView?id=sales.mth_content_collections_examples.htm&release=264.0.0&type=5 "Each company’s learning experience is different and supports unique groups of learners and a broad range of training and enablement requirements. Content collections can be simple or complex, depending on the size and learning requirements of your company. To help you generate ideas for fulfilling your company’s specific content strategy, explore examples of suggested content collection scenarios.")
- [Add Content to a Release from Trailmaker Content](https://help.salesforce.com/s/articleView?id=sales.mth_add_content_to_release_from_tm_content.htm&release=264.0.0&type=5 "After you create your module and quizzes and assign all the necessary metadata, add the content to a release.")
- [Archive Content with Trailmaker Release](https://help.salesforce.com/s/articleView?id=sales.mth_archive_content_with_tm_release.htm&release=264.0.0&type=5 "You can remove published content from your enablement site by archiving it, which hides the content from learners but doesn’t delete it. You can later restore archived content.")
- [Manage Releases with the Trailmaker Release App](https://help.salesforce.com/s/articleView?id=sales.mth_use_trailmaker_to_manage_releases.htm&release=264.0.0&type=5 "Prepare, preview, and publish new or changed content for your enablement site with the Trailmaker Release app. You can also update, archive, and restore content.")