Updated: 12 November 2026 · Applies to: CloudLinux OS (LVE Manager, CageFS, PHP Selector, MySQL Governor), according to the CloudLinux documentation; not tested by us
To move CloudLinux settings to a new server, install CloudLinux with the same components on the new server, transfer the accounts, then copy the configuration files listed below and apply them: /etc/container/ve.cfg for LVE and package limits (apply with lvectl apply all), the files you changed in /etc/cagefs/ for CageFS (apply with cagefsctl --remount-all), and /etc/cl.selector/ for PHP Selector defaults. Each user's own PHP Selector choices live in their home directory and move with the account.
CloudLinux is licensed software, so we could not test these commands in our lab. The file locations and commands below are taken from the CloudLinux documentation.
Before you start
- Install CloudLinux on the new server and activate its licence (see How to Check and Update a CloudLinux License Key).
- Install the same components you use on the old server: LVE Manager, CageFS, the alt-php versions for PHP Selector and, if you use it, MySQL Governor.
- Take a backup of the files listed below on both servers, so you can roll back.
- Transfer the hosting accounts first (on cPanel with WHM › Transfers › Transfer Tool). The limits refer to users and packages, so those must exist on the new server.
1. LVE limits and package limits
According to CloudLinux, all LVE limits are saved in /etc/container/ve.cfg (an XML file with a <defaults> section and per-account <lve id="..."> entries). Copy it from the old server, for example with scp, then apply it on the new server:
scp /etc/container/ve.cfg root@203.0.113.20:/etc/container/ve.cfg
lvectl apply all
According to CloudLinux, lvectl apply all resets all LVE settings based on /etc/container/ve.cfg. Check the result:
lvectl list
lvectl package-list
Important: a user's LVE ID is the account's user ID (UID). A transfer can give an account a different UID on the new server, and then a per-user override in ve.cfg applies to the wrong account or to nobody. Compare id USERNAME on both servers for accounts with custom limits, and set those again by user name if the UID changed:
lvectl set-user USERNAME --speed=100% --pmem=1024m
Package limits are not affected by UIDs, as long as packages with the same names exist on the new server. The PMEM lower bound, if you set one, is kept separately in /etc/sysconfig/limits_lower_bounds. For more on changing limits, see How to change CloudLinux LVE limits?.
2. CageFS settings
Copy only what you changed. According to CloudLinux:
- Custom mount points are in
/etc/cagefs/cagefs.mp. - Users excluded from CageFS are listed in files inside
/etc/cagefs/exclude/. - The enabled and disabled user lists are
/etc/cagefs/users.enabledand/etc/cagefs/users.disabled(both are directories). Copy them, and make sure the new server uses the same mode ("Enable All" or "Disable All"):cagefsctl --display-user-mode
- Do not overwrite the existing files in
/etc/cagefs/conf.d/; CloudLinux asks you not to modify them. Copy only files you added yourself, for example commands added to CageFS as in Add a command/binary to CageFS.
Then update the skeleton and remount all users. According to CloudLinux, --remount-all kills the users' current processes, so run it at a quiet time:
cagefsctl --force-update
cagefsctl --remount-all
Check the result:
cagefsctl --list-enabled
3. PHP Selector
Server-wide PHP Selector defaults (default version and default extensions) are in /etc/cl.selector/defaults.cfg. Copy it, together with any /etc/cl.selector/symlinks.rules or custom native.conf you created, then register the alt-php versions:
cagefsctl --setup-cl-selector
Per-user choices (version, extensions and options) are stored in each user's home directory under ~/.cl.selector/ (defaults.cfg and alt_phpXX.cfg). According to CloudLinux, these files come across with the home directory backup when the account is migrated, so the settings are kept. If a user's settings did not apply after the move, see How to restore PHP Selector options after restore or migration?.
4. MySQL Governor and other settings
- MySQL Governor's configuration is in
/etc/container/mysql-governor.xml, and its database-user map in/etc/container/dbuser-map. Install MySQL Governor on the new server first, then copy the configuration. - If you excluded mounts from LVE, copy
/etc/container/exclude_mounts.confand runlvectl start. - IO limits are switched on or off with
IO_LIMITS_ENABLEDin/etc/sysconfig/iolimits; according to CloudLinux a reboot is needed after changing it.
Check after the move
- Open LVE Manager in your control panel and compare the default limits and a few packages with the old server.
- Log in by SSH as a test user and confirm CageFS is active and the expected PHP version runs (
php -v). - Watch the first hours for "508 Resource Limit Is Reached" errors, a sign that limits are tighter than before (see How to fix 508 Resource Limit Is Reached error in CloudLinux and cPanel-WHM servers?).
Need a hand with a server move? Our cPanel server management team handles migrations.
Official documentation: CloudLinux limits, CloudLinux OS components (CageFS, PHP Selector, MySQL Governor), command-line tools.