A WP Engine handover uses the language of sites and environments. For a client project, that usually means checking production, staging, development, extensions, DNS network needs, and which users keep access after the site changes account.
This is a good candidate for a written cutover checklist because WP Engine may involve a migration, a transfer code, or destination-account settings. Decide who can approve what before you put the site in motion.
Before you start
- Take a fresh backup of files, databases, and environment settings before changing ownership.
- Confirm whether email, DNS, domains, add-ons, staging, and backups move with the site or stay behind.
- Give your client a clear window for freeze time, maintenance mode, or DNS changes.
On WP Engine, specifically
- WP Engine says self-serve site transfers are available for all sites, and the transfer includes the production, staging, and development environments for the site. Source, checked September 3, 2026.
- A WP Engine self-serve transfer requires Owner or Full with billing permissions on both the source and destination accounts. Source, checked September 3, 2026.
- WP Engine can transfer to an account you manage or to someone else's account by using a transfer code from the destination account. Source, checked September 3, 2026.
- WP Engine requires product extensions to be reactivated on the destination account, and some extensions can lose settings or data during transfer. Source, checked September 3, 2026.
- WP Engine does not support Dedicated Development Environments or sandbox sites for site transfers. Source, checked September 3, 2026.
The three stages
Prepare
Inventory the production site, staging copies, database names, cron jobs, environment variables, and billing add-ons. Pause risky content edits while the host prepares the transfer.
Transfer
Start the provider's account-transfer flow or create the receiving account path they document. Share only transfer codes or dashboard invitations, never your own login.
Confirm
Load the site from the new owner context, check SSL, forms, uploads, admin login, scheduled tasks, and any DNS records that point traffic at the host.
What to tell your client
- What moves automatically and what they need to recreate.
- Who pays for the hosting plan once the transfer is accepted.
- Whether your collaborator access stays in place after ownership changes.
After it is done
Record the asset in Everkey, change its ownership status from needs_transfer to client_owned, and leave a short note with the account that now controls the site. The free tier is enough for a small handover map.