Why managed hosts block plugins
Managed hosts run page caching, backups and security at the server level. Plugins that do the same job either conflict with that layer or add load the host has designed out. Kinsta says caching plugins hurt performance and usually do not work on its platform because it provides server-level page and object caching, and that "all non-incremental backups are not allowed". WP Engine says its servers already include most caching features and that nightly backups run on a separate server.
The second category is database thrashing: plugins that write on every page view (view counters, referrer logs) or compute related posts with heavy queries. WP Engine groups these as "Server & MySQL Thrashing" and "Related Posts". If your course site uses a view counter or a related-lessons widget, check this category closely.
Blocked plugins do not all fail the same way. WP Engine says Digital Access Pass is not actively removed but "will not work properly" on its platform, and that plugins depending on disabled server modules are not disallowed outright. Either way, find out before launch day.
Cross-host table for plugins course sites commonly run
The table lists categories and named plugins from each host's page. Kinsta and WP Engine name specific plugins; Liquid Web's managed WordPress product page mentions no plugin restrictions, and the Nexcess Managed WordPress plugin-management docs list none and link an article on optimising with W3 Total Cache. Nexcess appears alongside Liquid Web in Liquid Web's site header; confirm with Liquid Web which documentation applies to your plan.
| Plugin or category | Kinsta | WP Engine | Liquid Web / Nexcess managed WordPress |
|---|---|---|---|
| W3 Total Cache | Not named; caching plugins generally discouraged, Cache Enabler banned | Disallowed | Not listed as disallowed; Nexcess docs include a W3 Total Cache optimisation article |
| SiteGround Speed Optimizer (sg-cachepress) | On the complete banned list | Not on the list | Not listed |
| Duplicator (free) | Recommended for migrations | Disallowed (duplicator folder) | Not listed |
| Duplicator Pro | Banned | Not separately named | Not listed |
| UpdraftPlus | Banned ("Updraft") | Not on the list | Not listed |
| All-in-One WP Migration | Banned | Not on the list | Not listed |
| BackWPup | Banned at 5.5 and below; 5.6.0 and later allowed | Disallowed (backwpup folder) | Not listed |
| WP DB Backup, WP-DBManager | WP DB Backup banned | Both disallowed | Not listed |
| Related-posts plugins | Page says related-posts plugins are not allowed; WordPress Popular Posts listed under Misc | Contextual Related Posts, Similar Posts, Dynamic Related Posts, SEO Auto Links & Related Posts disallowed | Not listed |
| View counters | Not named | WP PostViews disallowed | Not listed |
| Server-side image optimisation | Banned; cloud-based optimisers allowed, EWWW Image Optimizer now allowed | Not on the list | Not listed |
| Server-side video conversion (FFmpeg) | Banned; use an external service | Not on the list | Not listed |
| Always-on scanning security plugins | Discouraged; Wordfence supported with extra configuration and traffic logging disabled | Bad Behavior disallowed as duplicate of host blocking | Not listed |
What each host says to use instead
Kinsta points to its daily automatic and downloadable backups, incremental backup plugins for off-site copies, the free Duplicator or Migrate Guru for migrations, cloud-based image compression, an external service such as Cloudinary for video, and its IP Deny tool, rate limits, Cloudflare integration and Patchstack-powered vulnerability protection in place of scanning plugins.
WP Engine points to its nightly backups (restorable, copyable and downloadable) plus third-party tools that store data externally, Google Analytics instead of on-server view tracking, and Related Posts for WordPress, Outbrain or Contextly, which offload related-posts work to external servers. For membership, it names Paid Memberships Pro, Restrict Content and S2Member as alternatives to Digital Access Pass, which relies on PHP sessions and system-level crons.
For email, WP Engine does not ban plugins but discourages sending directly from WordPress and recommends third-party services or your email provider's SMTP server.
Migration traps worth checking
The most common surprise is the migration tool itself. A site moving from SiteGround to Kinsta often has Speed Optimizer installed, which is on Kinsta's list. A site moving to WP Engine with a Duplicator package is using a plugin WP Engine disallows; use the host's own migration route instead.
Kinsta also lists one incompatible plugin, WooCommerce Amazon & eBay Integration, because it needs the proc_open PHP function, which Kinsta disables. Any course-store integration that shells out to system commands deserves the same check.
WP Engine notes that plugin names can be similar or change, and that its folder list is "the only source of truth". Compare folder names, not display names.
Pre-migration checklist
Run this before you book the cutover window.
- Export the plugin list with folder names: wp plugin list
--fields=name,status on the old host. - Compare every folder name against the target host's list, including inactive plugins.
- For each match, note what the plugin does and the host's stated alternative.
- Remove caching and backup plugins that duplicate platform features before the copy, so they do not write stale config on the new host.
- Replace related-posts and view-counter plugins with an external or lighter option, and test lesson pages that used them.
- Re-check the list on cutover day; WP Engine says plugins may be added temporarily while a security issue is fixed.
Questions before you decide
Can I use Duplicator to move a site to WP Engine?
WP Engine's disallowed list includes the duplicator folder, so plan to use WP Engine's own migration route. Kinsta, by contrast, recommends the free Duplicator or Migrate Guru for migrations while banning Duplicator Pro.
Is UpdraftPlus allowed on Kinsta?
No. Kinsta lists Updraft among banned backup plugins and says all non-incremental backups are not allowed; it recommends incremental backup plugins for off-site copies alongside its own daily backups.
Does Liquid Web publish a banned plugin list for managed WordPress?
Not on the pages reviewed. Liquid Web's managed WordPress page mentions no plugin restrictions, and the Nexcess Managed WordPress plugin-management docs list no disallowed plugins and link guidance on optimising W3 Total Cache. Ask support before migrating if you rely on an unusual plugin.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Kinsta docs: banned and incompatible plugins Accessed 30 Oct 2026
- WP Engine: disallowed plugins Accessed 30 Oct 2026
- Nexcess documentation (Liquid Web): Managed WordPress plugin management Accessed 30 Oct 2026
- WordPress.org: Speed Optimizer plugin listing (sg-cachepress) Accessed 30 Oct 2026
- Liquid Web: Managed WordPress hosting Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.