Skip to Content
Browse documentation

Command-line Migration Tools

Use additional cPanel and DirectAdmin backup converters, understand their output and prepare a separate restore on Eenos.

These standalone tools convert supported source account data into Eenos-format backups. They can run separately from an installed Eenos panel. Conversion does not restore the account on the destination or switch DNS.

SourcePackageEquivalent command namesGuide
cPanelcptoeenoscptoeenos, cp2eenoscPanel converter
DirectAdmindatoeenosdatoeenos, da2eenosDirectAdmin converter

Each tool supports live full-account conversion, one live account, live package conversion and supported backup-file conversion. Live operations require the corresponding source panel; backup-file conversion works from the supplied archive.

Safe working layout

Use a supported Python environment compatible with the chosen package release and its dependencies. The reviewed source declares Python 3.6 or later, but that declaration alone does not establish compatibility with current dependency releases. Check the installed tool's --help before running it.

Create fresh, private work and output directories before conversion. Use absolute paths without spaces or shell metacharacters: some current extraction and hook commands are assembled as shell strings. Do not run simultaneous conversions sharing a work or output directory.

Protect earlier output

Conversion can replace matching archive names. Package conversion recreates the output EenosHostingPackages directory. Keep previous results elsewhere and use a fresh output directory for each run.

Common operation rules

Choose exactly one operation: --full, --user, --backupfile or --packages. Always supply an existing --saveto directory. Supply an existing --workdir directory to control extraction storage; otherwise the tool uses the invoking user's home as its base.

Start with a foreground conversion of one representative account or copied backup. Inspect logs, output archives and a test restore. Do not rely solely on the process exit status to establish successful conversion of every component.

After conversion, securely transfer the output to the destination, restore it and verify services. Current DNSv2 converter output requires a compatible Eenos destination, documented as 5.0.1 or later. This section intentionally excludes historical tool changelogs.