Websites

Create a website

Administrators and resellers with website-creation permission can select Add website . The creation dialog supports static, PHP, Node.js, and Python websites.

Provide the primary domain and choose the runtime. Depending on the runtime and installed capabilities, the workflow can also configure:

• A PHP application profile and installed PHP version.
• A primary site account and optional SSH terminal access.
• Managed Let's Encrypt SSL and HTTP-to-HTTPS redirection.
• Native Core Panel DNS for eligible root domains.
• An access-and-limits package.

Core Panel includes PHP profiles for common applications such as WordPress, WooCommerce, Laravel, Symfony, Drupal, Joomla, CodeIgniter, CakePHP, Yii, Magento, PrestaShop, OpenCart, Craft CMS, TYPO3, Moodle, MediaWiki, phpBB, Nextcloud, Matomo, and custom PHP. A profile may be marked Coming soon when it does not have a safe unattended installer. Only selectable profiles can be provisioned.

Application profiles choose an appropriate initial public path and web-server routing. Framework installers run as the site's unprivileged account and preserve staged files when an operation is retried.

Import a website backup

Use the website-import action with either a portable Core Panel .tar.gz website archive or a cPanel full-account/cpmove archive. Core Panel uploads the file to isolated staging, validates its expanded paths and size, and shows a preflight summary before creating resources.

Choose the backup source

Select Import backup , then choose Upload archive for an existing cPanel full-account or cpmove .tar.gz archive, or choose Fetch from cPanel server after generating the full-account backup on the source server.

For a direct transfer, enter the cPanel server, SSH port, SSH username, and either a password or private key. In SSH host-key fingerprint , enter the exact SHA256 fingerprint verified through a trusted channel and provide the absolute Remote backup path . Core Panel streams the existing regular file over SFTP, does not delete it, and does not persist the supplied SSH credential. The remote archive must be in an accepted cPanel backup directory and must not exceed 100 GiB. Select Fetch and inspect backup to continue.

Select the website

Leave cPanel domain (optional) blank to migrate the account's primary domain. To migrate an independently rooted addon domain, reuse the same archive in a separate import and enter that domain. Same-root parked domains become aliases; independently rooted subdomains are copied and provisioned with their own roots.

Review what will be migrated

The selected import can include:

• Website files, detected PHP/runtime settings, and independently rooted subdomains.
• MySQL or MariaDB SQL dumps and native PostgreSQL pg_dump archives.
• Detected WordPress, Joomla, Laravel, Symfony, and generic PHP database configuration.
• Portable five-field cron jobs on the primary-domain import.
• Supported DNS records, mailbox password hashes, Maildir messages, and forwarders.

Core Panel normalizes destination database names, generates new database credentials and replacement DKIM keys, and updates a recognized managed application connection only after complete preflight recognition. Databases that cannot be linked safely to the selected application are retained with new credentials and listed in the migration warnings for manual configuration.

Resolve preflight findings

Before starting the import, review the staging-space estimate, detected resources, normalized names, and every conflict or warning. Preflight checks website, alias, subdomain, database, SFTP-user, mail-domain, DNS, mail-stack, reseller-feature, and quota capacity. Resolve all blocking conflicts before continuing.

Prerequisite: Install and enable the Core Panel mail stack before importing mail, and enable native PowerDNS before importing an authoritative DNS zone.

Complete and verify the migration

Provisioning uses rollback staging for website files, databases, and mail. When the job completes, open the backup's migration report and review retained warnings and successful verification steps.

Before cutover, test the application, database connectivity, mail login and delivery, subdomains, cron jobs, and HTTPS. Review imported A, AAAA, MX, nameserver, and DKIM records because they may still point to the source server. Change DNS only after destination checks pass, and keep the source server and backup available until post-cutover monitoring is clean.

Limitations

cPanel/FTP users, SSH keys, reseller packages, Apache-only directives, AutoSSL state, DNSSEC private keys, calendars, contacts, mailing lists, cPanel plugin state, and private files outside detected application or subdomain roots are not imported. Review the migration report and complete any required manual follow-up before cutover.

Website lifecycle actions

From the website list, authorized users can:

• Open and manage a website.
• Enable or disable public service.
• Retry a failed provisioning or configuration operation.
• Permanently delete a website after explicit confirmation.

Deletion removes the managed Nginx configuration and website root. Dependencies can block deletion; for example, remove a linked mail domain and additional SFTP users first. Download any required backup before permanently deleting a website.