Versions Compared

Old Version 1

changes.mady.by.user Unknown User (jareds)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (aric)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Include Page
Migrate Accounts from Other Servers to InterWorx
Migrate Accounts from Other Servers to InterWorx

If you have accounts you need to move from Plesk to your server with InterWorx, there are several tools designed to make this process easy.

Tip
If you have an InterWorx server with HostDime, feel free to contact us to help you with your data migration. Our experts will take the hassle out of this process.

Migrate Accounts

The first step is to migrate accounts from another server.

Tip

Migrations must be done by an InterWorx administrator (not a reseller or regular user) and they must have direct root access to the source server if the mass import tool is going to be used. If a single account is going to be imported then root access is not required on the source server, only access to a full unencrypted backup made by the other control panel.

cPanel to Plesk Transfer

Warning

You should be aware of the following limitations for importing accounts from Plesk servers:

  • Only Plesk accounts from Linux servers can be migrated to InterWorx. If the Plesk server is running Windows, then you should create an account on the InterWorx server and manually migrate data instead.
  • InterWorx can only mass migrate accounts from very old versions of Plesk (versions 6-8), so you'll need to import Plesk accounts one-by-one instead following the directions below.
  • InterWorx can only import unencrypted backups.
  • InterWorx doesn't support every feature Plesk does, so Mailman mailing lists, PostgreSQL databases, server-side Java, Ruby on Rails, Docker, and NodeJS will not migrate successfully.
  • InterWorx does not currently support DNSSEC, so if domains in Plesk are using that, it should be disabled at the registrar and in the Plesk account prior to migration.
  • Web stats will not be migrated.
  • Not everything that appears in the home directory for an account on a Plesk server will be migrated to the InterWorx server. Only those items that InterWorx specifically knows it needs will be transferred. So mail and web pages will get moved, but Softaculous or Fantastico script autoinstaller data, as an example, will not.
  • MySQL/MariaDB databases and users will be migrated, but they might need to have their names changed. If this happens, InterWorx will note the change in the migration log as well as put a notice into the migrated account for the user to see. This is important because if a script relies on accessing that database, you'll need to manually update the script configuration file with the new details.
  • InterWorx will read the Plesk subscriptions and service plans and try to replicate those settings as close as possible, but not all limitations or settings may be possible on the InterWorx server.

This is how you migrate Plesk accounts:

  1. Log into your InterWorx server as an administrator.
  2. Make sure you have a valid full Plesk account backup before you begin.
  3. Select Import from the SiteWorx section of the NodeWorx interface.
    Select Import from the SiteWorx Section of the NodeWorx InterfaceImage Removed
  4. Click Import From Plesk from the available options. Although the description only mentions Plesk 9-11, we can confirm it works up to at least 17.8.
    Click the Import From Plesk ButtonImage Removed
  5. You will then be prompted to choose a non-encrypted Plesk backup from your local machine (Browse Files), or you can click Use a file already on the system and type in the full path to the Plesk backup stored on your InterWorx server. Backups over 1 GB should always be uploaded to your local server rather than uploaded through this web form. The path you enter should be a full path, including the initial /. When you are ready, click Continue. The server will upload/decompress the backup in preparation for the next step.
    Click Browse Files to Upload an Unencrypted Backup or Specify the Path to the Backup on the ServerImage Removed
  6.  InterWorx will show you the details for the account it found in the backup and now you will be able to adjust a few settings. At minimum you should check to make sure the InterWorx Reseller (i.e., account owner), the IP Address and Database server are set to what you want that account to use. You may also want to add or update the Client Email so InterWorx knows who to email concerning the account.
    Confirm the Account Ownership and Settings are OK and then Click Continue to Start the Import ProcessImage Removed
  7. Click Continue and InterWorx will start importing the account. Click Cancel to abort this process. When done, InterWorx will inform you of the success or failure.

Post-Migration Investigation

While InterWorx will take care of a lot of data migration tasks, there are still a few things that you or your clients may need to do afterwards. Here are a list of some things you should investigate or change as needed:

  • DNS changes: Your clients may need to update the nameservers that their domains point to or their custom nameserver IP addresses so that they point to your InterWorx server. Several things like mail and the user's website may not work properly until DNS propagation is complete.
  • Check the website: Your clients should check to make sure their website works as expected after the transfer. Don't forget that if the migration changed the name of a database or database user that a web script relies on, that will need to be updated manually in the web script's database configuration file.
  • Try logging into mail: Not only may users need to adjust the mail account connection details in their email clients, but they should also ensure that all mail they expect is in the account and that new mail is arriving.
  • Check other services like FTP to make sure they work as expected, too.
  • You may need to manually copy over some additional data from the source server (like Softaculous or Fantastico information if those things are in use on both servers).
Warning

Do not delete the data from the source server until you are sure the import was successful and everything is working properly.

Congratulations on your successful migration!