What WP Engine handles that you will now configure
WP Engine runs page caching, object caching and its Alternate Cron at the platform level, and it says it does not provide nameservers or email servers. The good news is that your DNS and email are already elsewhere, so they do not move. The work is replacing the platform features your site depended on.
| At WP Engine | Documented behaviour | SiteGround replacement |
|---|---|---|
| Page cache | Varnish page cache, 10-minute default expiry; pages with a cookie containing wordpress_ that has a value are excluded | Dynamic Caching (NGINX), on by default; logged-in users not cached by default; exclusions in Speed Optimizer |
| Object cache | Enabled per environment in the User Portal | Memcached, enabled in Site Tools then in Speed Optimizer |
| Alternate Cron | Server checks wp-cron.php every minute; requires DISABLE_WP_CRON | Site Tools > Devs > Cron Jobs running wp cron event run --due-now |
| Daily backups | 30 days kept | Daily backups; up to 30 copies on shared plans |
| Email and DNS | Not provided by WP Engine | No change needed unless you choose SiteGround mail or nameservers |
Step 1: Export a backup from WP Engine
In the User Portal open the environment's Backups page, create a fresh backup, then use the three-dot menu and Prepare ZIP. A Full Backup contains all files and the database; a Partial Backup lets you pick the database (saved as /wp-content/mysql.sql), themes, plugins and must-use plugins, uploads or other files. WP Engine says a prepared backup can be downloaded for up to 7 days.
WP Engine's article does not state whether wp-config.php is in the ZIP. Check the archive yourself before relying on it, and record the database table prefix from the live wp-config.php.
Step 2: Copy the site to SiteGround
SiteGround's Migrator route: in Site Tools go to WordPress > Migrator, choose the domain and path, click Generate, and paste the token into the SiteGround Migrator plugin on the WP Engine site. SiteGround's tutorial says it copies files and databases, keeps URL structure, and creates a temporary URL active for 48 hours. The plugin listing says it moves only WordPress content, cannot move a full Multisite network, and can fail on hosts SiteGround does not control.
If the plugin fails, SiteGround's transfer guide offers a professional migration by its team, which you pay for and which may take up to 5 business days, or an empty site you fill yourself over SFTP or SSH. SiteGround's WordPress hosting page currently advertises a free site transfer on all plans for a limited time, so check the price in your Client Area before ordering. For a manual move, WordPress's own migration guide says that if the domain stays the same you can copy files and the database, update wp-config.php if the database name or user changes, and reset permalinks.
Step 3: Swap caching and cron
WP Engine's Alternate Cron sets DISABLE_WP_CRON in wp-config.php. If that line arrives at SiteGround with no cron job behind it, scheduled tasks such as subscription renewals and drip lessons stop running. Either remove the line, or follow SiteGround's real cron tutorial: keep DISABLE_WP_CRON and add a job in Site Tools > Devs > Cron Jobs that runs wp cron event run --due-now from the WordPress directory. SiteGround suggests every 30 minutes for most sites; a membership site with time-sensitive renewals may want a shorter interval.
SiteGround's Dynamic Caching is on at server level for all sites. Speed Optimizer does not cache logged-in users by default, and you can exclude paths with a wildcard, such as /account/* or /checkout/*. WP Engine excluded cart, checkout and store pages automatically; on SiteGround, list your membership account, checkout and course pages explicitly.
Remove WP Engine-specific leftovers you find in wp-content/mu-plugins and any object-cache drop-in that refers to the old platform, then enable Memcached in Site Tools if you want an object cache.
Step 4: Verify on the temporary URL
The temporary copy lasts 48 hours, so schedule testing for the same day as the transfer. Freeze content changes on the WP Engine site during this window, or plan a second copy.
- Log in as a test student and as an administrator on the new copy; confirm the session survives a page change and a logout.
- Pick three real members at different stages and compare course progress, quiz attempts and certificates on both copies.
- Compare the number of active memberships or subscriptions and the newest five orders on both copies.
- Send a password reset and a purchase receipt from the new copy and confirm both arrive.
- Open a protected lesson while logged out and confirm it is still blocked.
- Check that one scheduled event runs on time after you set up the cron job.
Step 5: Point DNS and keep WP Engine briefly
Because WP Engine does not host DNS, your records are at your registrar or DNS provider. SiteGround documents two options: change only the A record to your SiteGround IP, which leaves other records and email intact, or move nameservers to ns1.siteground.net and ns2.siteground.net, after adding any custom records in SiteGround's DNS Zone Editor. For most WP Engine leavers the A-record route is the smaller change.
SiteGround recommends making no site changes for 48 hours after switching DNS. Keep the WP Engine plan until that window passes and your latest orders and enrolments appear only on SiteGround.
Questions before you decide
How long can I download a WP Engine backup ZIP?
WP Engine says a prepared backup can be downloaded for up to 7 days. Daily backups are kept for 30 days.
Will my scheduled tasks keep running after leaving WP Engine?
Not automatically if DISABLE_WP_CRON is still set. WP Engine Alternate Cron adds that constant, so either remove it or add a SiteGround cron job that runs due WordPress events.
Do I need to move email when leaving WP Engine?
Usually not. WP Engine says it does not provide nameservers or email servers, so your mail and DNS are already hosted elsewhere and only the A record needs to change.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- WP Engine: Backup and restore Accessed 30 Oct 2026
- WP Engine: Cache Accessed 30 Oct 2026
- WP Engine: Object caching Accessed 30 Oct 2026
- WP Engine: WP-Cron and WordPress scheduling Accessed 30 Oct 2026
- WP Engine: Scope of support Accessed 30 Oct 2026
- SiteGround KB: Transfer a website with WordPress Migrator Accessed 30 Oct 2026
- SiteGround: WordPress Automatic Migrator tutorial Accessed 30 Oct 2026
- WordPress.org: SiteGround Migrator plugin Accessed 30 Oct 2026
- SiteGround: Speed Optimizer caching (SuperCacher) Accessed 30 Oct 2026
- SiteGround: Replace WP-Cron with a real cron job Accessed 30 Oct 2026
- SiteGround KB: Point your domain to SiteGround Accessed 30 Oct 2026
- SiteGround: How to transfer an existing website Accessed 30 Oct 2026
- SiteGround: WordPress hosting plans Accessed 30 Oct 2026
- WordPress Advanced Administration: Moving WordPress Accessed 30 Oct 2026
- SiteGround KB: How to use the Backup service in Site Tools Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.