cPanel & WHM 138 Upgrade Checklist: Meridian Rollout and Hosting Workflows

July 28, 2026

cPanel & WHM version 138 introduces Meridian, an optional goal-based cPanel interface. It is not a reason to rush a production server into change. Treat it as a managed hosting rollout: confirm the release tier and provider support, decide whether the interface is useful for the account types you host, test the day-to-day paths that matter, and leave Jupiter available for users who need it.

This checklist is for hosting administrators, resellers, and site owners who need a practical adoption plan. It does not replace the provider’s maintenance process or make changes to existing backup retention and schedules.

What cPanel 138 Changes

According to cPanel’s release notes, Meridian organizes common tasks into Websites, Email, Files, Databases, Security, and Performance hubs. Its dashboard is intended to show account actions and next steps, while Guided Setup can bring domain, website, and email setup into one flow.

Meridian is opt-in. Jupiter remains supported, including for advanced and less-frequently used tools, and a user can switch back. Availability can depend on the hosting provider, enabled features, and the server’s release tier. That makes a deliberate pilot much more useful than a blanket instruction to change every account.

Decide Whether Your Server Is a Candidate

Start with the server’s normal change-control process. Confirm which cPanel & WHM release tier it uses, whether the provider supports version 138 for that server, and whether any custom themes, plugins, account packages, or documentation assume the older interface.

Choose a small group of internal or low-risk accounts for the first review.
Record the current cPanel interface and the workflows each account uses most often.
Schedule the work in an approved maintenance window when support staff can respond to access or navigation questions.
Keep the current backup and retention policy unchanged. Confirm the usual recovery contact and restore path before any panel maintenance.
Tell account owners that Meridian is optional and that Jupiter remains available during the rollout.

Test the Meridian Workflow Before Broad Enablement

Use a representative account rather than a newly created empty account. Test the routes a customer actually relies on: domain management, file access, databases, email, security tools, performance settings, and the path back to Jupiter. Check that the account sees only the features that its package should expose.

For WordPress hosting, open the site from a private browser window, sign in to the WordPress dashboard, confirm the intended PHP and caching controls still behave normally, and verify that the selected cPanel path does not confuse the site’s existing support process. The Fix I.T. Phill WordPress Support hub is the escalation starting point for WordPress update, restore, and troubleshooting work.

Review Guided Setup and Optional Services

cPanel documents that Meridian’s Guided Setup can cover domain, site, and email configuration and may offer WordPress, Sitejet Builder, a Node.js application, or an uploaded site when the hosting provider enables those options. Review the feature list for the account package before presenting it as a standard path to customers.

Do not enable an application path merely because it appears in the interface. Confirm who owns ongoing updates, backups, billing, and support for that site type. For a conventional WordPress install, keep the support path clear and use the Install WordPress with Installatron guide when Installatron is the supported installer on the account.

Handle Domain Changes Carefully

Version 138 adds domain recommendations and purchase capabilities that can integrate with WHMCS when the hosting business chooses to configure them. It also adds the ability to rename primary, addon, and parked domains in the cPanel Domains interface. Both features deserve ownership and communication rules before they are made widely available.

Enable domain recommendations only after the WHMCS owner has reviewed pricing, ordering, support, and billing expectations.
Keep domain renames out of unrelated maintenance windows and make sure the responsible site owner approves the change.
Before a rename, identify the site, mailbox, certificate, DNS, redirect, application, and customer communication impact.
After an approved change, verify the intended site and email experience from outside the control panel.

Review New Administration Touchpoints

The release notes also introduce a WebPros Dashboard plugin for connecting a cPanel & WHM server to WebPros Dashboard and managing status, websites, alerts, and tools across servers. The feature is also backported to cPanel & WHM 134 and 136. Treat any new external management connection as a separate administrative decision: define the owner, access model, notification path, and support boundary before enabling it.

Version 138 also changes the WHM Initial Setup Wizard’s legal step and adds a configurable action for forwarded mail identified as spam. Review these with the team responsible for legal acceptance and mail policy. Avoid changing mail handling during an unrelated interface trial.

Post-Update Checks for Hosted Sites

After the provider-approved update, verify that normal hosting work is still intact. Check one account from each major package type, then work outward only if the pilot behaves as expected.

Confirm WHM access, cPanel login, account navigation, and the option to use Jupiter where required.
Open a representative website and its HTTPS redirect path from a private browser window.
Check mail delivery, a mailbox login, and any agreed spam-handling behavior.
Confirm database and file-management paths are available to the users who are meant to have them.
For WordPress and WooCommerce accounts, test the dashboard and a normal visitor or customer journey before closing the change.
Review the approved monitoring and support queues for real customer impact, then document any interface-specific guidance.

When to Pause and Escalate

Pause the rollout when a provider has not enabled the required release tier, a package exposes unexpected tools, a user cannot return to the interface they need, or a site, mail, billing, or support workflow behaves differently after the update. Keep the scope narrow, capture the affected account and visible symptom, and work through the provider’s normal escalation process. Do not change unrelated account settings or recovery schedules as a reaction to a panel-navigation issue.