Contact Us

Sitecore Content Hub, a solution by Sitecore manages media items allowing you to import and export data between diverse environments. It sits in the middle of all the platforms that you use and can manage both upstream and downstream flow including all the content and assets coming into your organisation from agencies, suppliers, ERPs etc.

Also, it oversees how that content gets distributed to a CMS, CRM, social media channels, or wherever else it needs to go, through a host of out-of-the-box connectors or customised integrations.

The end-to-end transfer has two steps involved. Firstly to export the media asset in a Zip file and then import it to the destination environment. In addition, while transfering you can accumulate the attributes of the assets in a spreadsheet to retain the information.

Advantages of Sitecore Content Hub

  • Accelerated time-to-market
  • Increased reuse of your multichannel assets
  • Increased findability of assets
  • Reduced number of misused assets
  • Reduced digital content production time
  • Improved compliance with privacy and security

Here's how to migrate assets from Sitecore Media Library to Content Hub:

Step 1: Export Sitecore Items in Excel

Run PowerShell Script and get all Sitecore media library items in Excel/CSV format.

medianew

itemlastupdated

Step 2: Create Taxonomy in Content hub Instance

Create Taxonomy/ Option List as per business requirements in Content hub.

taxonomy

Step 3: Update Excel data as per Taxonomy

Update Column name in the exported sheet as per Taxonomy name

more taxonomy

Update all data in excel according to the Taxonomy's value Identifier. For example:

taxonomy management

somedataaftertaxonomy

Also, Rename the Name of Excel sheet (Name should be always "M.Asset")

massest

Step 4: Upload Assets in Content hub through Import Excel

import

Step 5: Install Connector in Sitecore Instance (as per Sitecore version and content hub instance version)

Before installing the Connector Package, you need to add Sitecore url in Content hub Settings.

Go to Manage > Settings > Portal Configuration > CORSConfiguration

See below example:

settings

After Installation of Connector in Sitecore instance, you can see new browser link "Browse Sitecore DAM".

DAM

Step 6: Run PowerShell Script in Sitecore to change the pointing URLs of images / Rich Text

powershellscript

Step 7: Check new URL in Sitecore

Now you can search any Image /PDF /Rich Text item. The URLs should be changed and pointing to Content hub URL.

For Example:

tools

Sitecore Path: /sitecore/content/Global/Components/Rich Text/IND Get Started/Tools and Resources

New URL: https://sele-p-001.sitecorecontenthub.cloud/api/public/content/e9df763864af41ba8ecf6ed2e1f525ea

Old Sitecore URL: https://sitecoreinstance/-/media/sitecore/pdf-documents/individual/1848831_gettingstarted_ind_id.ashx

Conclusion

Multiple instances of migration might be required in a development process. As each software is subject to scale or shift to a new environment as per the situational needs. In the past, migration has been a tricky operation, as either the procedure has been complicated or keeping the data consistent throughout the migration has been contesting.

However, the above mentioned migration can maintain the records and a sequential execution making for a smooth transition. For any Sitecore consultation get in touch with our team.

Need Help?