Migrating from Other Cache Plugins (Pro)
Already using another caching plugin? xSpeed Cache Pro can read its settings and translate them into the matching xSpeed Cache settings, so you do not have to set everything up again by hand.
What this does
The Migration panel detects supported caching plugins on your site and imports their settings into xSpeed Cache. It reads the other plugin’s saved configuration, maps each setting to its xSpeed Cache equivalent, and writes the result into the right modules (page cache, minify, lazy load, and so on).
xSpeed Cache only imports settings that have a clean match. Options that work very differently in the other plugin are skipped instead of guessed at, so nothing is imported incorrectly.
You can preview exactly what will be imported before anything is written.
Supported source plugins
xSpeed Cache can import from these caching plugins:
- WP Rocket
- W3 Total Cache
- WP Super Cache
- LiteSpeed Cache
If one of these plugins is installed and configured, it shows up in the Migration panel as an import source.
Why use it
Reconfiguring a caching plugin from scratch is slow and easy to get wrong. Migration carries over your existing page cache rules, exclusions, minify choices, and lazy load settings in one step, so you keep the setup you already tuned.
Requirements
- xSpeed Cache Pro must be installed and active.
- The plugin you want to import from must be installed and configured on the same site.
Note: Each source plugin stores its settings differently. xSpeed Cache reads them from wherever that plugin keeps them — the options table for WP Rocket and LiteSpeed Cache, and a config file on disk for W3 Total Cache (
wp-content/w3tc-config/master.php) and WP Super Cache (wp-content/wp-cache-config.php).
How to import your settings
- Open the xSpeed Cache dashboard and go to the Migration panel.
- xSpeed Cache lists each detected source plugin, along with how many settings it would import.
- Find the source you want and select Import.
- Review the preview of what will change. This shows the settings xSpeed Cache is about to write, before anything is saved.
- Confirm the import.
- xSpeed Cache writes the mapped settings into the matching modules and marks that source as imported.
Note: You can also start an import from the dashboard notice. When xSpeed Cache detects another caching plugin, it shows a one-click Import prompt for it on standard admin screens.
What happens after an import
After a successful import, xSpeed Cache deactivates the source caching plugin. Two page caches running at the same time fight over the cache drop-in and can cache the same pages twice, so the old plugin is turned off for you. The panel tells you which plugin was deactivated.
Important: Importing turns caching on if the source plugin had caching enabled. xSpeed Cache installs its own cache drop-in and rewrite rules at that point.
What gets imported
The exact settings depend on the source plugin, because each one supports a different set of features. In general, xSpeed Cache maps these areas where the source has an equivalent:
| Area | Imported when the source supports it |
|---|---|
| Page cache | On/off state, cache lifetime, excluded URLs, excluded cookies |
| Mobile | Separate mobile cache |
| Minify | HTML, CSS, and JS minification; CSS/JS combine; defer JS |
| Lazy load | Lazy load for images, iframes, and videos |
| Preloader | Cache preloading and its schedule |
| Browser cache | Browser caching on/off |
| Object cache | Redis or Memcached backend, host, and port |
| CDN | CDN URL |
Not every source fills in every row. For example, WP Super Cache stores only a small set of options, so it imports fewer settings than WP Rocket or LiteSpeed Cache. The panel shows the real number of settings each source will import before you start.
Note: Your existing safety exclusions are protected. When an import brings in exclusion lists (excluded URLs, excluded cookies, bypass user agents, ignored query parameters), xSpeed Cache adds the imported entries to your current ones instead of replacing them. This keeps important rules like the logged-in user exclusion in place.
Best practices
- Run the import on a staging site first if you can, then check that your store, login, and account pages still behave correctly.
- Open the preview and read it before confirming. It is the clearest way to see what will change.
- After importing, clear your cache and load a few key pages to confirm everything looks right.
- Keep only one caching plugin active. xSpeed Cache deactivates the source for you, but double-check that no other caching plugin is still running.
Troubleshooting
My old plugin is not showing up as a source. The plugin must be installed and active, and it usually needs to have been configured at least once so its settings exist. xSpeed Cache reads W3 Total Cache and WP Super Cache settings from their config files on disk, so those files must be present and readable.
The import brought in fewer settings than I expected. xSpeed Cache only imports settings that map cleanly to an xSpeed Cache feature. Options that behave differently in the source plugin are skipped on purpose. The count shown next to each source is the honest number of settings that will actually be written.
My old caching plugin turned off after importing. That is expected. xSpeed Cache deactivates the source plugin after a successful import so two page caches do not run at once.
FAQ
Will importing overwrite settings I already changed in xSpeed Cache? For most settings, yes — the imported value is written. But exclusion lists are merged, not replaced, so your existing safety exclusions are kept.
Can I see what will change before committing? Yes. The preview shows the full set of settings xSpeed Cache will write before you confirm.
Does importing from LiteSpeed Cache work? Yes. LiteSpeed Cache is a supported source, alongside WP Rocket, W3 Total Cache, and WP Super Cache.
Related
- Page Cache
- Minify and Combine
- Lazy Load
- Object Cache
- CDN Integration