Requesting Liquid Content Copy Tenant migration from DNN Support


This article describes the process of migrating Microservice Content from one instance to another through the Copy Tenant process. This is generally needed if an import/export of Liquid Content fails and migrate the Form Builder data with Liquid Content. A copy tenant can be used if the Content Library content is shown empty in the Persona Bar.



Microservices and Liquid Content are serviced by DNN systems. Therefore, when you need to migrate the content from one instance to another, the Support team needs to work with the Infrastructure team to create a tenant copy.

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 for you to know that the content in the target will be overwritten once this process is completed.

If you do not want to overwrite the Liquid content, you need to create a backup of Liquid Content



  1. The first step is to find the Microservices Tenant ID for both instances. 

    NOTE: Make sure to indicate which tenant ID is tied to the old instance and which is tied to the new instance.
  2. Create a ticket with the Support team (or follow up in the existing one if you already have it) and provide both Microservices Tenant IDs

  3. Once the ticket has been created, the Support team will do the needed actions.



Once you received confirmation from the support team that the migration has been completed you can test it by doing the following:

  1. You must login to the target environment as a SuperUser
  2. Go to Content > Content Library.
  3. You should be able to see the migrated Liquid Content from the source environment.


Related Articles



Please sign in to leave a comment.