Emails going to spam after changing domain or email provider
Separate what changed from what stopped working. A new domain, a move between mail providers and a reconnected CRM affect different parts of the email journey. Start with a before-and-after map of the affected routes, then use message evidence to decide what needs correcting.
- Why can emails go to spam after a migration or domain change?
- The change may leave a sending route with incomplete authentication, a different sender identity or an application still using the old connection. Recipient rules and message changes can also affect the result. The timing is a clue, not proof that the migration caused it. Establish whether messages are failing to send, bouncing or reaching junk before changing more settings.
1. Identify which kind of change took place
| Change | What may be different | First evidence to collect |
|---|---|---|
| New company domain or email-address domain | The visible sender, signing domain, reply address, aliases and application identity | The old and new addresses, affected message types and an example from each route |
| New mailbox provider, with the same company domain | Outbound infrastructure, authentication, connectors and mailbox integrations | The cutover time, active old and new services, and comparable sent-message evidence |
| A new tenant with the same provider | Tenant-specific DKIM values, permissions, routing and connected accounts | Configuration supplied by the destination tenant and the applications still using the previous one |
| CRM, invoicing or other application reconnected | The connected user, permissions, selected From address or sending service | Connection status, application errors and a comparison with direct mailbox sending |
If only incoming email is failing, start with inbound routing and mailbox availability. If outgoing messages arrive in recipients’ junk folders, investigate the outbound route and received evidence. These are different symptoms, even when they began on the same day. Microsoft’s mail-flow overview (opens in a new tab) explains the role of routing and authentication in the wider setup.
2. Build a before-and-after record before making another change
Record the time of each change and the first known affected message, including the time zone. Include the mailbox provider, visible sender address, sending application, recipient environment and message template. Keep a successful pre-change example where one is available.
List the systems that send email, not just the mailboxes you migrated. A CRM, invoice tool, website form, help desk or mailing platform may send independently. Mark each route as still on the old service, moved to the new service or controlled by a separate supplier.
This record lets an administrator test a specific explanation. For example, a CRM may still send through the previous provider while staff mail uses the new one. Do not assume that every message followed the mailbox migration.
Keep these details together
- Change date and owner
- Old and current sending route
- Actual From and reply-to identity
- Exact error or observed destination folder
- A comparable successful example
- Any other changes to templates, links or volume
3. Check SPF against the senders that are actually active
Review whether the SPF configuration still authorises the legitimate systems using that SPF domain. During a transition, old and new services may both be active. Replacing the record with only the new mailbox provider’s value can omit another authorised sender, while retaining unused sources indefinitely leaves an inaccurate configuration.
Have the administrator review the complete record, its dependencies and the actual authentication result. Publish only one SPF record for a given domain or subdomain, and check the ten-DNS-lookup limit, including nested lookups. Microsoft’s SPF guidance (opens in a new tab) explains these constraints.
Do not add a second SPF record for the new provider or paste together every supplier’s example. Use the current instructions for your active routes, agree any change and verify it with an appropriate message afterwards.
4. Verify DKIM signing and DMARC alignment on new messages
Check that the new sending service signs as intended and that its published DKIM records match the account or tenant now sending. A record left by the previous service does not establish that the new route signs correctly. For Microsoft 365, use the destination tenant’s current values and confirm signing is enabled, following Microsoft’s DKIM setup guidance (opens in a new tab).
Then inspect a newly received message. Our email-header walkthrough explains the sending identities and trusted results to compare. DMARC needs a passing SPF or DKIM result that aligns with the visible From domain. A provider signing with its own domain can pass DKIM without providing that alignment for your company’s From address. The DMARC standard’s explanation of alignment (opens in a new tab) describes how these identities relate.
Keep the authentication result separate from the recipient’s filtering decision. Authentication can pass while a message still reaches junk. In that case, investigate the received verdict, route and message characteristics. Changing DMARC policy merely to make an error disappear is not a substitute for correcting an authorised sender.
5. Recheck applications, aliases and replies
Verify the connected account and selected sender in each application. A connection can look present while the underlying account, permission or address has changed. Check a message generated by the application itself, not only a manual email sent from the new mailbox.
Google’s primary-domain-change guidance (opens in a new tab) includes follow-up work on users, groups, aliases and applications. It advises checking with app developers about the effect on installed apps. A renamed Workspace address does not establish that every third-party connection has been updated.
Test the reply journey too. A message may arrive successfully but direct the customer’s response to an obsolete address or an unmonitored shared inbox. Record who receives and owns replies after the change. For billing routes, the invoice email troubleshooting guide distinguishes platform-owned sending from connected-mailbox sending.
6. Verify each route with a controlled test
| Test | Record the result | Do not infer |
|---|---|---|
| Direct staff-mailbox message | Sending trace, received authentication, destination folder and any filtering verdict | That CRM, invoice or mailing-platform routes also work |
| Message generated by a connected application | The actual sender, application event and received evidence | That a connected-account badge proves a successful send |
| Reply to the newly sent message | The address used, destination mailbox and person responsible | That successful outbound delivery proves the reply route |
| An old address or alias that must remain active | The agreed handling of incoming mail and any reply behaviour | That the old address is retained just because it used to work |
| Comparable message after a scoped correction | The changed variable, test recipient, result and remaining limits | That one inbox result guarantees future placement everywhere |
Use agreed test recipients and keep the relevant message conditions consistent. If urgent client correspondence is affected, use an established alternative channel while the issue is investigated. An administrator should decide whether a correction or rollback is justified, with the impact on other routes understood first.
Illustrative example: the mailboxes moved, but the CRM did not
A fictional firm changes mailbox provider while keeping its company domain. Staff can send directly, but CRM messages begin to fail. The timing suggests checking the migration, while the different outcomes suggest comparing the two sending routes.
The investigation finds that the CRM connection still points to the old service. That observation alone does not establish the complete failure mechanism. Its send error, active permissions and received evidence, if a message reached a recipient, determine the next action.
The administrator can then agree whether to reconnect the application, correct authentication or raise a supplier issue. A new test must use the CRM and verify the reply path as well. This is an illustrative diagnostic sequence, not a client case study.
A useful conclusion states
- What changed and which route was affected
- What the evidence actually establishes
- Who owns the correction
- How that route will be tested afterwards
When a specialist review is useful
A specialist review is useful when several suppliers are involved, different routes behave differently or the problem persists after the initial migration checks. Neotiqa’s email deliverability assessment is a scoped, read-only investigation that produces findings and a prioritised technical handover. Any implementation, migration work or monitoring is agreed separately.
For platform-specific detail, use our Microsoft 365 troubleshooting guide or Google Workspace guide. For a sales-platform route, the HubSpot guide separates connected-inbox and marketing sends.
The same investigation can support accountancy practices with multiple client-email systems, estate and letting agencies with branch and CRM changes, and law firms with practice notifications. For commercial sending workflows, explore our B2B SaaS support. Each engagement follows the affected systems and an agreed scope.
Questions about email after a migration or domain change
How long should we wait for email to stop going to spam after a migration?
There is no universal settling period. DNS caching and provider activation can take time, but a wrong record or broken connection will not necessarily resolve by waiting. Compare the configuration and newly received evidence with the expected route, and separate propagation from other causes.
Does changing the MX record fix outgoing email?
An MX record directs incoming mail for a domain. It does not, by itself, configure outgoing authentication or reconnect a CRM. Review outbound sending and inbound routing separately, then test the routes your business needs.
Is changing our email domain the same as moving to Microsoft 365?
No. A domain change alters an email identity, while a provider migration changes the service handling mail. You can do one without the other, or both together. Record which changed so the investigation covers the right identities, connections and routes.
Should we turn off DMARC to make the messages arrive?
Do not treat that as a general fix. Identify which legitimate route fails authentication or alignment and have the administrator evaluate the correction. Passing DMARC also does not guarantee inbox placement, so a policy change may leave the underlying issue unresolved.
Can Neotiqa work alongside the provider that performed the migration?
Yes. We can agree an independent deliverability assessment using supplied evidence or guided, least-privilege access. Your provider retains control of production settings. Recommendations, implementation responsibilities and any follow-up work are documented separately.
Did important email stop reaching people after a change?
Tell us what changed, which applications send email and what recipients are seeing. We can scope a review with your existing IT provider.