Introduction

If email forwarders disappear or stop routing after a cPanel account transfer, treat it as a migration and routing problem instead of a mailbox delivery problem. In many cases, the mailbox itself still exists and can receive normally, but the forwarder rules were not restored, were overwritten later, or are no longer being applied on the destination server.

Start by proving whether the forwarders actually exist on the new server, then confirm the domain is being handled as local mail and that each destination is still valid. That separates missing configuration from a wider mail-routing issue.

Symptoms

  • Forwarders that existed before the transfer no longer appear in cPanel
  • Mail sent to forwarded addresses no longer reaches the destination address
  • Primary mailboxes still work, but alias-style forwarding does not
  • Only some forwarders are missing while others still function
  • The forwarder list is empty or incomplete after restore
  • Test messages never reach the external destination even though there is no obvious mailbox outage

Common Causes

  • The account transfer did not restore the forwarder configuration cleanly
  • Mailboxes were recreated, but forwarder rules tied to the domain were missed
  • The domain’s email routing is set wrong after migration, so local forwarders never run
  • A later restore, sync, or migration pass overwrote newer forwarder data
  • Addon domain, parked domain, or subdomain mappings were not rebuilt correctly
  • Forwarders point to invalid or retired destination addresses
  • DNS now sends mail elsewhere, so the new cPanel server never receives the message to forward

Step-by-Step Fix

  1. Open **Email > Forwarders** in the destination cPanel account and confirm whether the missing entries are truly gone, because if the list is already empty or incomplete, the first problem is missing configuration rather than mailbox access.
  2. Compare the current forwarder list with a known-good source from the old server, backup, or migration notes, because you need an exact record of which addresses should forward and where they should go.
  3. Check **Email Routing** for the affected domain and make sure the domain is handled as local mail where appropriate, because forwarder rules will not run correctly if the server is not responsible for processing that domain’s inbound mail.
  4. Verify that the affected domain, addon domain, or subdomain restored cleanly into the destination account, because broken domain mappings can make the forwarders tied to that domain disappear or fail silently.
  5. Recreate one missing forwarder manually as a controlled test and send a message to it, because that quickly shows whether the issue is just missing forwarder data or a larger routing problem on the new server.
  6. Confirm that each forwarder destination is still valid and able to accept forwarded mail, because a dead destination mailbox or strict remote filtering can make a healthy forwarder look broken.
  7. Review whether another restore, sync, or transfer retry happened after the initial move, because later migration activity often overwrites the forwarder state you thought had already been restored.
  8. Test from an external sender after each correction and track results by address instead of by domain, because some forwarders fail only on one mapping or one destination target.
  9. Once the forwarders work again, document the recovered rule list before any future migration or DNS change, because forwarders are easy to miss during transfer validation and are often forgotten until users report lost mail.