HBMHBM Rocket
ALL DOCS
DOCUMENTATION

Migration guides

7 MIN READ

Switching from another speed plugin or service should not require downtime, and it does not. Run HBM Rocket alongside your existing stack for one week, confirm parity, then deactivate the old one.

From WP Rocket

Day zero

  • Add the site to HBM Rocket dashboard, install the agent plugin, set the secret
  • Leave WP Rocket active
  • Watch the first audit complete; baseline score recorded

Day one to seven

  • HBM Rocket runs alongside, applying its optimizations on top
  • Critical CSS pushes within an hour, JS delay applies on next page load
  • Page cache: WP Rocket serves first, HBM Rocket short circuits if WP Rocket misses

Day seven, switchover

wp plugin deactivate wp-rocket
wp plugin delete wp-rocket
wp hbm-rocket purge

Cancel the WP Rocket subscription. The savings are real even at agency volume.

From LiteSpeed Cache

LSCWP relies on the LiteSpeed server. If you are leaving LiteSpeed hosting, LSCWP cannot follow you. If you are staying:

  • HBM Rocket and LSCWP can coexist for a few days
  • LSCWP serves cache from LiteSpeed at the server level (faster than any plugin can be)
  • HBM Rocket's critical CSS, JS delay, and image optimization stack on top
  • Once HBM Rocket is steady, deactivate LSCWP
Some teams keep LSCWP for the server level cache and use HBM Rocket only for the optimization, audit, and fleet view layer. That works. Set pageCache to off in HBM Rocket and let LSCWP handle the cache.

From NitroPack

Pre flight

  • NitroPack rewrites HTML through their cloud. Disable optimization in the NitroPack dashboard before installing HBM Rocket to avoid double optimization.
  • Keep NitroPack's plugin installed and connected, but with optimization paused

Switch

  • Install HBM Rocket agent, set secret, wait for first audit
  • Compare scores side by side for 2 to 3 days
  • When you are confident, deactivate the NitroPack plugin and cancel the subscription

From WP Fastest Cache, W3 Total Cache, SG Optimizer

All three are simpler than HBM Rocket. Migration is straightforward:

# 1. Install HBM Rocket
wp plugin install /tmp/hbm-rocket.zip --activate
wp option update hbm_rocket_secret <SECRET>

# 2. Wait for first audit (5 minutes)

# 3. Deactivate the old plugin
wp plugin deactivate wp-fastest-cache
# or w3-total-cache, or sg-cachepress

wp hbm-rocket purge

No coexistence period needed; these are not sophisticated enough to interfere.

From a custom internal stack

If you have hand rolled optimization (a custom plugin that injects critical CSS, custom JS deferral, etc), keep it during the trial. The agent does not break anything you have done yourself. Compare audits, decide what to retire.

Rollback

If anything goes wrong, the rollback is one command:

wp plugin deactivate hbm-rocket
wp plugin delete hbm-rocket
wp hbm-rocket purge   # NOTE: run this BEFORE deactivate to clear cached HTML

The plugin removes its cache directory and option keys on uninstall. No residue.

Migration guides | HBM Rocket