Start a conversation

Unable to export Content Library to a new environment

Overview

You are migrating your DNN instance to a new environment and have been successful in moving everything over except the Content Library, as when you try to import its contents to the new Library it only imports a partial number of files (e.g. 1,220 files in the new library vs. 2,959 items in the original library). Despite repeating the process multiple times, the new library always stops at the same partial export of files.

Solution

This issue could be caused by the import process timing out unexpectedly. The solution is to have a migration of your Liquid Content done by the Infrastructure team.

Please open a support ticket informing the Tenant IDs for both the old instance (source) and the new instance (destination) - both of which can be found performing the instructions in the Finding your Microservices Tenant ID article.

It is recommended to create a backup of Liquid Content before attempting the migration. 

Important: this process is a 1:1 database copy of the content and will overwrite any existing content that currently resides in the destination target. It is important to confirm with the customer that the content in the target will be overwritten once this process is completed, and also to recommend the customer to backup Liquid Content as stated above.

 Testing

Once the Support Agent confirms the migration of your content, log into the target environment as a SuperUser and navigate to Content > Content Library. You should be able to see the migrated Liquid Content from the source environment.

 

Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted a month ago
  3. Updated a month ago

Comments