Table of Contents
How to Import Multiple Account
Prerequisites
Last Updated for InterWorx-CP version 3.0
The server must have at least one SiteWorx account on the system.
Purpose
Using NodeWorx’s Mass Transfer interface, administrators can easily migrate multiple InterWorx-CP accounts from one server to another. Additionally, administrators can easily import multiple accounts from a cPanel, Ensim, or Plesk server to an InterWorx-CP server.
Procedure
If you prefer to use the web interface, follow the steps below.
- Click on the menu if it is not already expanded.
- Click on the submenu if it is not already expanded.
- Click on the ◊ Mass Transfer item.
- You should now be looking at the Mass Account Transfer controls in the main content area.
- In the Hostname: field, enter the hostname of the remote server from which you want to migrate.
- In the Root User: field, enter the root user of the remote server from which you want to migrate.
- In the Password: field, enter the password for the root user you entered above.
- Click the button.
- You will now see a list of accounts on the remote server, with a checkbox next to each account.
Note: If the remote server also has InterWorx 3.0 installed, the list of accounts will be grouped by resellers. - Mark the checkboxes next to accounts you would like to migrate.
- Select the destination Reseller you want to use for each migrated account from the Reseller column. If the remote server also has InterWorx 3.0 installed, and the remote reseller doesn’t already exist on the destination server, you will have the option to import the remote reseller. If the reseller in the backup file already exists, the account will automatically be imported under this reseller.
- Select the IP Address you want to use for each migrated account from the IP Address column.
- There are also “Advanced Options” dropdowns at the top of each group of accounts, allowing you to quickly and easily set options for all the accounts in the list. For example, choosing an IP Address in the Advanced Options section will select that IP for all accounts.
- If the remote server also has InterWorx 3.0 installed, there will be a few more options available.
- A Storage Used column will appear, indicating the approximate amount of disk space the account is using on the remote server.
- A Type option will appear for each account, allowing you to choose either a “Full Import” or “Structure-Only Import”. Structure-only imports are much smaller and faster than full imports, but only import SiteWorx account related information (such as quotas, usernames, passwords, etc) and not actual data (such as website data files, database data, and email files). Structure-only is especially useful when mass-transferring large accounts, since large accounts can take a considerable amount of time to mass-transfer.
- Select Import ... from the drop-down list at the bottom of the table.
- You will now see a list of the accounts you chose to mass transfer, along with a status for each account under the Import Status column.
- In Progress - Account is currently being backed up, transferred over from the remote server, and imported into InterWorx-CP.
- Pending - Account is waiting for import process to begin.
- Success - Import of account succeeded.
- Failure - Import of account failed. A message that indicates possible reasons for failure will appear beneath the Failure box.
- The page will automatically reload after a certain interval to update the import status of each account.
- When the mass transfer process is complete, all accounts will either have a Success or Failure status in the Import Status column.
| If you leave this page, the mass account transfers will still continue in the background. However, if you return to this page, you will no longer be able to see the status of any of the accounts. |
Troubleshooting
If you get a Permission Denied error after clicking the button on the first Mass Account Transfer page, check the following:
- You have entered the correct root password.
- You have entered the correct root username.
- Double check that the remote server allows the
rootuser to SSH in. You can verify this by trying to SSH into the remote server as therootuser.
