Skip to Content
Browse documentation

cPanel Migration with cptoeenos

Install the cPanel converter, convert live accounts or supported backups, review cp2eenos options and prepare the output for restore.

cptoeenos and cp2eenos are two command names for the same converter. Use it for a separate cPanel backup conversion workflow. For destination-driven live migration, see WAP cPanel import.

Install and check

For live accounts, WHM packages or a whole-server conversion, install the tool on the source cPanel server. To convert an existing backup archive, install it on the Eenos destination or another suitable Linux server.

Use Python 3 and its matching pip installer. The tool declares Python 3.6 or later; the selected release's dependencies must also support your Python version. Run the following installation command from the server shell as root. It includes the Eenos package index, which must not be omitted:

pip3 --no-cache-dir install --extra-index-url https://pip.eenos.com/ cptoeenos

If your Python 3 installer is named pip instead of pip3, use that name with the same arguments. Run only one installation command. The package name is cptoeenos; installation provides both cptoeenos and cp2eenos commands.

Check the installed command and its supported options:

cp2eenos --help

Live conversion needs root access to the cPanel source and its data. Prepare trusted input backups, extraction utilities, capacity and fresh existing work/output directories as described in command-line preparation.

Choose one conversion command

The paths and exampleuser below are placeholders. Create the private directories first and use a fresh output directory per run. Run one example that matches your operation.

Convert a copied cPanel account backup (.tar or .tar.gz):

cp2eenos --backupfile /backup/cpmove-exampleuser.tar.gz --saveto /backup/cp-run-01/output --workdir /backup/cp-run-01/work

Convert one live cPanel account:

cp2eenos --user exampleuser --saveto /backup/cp-run-02/output --workdir /backup/cp-run-02/work

Convert all live accounts and packages:

cp2eenos --full --saveto /backup/cp-run-03/output --workdir /backup/cp-run-03/work

Convert live hosting packages only:

cp2eenos --packages --saveto /backup/cp-run-04/output --workdir /backup/cp-run-04/work

Options

OptionMeaning
-f, --fullConvert all live accounts and packages.
-u, --user USERConvert the specified live source account.
-b, --backupfile PATHConvert a supported account backup.
-p, --packagesConvert live hosting packages.
-s, --saveto DIRRequired existing output directory.
-w, --workdir DIRExisting temporary-work base directory.
--skipmysqlSkip MySQL data conversion.
--skippgsqlSkip PostgreSQL data conversion.
--skiphomedirSkip home-directory data conversion.
--skipemailSkip email data conversion.
--skipresellerconfigSkip reseller configuration conversion.
-d, --demonDetach into background mode; the current option spelling is demon.
-pu, --postupload SCRIPTRun a supplied script after conversion dispatch, passing the output directory.
-h, --helpShow the installed release's options.

Skipped data needs a separate migration plan. A backup created with skip options is not a complete copy of that account.

Logs and output

For root, inspect /var/log/cptoeenos.log; for another user, the log is cptoeenos.log in that user's home. Review conversion errors, unsupported items and the reported backup location. Inspect account archives and the EenosHostingPackages output when applicable.

The current converter maps package-name dots to Dot and whitespace groups to Space; collisions require review. Its current DNSv2 output targets Eenos 5.0.1 or later. DNS records that cannot be converted may be skipped or cause errors; DNSSEC signing material is not transferred as an active signing setup. Verify the destination zone separately. cPanel Mailman 2 mailing lists are not supported by this converter.

Background mode and hooks

Use foreground mode for the first test. Background mode detaches the process; monitor its log and output rather than treating command return as completion.

The post-upload hook receives the output directory, not an individual archive. It may run even when individual conversions failed. Use only a trusted executable script with a simple absolute path, and make the script check which files are valid before uploading. Verify the remote result separately.

Continue with restore and verification.