An old hosting server can appear healthy while its operating system has fallen outside normal maintenance. Moving CentOS 7 to AlmaLinux 8 with cPanel ELevate is an operating-system migration, not an ordinary panel update. The priority is keeping websites, mail and customer data recoverable throughout the change.
This guide covers an existing CentOS 7 server running cPanel & WHM. Requirements and blockers can change: check the linked official documentation immediately before scheduling work. The workflow below has been checked against that documentation; it has not been executed against your server.
cPanel’s documentation lists CentOS 7 to AlmaLinux OS 8 as a supported elevation. The CentOS 7 source must run cPanel & WHM 110, updated to its latest available minor release for that operating system, with a valid licence and an interactive root shell.
Use cPanel’s ELevate wrapper for a cPanel installation. Do not substitute a generic Leapp command sequence: the panel-specific workflow handles additional dependencies. This path also does not jump directly from CentOS 7 to AlmaLinux 9 or 10. Any later elevation is a separate project with separate eligibility checks.
An in-place migration may preserve an established configuration, but it also carries that configuration’s complexity forward. Compare it with building a fresh, supported server and transferring accounts through the vendor’s supported process. A replacement server can be easier to rehearse when the old machine has substantial customization or difficult recovery constraints.
Write down a recovery decision point and who can authorize it. Do not promise zero downtime or assume another server can reproduce every custom service without preparation.
A CentOS 7 to AlmaLinux 8 migration needs a verified backup and a recovery path that remains available if the host fails.
cPanel states that the elevation script does not back up your data before upgrading. Account backups are useful, but they do not necessarily preserve every system customization. A snapshot also needs a suitable consistency strategy for active databases.
From an interactive root shell, obtain the script from the official cPanel repository. Inspect the downloaded file before running it. The documentation uses /scripts examples and specifies the cPanel scripts directory; verify the expected directory mapping on your server.
wget -O /scripts/elevate-cpanel \
https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel
chmod 700 /scripts/elevate-cpanel
less /scripts/elevate-cpanel
/scripts/elevate-cpanel --check
Treat a failed check as work to resolve, not something to suppress. Review the current known-blocker list, package repositories, available space on the relevant filesystems, supported database versions and incompatible packages. Container-like environments are a documented blocker. Updating the script does not make an otherwise unsupported configuration safe.
Complete source-system updates and the cPanel preparation steps in the official guide. Re-run --check after resolving issues, and ensure the final recovery point is current before starting the outage.
Before a CentOS 7 to AlmaLinux 8 change, review application and cPanel support for the specific migration route.
/scripts/elevate-cpanel --start
The elevation has multiple stages and reboots. Allow the documented process to progress, monitor through reliable access and avoid unrelated package changes during the run. Status and logs provide more useful evidence than a single successful SSH reconnect:
/scripts/elevate-cpanel --status
/scripts/elevate-cpanel --log
If the upgrade stops, preserve the logs and investigate the reported stage with the official guidance or support. Do not repeatedly restart it, remove state files or use --clean as a generic repair. cPanel restricts cleanup after the early stages; --continue belongs only after the underlying failure has been understood and addressed.
| Area | Evidence to collect | |
|---|---|---|
| 1 | Operating system and panel | Expected release, working WHM, valid licence and healthy update configuration. |
| 2 | Websites | Representative static and dynamic pages, login, forms, database access and TLS. |
| 3 | Mail and DNS | Inbound/outbound delivery, queues, authentication and authoritative records. |
| 4 | Applications | Supported runtime versions, dependency installation and successful application startup. |
| 5 | Operations | Cron jobs, monitoring, backups, resource usage and a fresh recovery test. |
Applications managed through Passenger may need dependency or runtime attention after an OS change. Work inside the correct account and application directory, use its supported runtime and reproducible dependency process, and test the application itself. A running web server does not prove that every hosted application works.
Watch error logs, mail queues and scheduled jobs through a representative operating period. Keep the previous recovery point until the agreed validation is complete, then document the resulting OS, panel and application versions.
The most useful upgrade plan answers a practical question before anything changes: if this server cannot boot or a key customer workflow fails, exactly how will we restore service?
Related reading: Install TypeScript on AlmaLinux: A Practical Project Setup
Keep exploring: See all Linux and developer guides.
The Nandan Sinha newsletter
Get new articles on technology, practical guides, wellbeing and spirituality, delivered to your inbox.
Subscribe by email. Confirm your address to join. Unsubscribe anytime. Privacy policy.
We use essential cookies to run this website and optional cookies for analytics and advertising. Choose Accept All, Reject, or Preferences to manage optional cookies. You can change your choice at any time.
Manage your cookie preferences below:
Essential cookies enable basic functions and are necessary for the proper function of the website.
These cookies are needed for adding comments on this website.
Google's current Sign in with Google client library. It renders the Google sign-in button, or the One Tap prompt, so visitors can log in to your site with their Google account. It replaces the older Google Sign-In platform library.
Service URL: policies.google.com (opens in a new window)
Google Tag Manager simplifies the management of marketing tags on your website without code changes.
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Service URL: policies.google.com (opens in a new window)
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
AddToAny provides share and follow buttons that let visitors post your pages to social networks, messaging apps, and bookmarking services.
Service URL: www.addtoany.com (opens in a new window)
You can find more information in our Privacy Policy and Privacy Policy.





Leave a Reply