Introduction

A mail migration can move live delivery successfully while journaling still sends message copies to an old archive system. Users may send and receive mail normally, but compliance copies continue flowing to a retired journal mailbox, old archive appliance, or previous provider because the journaling target was never updated during cutover.

Treat this as a compliance-routing problem instead of a normal delivery problem. Start by identifying where journal copies are actually going now, because mail migration projects often validate mailbox traffic first and leave background archive or journal paths tied to legacy infrastructure.

Symptoms

  • Mail delivery works, but journal copies still arrive at the old archive platform
  • Compliance or archive teams report missing data in the new system after migration
  • Message traces show normal delivery plus an unexpected copy sent to a retired journal target
  • The old archive system still receives traffic even though user mailboxes were moved
  • Journaling failures, bounces, or queue growth begin after mail cutover
  • The issue started after archive migration, Exchange cutover, or provider switch

Common Causes

  • A journal rule or compliance transport rule still points to the old archive destination
  • The migration moved user mailboxes but did not update the journal mailbox or archive address
  • Hybrid or coexistence transport paths still duplicate mail toward the previous archive system
  • The new archive platform was prepared, but the live journal target was never switched over
  • Compliance dependencies made the team delay archive cutover and the old route stayed active
  • Validation focused on user-visible mail flow instead of hidden journaling or archive traffic

Step-by-Step Fix

  1. Capture a recent message trace or header trail and confirm where journal copies are actually being delivered, because you need proof of the live archive path before changing any compliance-related configuration.
  2. Identify the active journaling control point in the mail platform, because the real target may be defined in Exchange journal rules, transport rules, a gateway, or another compliance layer rather than in the mailbox system itself.
  3. Compare the current journal destination with the intended post-migration archive target, because many projects build the new archive first but never switch the rule that actually sends journal copies.
  4. Check whether the archive destination is a journal mailbox, external SMTP address, appliance, or gateway handoff, because each of those paths can survive migration in a different place.
  5. Review coexistence, hybrid, or gateway rules that may still duplicate mail toward the old archive path, because one leftover transport rule can keep the legacy journal system alive even after the primary destination changes.
  6. Update the real active journal target only after confirming the new archive platform is ready to receive and retain compliant copies, because changing compliance flow without validating the destination can create an audit gap.
  7. Send controlled test messages through the affected mail flow and verify both user delivery and journal copy delivery, because the archive fix is incomplete if only one side of the message path works.
  8. Confirm the old archive system stops receiving new journal traffic after the change, because a successful test into the new system does not prove the legacy archive route has been removed everywhere.
  9. Document the final journaling design, archive target, and cutover date for compliance records, because journal routing is easy to overlook during later mail platform changes.