Migrating to DXP Cloud¶
- Stage 1: Matching DXP Versions
- Stage 2: Creating Data Backup Files
- Stage 3: Uploading and Restoring the Data Backup
- Stage 4: Migrating DXP Configurations and Customizations
- Stage 5: Migrating Web Server Configurations
- Stage 6: Migrating Search Configurations
- Stage 7: Connecting the VPN
- Stage 8: Next Steps After Migration
Liferay DXP Cloud is a secure and reliable enterprise platform built for high availablity, scalability, and performance. Running a Liferay DXP instance on DXP Cloud provides you with features to ensure a safe, reliable, and smooth experience for your users.
Migrating to DXP Cloud from an on-premises Liferay DXP environment requires moving your entire instance into an environment running on DXP Cloud, including all of your data (in documents or the database), configurations, and customizations (such as OSGi modules or plugins). This also involves working with and deploying changes with a Git repository that integrates with your DXP Cloud environment(s).
Here are the main stages of migration to DXP Cloud:
Why Should I Migrate to DXP Cloud?¶
Migrating to DXP Cloud allows you to take advantage of its high availability and scalability with quick-to-deploy features like clustering, load balancing, and auto-scaling out-of-the-box. Built-in integration with Git and Jenkins also streamlines your development process. This makes your production instance easier to deploy and develop with, more flexible for your needs, and more reliable for your users.
What Do I Need to Prepare in Advance?¶
You can take several measures to prepare for the migration in advance, including planning and setting up your project repository and required tools ahead of time.
The first important task to perform to prepare for the migration is to plan ahead and reserve the time for it. Work with your database administrator to arrange a time to make the transition once the migration steps are complete, as well as a window to freeze your data for the second stage of migration (creating backup files for your database and document library).
Review the steps of the migration ahead of time so that you have an idea of what to expect and how long the migration may take for you to complete.
Install and Learn the Tools¶
You should also ensure that you have the necessary tools on your local system for the migration steps:
Git: You must have Git installed so that you can use it to commit and push your changes to DXP Cloud throughout the migration.
The Liferay Patching Tool: You need the Patching Tool to confirm your patching and hotfix information for the first stage of the migration.
File compression software: If you are using Windows as your local system’s OS, then you also need file compression software (such as 7-Zip) to pack/unpack compressed files.
Once you have these tools installed, you may want to take some time to familiarize yourself with them.
For instance, if you are new to Git, then you may want to see the official Git materials (including reference documentation, a command cheat sheet, etc.) or practice using it independently before applying it to your migration. Git is a powerful version control tool with capabilities beyond what is used in this migration guide.
Migrating to DXP Cloud also involves moving your own custom code, modules, and themes into a Liferay Workspace specifically for your project. If you are new to Liferay Workspace, then you may also want to learn how to use it effectively here.
Prepare the Environment¶
Prepare your environment for the migration in advance to ensure the migration process starts smoothly.
If you have not already done so, complete the tasks in the Initial Setup Overview to ensure that your DXP Cloud environment is up and running as expected. In case you run into problems during the migration, enable Support Access; enabling Support Access gives Liferay DXP Cloud Support staff more capacity to help if necessary by giving them access to your project’s console, logs, and more.
Set up your repository (using GitHub, Bitbucket, or GitLab) to confirm that you can make deployments. The migration requires deploying multiple changes throughout the process, so you must be able to deploy them to proceed with the migration.