Using Plesk Migrator to move data between 123 Reg Virtual Private Servers
This article will show you how to use the Plesk Migrator to move data between our Virtual Private Servers.
The Plesk Migrator in the Plesk Panel offers a quick and easy way of moving your data from one Plesk Panel Service to another, such as migrating from our previous generation of VPS to our current generation of VPS. Simply follow the instructions below to get started:
Start by logging in to Plesk as the Admin user on your new 123 Reg VPS service (i.e. the destination server).
From there, select Server Management within the left-hand menu and then choose Extensions from the list of options that appear.
On the next page, click Plesk Migrator, followed by Start a New Migration.
You will now need to select the hosting panel installed on your old 123 Reg VPS service (i.e. the source server) by choosing one of the provided options.
Once you’ve done this, you’ll need to enter the IP address for the source server into the provided field.
If you’re migrating from a Linux-based server, you’ll need to specify the SSH port (22 by default) as well as the login and password for the root user on the source server.
If you’re migrating from a Windows-based server, you’ll need to specify the method for installing the RPC agent (an application that enables Plesk Migrator to gather data):
- Automatic (recommended): Plesk Migrator will try to deploy and start the RPC agent on the source server using the built-in administrator account. In some cases, automatic deployment may fail (for example, due to firewall settings or because the File and Printer Sharing or RPC services are disabled). If this happens, you will need to deploy the agent manually.
- Manual: A link to download the RPC agent package will be provided. Download the package and manually install the agent on the source server.
Once you’ve done this, click Prepare Migration.
Plesk Migrator will then attempt to fetch data for all the different objects on the source server, such as domains, subscriptions, customer/reseller accounts and hosting plans.
After a few moments, you will be taken to the ‘List of subscriptions’ tab.
Here you must select which subscriptions you want to be migrated to the new VPS service by using one of four available filters.
Please note: you cannot migrate individual domains. The fewest number of objects you can migrate is a single subscription and all of its domains.
By default, Plesk also migrates additional content such as email messages, website files, database tables, and external IDs. If you don’t want to migrate any of these details, clear the corresponding checkboxes.
If you want to change the migration settings, click Settings in the upper-right corner and you’ll be given several options.
Once you’re satisfied with the list of subscriptions to migrate and the migration options, click Migrate to proceed.
Pre-migration checks will now start, which will look for any potential issues and display a report. Should any issues be detected, such as missing modules, we advise you to fix them before continuing with the migration.
After you’ve made the necessary configuration changes, click Refresh to re-run the tests until you have a clean result.
Once you have a clean result on your pre-migration checks, click Start migration to begin the migration process.
You can monitor its progress on the ‘Overview’ tab.
As each subscription is migrated, status reports will be displayed, stating whether that subscription’s migration failed or was successful.
After the migration is finished, you can perform an additional sync of a subscription’s content by clicking Re-sync next to the subscription’s name. If, however, you want to migrate additional subscriptions from your source server, return to step 6.
Otherwise, unless you plan to migrate from the same source server again in the near future, click Finish migration to remove the source server from the list of ongoing migrations.
