Moving an addon domain to a new document root

Back up the application and database, record the old root and check whether other domains share it. This control is not available for every domain type, including the main domain and names sharing its root.

1. Open Domains, select Manage beside the intended addon domain and record its current document root.
2. Prepare the new permitted folder and copy the application files with hidden configuration files included. Keep private storage outside the public root where the application requires it.
3. Update any absolute filesystem paths in application configuration, cron commands and deployment scripts. Preserve ownership and appropriate permissions.
4. Enter the new path in the document-root control and save. Follow the panel’s path restrictions rather than assuming any server directory is allowed.
5. Test the website over HTTPS, including uploads, administration and scheduled tasks. Keep the old directory intact until the new location is confirmed.

The domain should serve the prepared new directory, while other domains retain their intended content. Compare a distinctive test asset or application path to verify you are not seeing a cached old page.

If the site fails, restore the recorded root while you correct missing files or path settings. Do not delete the old folder during diagnosis. A PHP-FPM or runtime setting can be influenced by shared roots, so inspect the effective PHP version after the move.

No. Visitors can continue using the same hostname. This is a server-path change, while renaming a domain or moving DNS changes different parts of the service and requires its own plan.

• Understanding domains, aliases and subdomains in current cPanel
• Selecting a PHP version for a cPanel domain
• Uploading website files with cPanel File Manager
• Adding a domain alias that shares an existing cPanel website

• cPanel: Manage The Domain
• cPanel: Multiphp Manager For cPanel