How to Cancel WP Engine (2026): 60-Day Guarantee, Notice Periods & Export

Quick answer: WP Engine offers a 60-day money-back guarantee on new plans. There's no self-serve cancel button on most plans - request cancellation via User Portal support chat, or disable renewal to let it lapse. Export every environment first; the account goes when the plan does.

Step 1: Export Your Environments

• User Portal > environment > Backup points > create a fresh checkpoint, then download it - the zip includes files and database
• Repeat for every environment on the account - prod, staging, dev
• Download any access logs or SFTP-stored files you still need

These zips are portable - a competent new host can deploy them directly.

Step 2: Migrate Before You Cancel

1. 1.Sign up at the new host - Bluehost migrates WordPress free
2. 2.Hand them the WP Engine backup zip or SFTP access for migration
3. 3.Verify the site on the new host's temporary URL - note: WP Engine's mu-plugins drop-in won't exist elsewhere; check for platform-specific code
4. 4.Update DNS - WP Engine sites use CNAME/A records, not nameservers, so you'll change records at your DNS provider: DNS guide

Watch for WP Engine-isms during migration: disallowed plugins list doesn't apply elsewhere, the object-cache drop-in may need removal, and EverCache references in wp-config should be stripped. Details: migration guide.

Step 3: Request Cancellation

• Within 60 days (new plans) - request cancellation and refund via support chat; the guarantee covers plan cost, not add-ons
• Monthly plans - cancel before the next billing date via support; no partial-month refunds typically
• Annual plans, past 60 days - generally non-refundable; the option is disabling renewal so it lapses at term end - ask support to set non-renewal if the portal doesn't offer it

Don't Forget

Genesis themes bundled with WP Engine, premium add-ons, and any sub-user access all end with the account. DNS records pointing at WP Engine will 404 the moment the environment is deleted - only cancel after the new host is serving traffic. Pitfalls: migration mistakes.