Migration Guide

WordPress Migration Guide

This guide explains how to migrate an existing WordPress website to Virtuozzo Application Management using a pre-configured WordPress package from Marketplace and the Migrate Guru plugin.

!

Galera Cluster requirement

If you plan to migrate to a WordPress installation that uses a Galera database cluster, make sure every database table has an explicit primary key, either single-column or multi-column. Otherwise, replication can fail.

Create the Destination WordPress Environment

1

Create WordPress from Marketplace

Open the Virtuozzo Application Management dashboard and create a new WordPress environment from Marketplace. The destination can be either a standalone WordPress installation or a clustered WordPress solution.

2

Install Migrate Guru on the destination site

After the environment is created, open the WordPress admin panel and install the Migrate Guru plugin.

Generate the Migration Key

3

Activate Migrate Guru

Activate the plugin on the destination WordPress site and open its tab. Copy the displayed Migration Key. You will use this key from the source WordPress site.

Prepare the Source WordPress Site

4

Install Migrate Guru on the source site

Log in to the WordPress website you want to migrate. Install and activate the same Migrate Guru plugin.

Open the plugin tab, provide your email address, accept the terms of service, and click Migrate to continue.

Recommended before migration

Create a complete backup of the source WordPress site before starting the migration.

Start Migration with the Migration Key

5

Select Other Hosts

On the migration page, choose Other Hosts and provide the Migration Key copied from the destination WordPress environment.

Adjust any other required settings and start the migration.

Alternative: Manually Input Host Details

Instead of using the Migration Key, you can switch to Manually Input Host Details. This method requires a public SSH key to be added to the platform.

Destination Site URLThe URL of the new WordPress site. It can be a custom domain or the default domain provided after the environment is created.
ProtocolSelect SFTP to use secure file transfer.
Destination Server IP / FTP AddressCopy the Host value from the platform’s SSH access settings.
PortCopy the Port value from the same SSH access section.
FTP UsernameUse the automatically generated username shown in the SFTP / Direct SSH Access section.
SSH KeyUse the private key associated with the public key that has been added to the platform.
Directory PathUse the WordPress installation path: /var/www/webroot/ROOT/.

To find the SFTP connection details, open the account or environment settings, go to the SSH section, switch to SFTP / Direct SSH Access, and select the WordPress application-server node.

i

SSH key detail

The Migrate Guru form requires the private key that corresponds to the public key registered on the platform.

After all fields are complete, click Migrate.

Complete and Verify Migration

6

Monitor the migration

Migrate Guru handles both website files and the WordPress database automatically. Migration progress is shown on the plugin page.

7

Check the success result

When the process completes, the plugin displays a success message and sends an email notification containing the migration details.

8

Verify the migrated WordPress site

Open the newly migrated site on Virtuozzo Application Management and check that the website works as expected.

Expected Result

The existing WordPress website is copied to the new Virtuozzo Application Management WordPress environment, including both site files and database content. The migrated site is then available at the destination URL for verification.

Important Notes

  • The source workflow uses the Migrate Guru plugin.
  • The preferred workflow uses a Migration Key generated on the destination site.
  • The alternative manual workflow uses SFTP and SSH-key authentication.
  • The documented WordPress application directory is /var/www/webroot/ROOT/.
  • Create a full backup of the source site before migration.
  • For Galera-based WordPress, all database tables must have explicit primary keys.
  • After migration, verify the destination site before relying on it in production.