Introduction

A hosting migration can move the website correctly while Cloudflare still sends visitors to the old site through a Bulk Redirect. The DNS records may already point at the new platform and the origin may already be healthy, but one redirect list entry or attached redirect rule keeps matching the old hostname pattern and forwarding traffic before the new site ever gets a chance to respond.

Treat this as an edge redirect problem instead of a general DNS or origin failure. Start by checking whether Cloudflare is still applying a Bulk Redirect for the affected hostname or path, because redirect logic at the edge can survive a migration even after the origin is fully replaced.

Symptoms

  • The domain or subdomain still redirects to the old site after migration
  • DNS looks correct, but visitors are still sent to a legacy hostname
  • The old destination appears only on certain hostnames or URL paths
  • Direct origin tests look correct while normal public traffic still goes elsewhere
  • Cloudflare is enabled and the issue started after redirect cleanup, cutover, or hostname changes
  • The problem affects one redirect pattern while the rest of the migrated site works normally

Common Causes

  • A Cloudflare Bulk Redirect list still contains the old destination
  • The redirect list was updated, but the attached rule or ruleset still points at the old list entry
  • Hostname or path matching is broader than intended and still catches migrated traffic
  • A migration changed the live hostname, but Cloudflare redirect logic was never updated to match the new destination
  • Another redirect layer in Cloudflare makes the old Bulk Redirect harder to spot
  • Migration validation focused on DNS and origin health instead of edge redirect behavior

Step-by-Step Fix

  1. Test the exact URL that still redirects and record the source hostname, path, and destination, because you need the real matching pattern before changing any Cloudflare rule.
  2. Check the Cloudflare Bulk Redirect list entries tied to that domain and confirm whether any still reference the old site, because one stale target can keep overriding an otherwise correct migration.
  3. Review which redirect rule or ruleset attaches the Bulk Redirect list to live traffic, because a cleaned-up list does not help if another attached rule still serves the old behavior.
  4. Compare the redirect match conditions with the hostname and path used after migration, because broad patterns often keep catching traffic that should now stay on the new site.
  5. Check for overlapping Redirect Rules, Page Rules, or Always Use HTTPS behavior in Cloudflare, because multiple redirect layers can mask which one still points to the old destination.
  6. Update or remove the stale Bulk Redirect entry at the actual matching source, then retest the exact URL, because changing unrelated DNS or origin settings will not fix an edge redirect that still fires first.
  7. Test more than one affected hostname or path after the change, because Bulk Redirect lists often cover multiple patterns and one stale entry may not be the only leftover.
  8. Compare results from a clean browser session and another network, because cached 301 behavior can make the redirect look unchanged after the Cloudflare rule is already fixed.
  9. Document the final Cloudflare redirect inventory for the migrated domain, because edge-level redirect rules are easy to miss during future cutovers.