Before migration, identify the application sender
Determine which service sends WordPress messages and which configuration connects the application to it. Cloudways documents options such as Elastic Email and external SMTP, while human mailboxes are a separate requirement. Do not assume that moving website files moves every mail-delivery setting correctly. Record the sender domain, responsible service and intended recipient role without exposing passwords, API keys or a list of real customer addresses.
Preserve domain authentication deliberately
Sender authentication records such as SPF and DKIM need to reflect the actual sending arrangement. Follow the current service instructions and keep unrelated mail-routing records intact. A fictional agency should compare the intended record change with the existing domain configuration instead of adding a second conflicting record blindly. This guide explains the verification task; it does not provide a universal DNS value suitable for every email provider or domain.
Test the complete permitted path
An application showing message sent is only one observation. Use a small authorized test addressed to a controlled inbox, then verify actual receipt and the information needed to understand the delivery result. Do not generate messages to customers or manufacture business events for testing. Check the business-critical message type, such as a form notification or password reset, because different plugins may not share exactly the same sending path.
Keep failure evidence actionable
If receipt fails, record the message type, approximate time, application response and available delivery status without copying sensitive message content into a public report. Distinguish a queue acknowledgement, provider acceptance and inbox receipt. Avoid repeated resends when the outcome is uncertain. The operating record should identify who can inspect the relevant service and what bounded next check is supported, rather than reducing every mail issue to changing hosts.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Cloudways transactional email versus mailboxes — Merchant documentation · support.cloudways.com · Merchant-controlled · checked 2026-09-21
- Cloudways sender-domain and email DNS setup — Merchant documentation · support.cloudways.com · Merchant-controlled · checked 2026-09-21