If you are migrating your site from one DNN instance to another, both your local and Microservices data need to be moved. Microservices data is stored on DNN's cloud platform and linked to your instance with your Tenant ID. There are two types of Microservice data that need to be redirected: Liquid Content, and Form Builder. To link your Microservice data with your new instance, you have a few options:
- To move Liquid Content only:
- You can Export your Liquid Content from your old instance and import it into the new instance. This is the fastest and easiest method of transitioning your content if you do not need Form Builder content migrated.
- Request a Tenant Migration from DNN support. This is generally only needed if the Export/Import process fails.
- To move Liquid Content and Form Builder
- Set up your new instance so that it has the same Tenant ID as the old instance. This doesn't move your Microservices data, but rather points your new instance at the same cloud storage location as the old.
- Request a Tenant Migration from DNN support.
This article covers the information our support team will need to perform the Tenant Migration process.
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 already present in your new instance, you can create a backup of Liquid Content which can later be imported to your new environment after the Tenant Migration
To request a tenant migration from our support team:
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.
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
Once the ticket has been created, the Support team will perform the migration.
Once you received confirmation from the support team that the migration has been completed you can test it by doing the following:
- You must login to the target environment as a SuperUser
- Go to Content > Content Library.
- You should be able to see the migrated Liquid Content from the source environment.