>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3629607. --> Reported by: [shaker-gspikes](https://www.drupal.org/user/3871146) >>> <p>Migrate Redirect Map builds the 301 redirects a Drupal 7 to Drupal 10/11 migration needs and reports, before launch, which legacy URLs would return 404. It reads the migrate map tables of the node, taxonomy term, user and media migrations (both d7_node_complete:bundle IDs and the upgrade_d7_* IDs written by the Migrate Drupal UI), the legacy url_alias table and the legacy redirect table, resolves each legacy path to the alias the migrated entity actually has on the new site, and classifies it as redirect / identical / already exists / unresolved. A dry run writes the full map to CSV; creation runs through the Batch API (or drush migrate-redirect-map:build) with loop protection and no duplicates. Drupal 7 translation sets (tnid) are followed, and aliases in a language the new site does not have become language-neutral redirects.</p> <h3>How it differs from existing solutions</h3> <ul> <li>The Redirect module's d7_path_redirect migration only copies redirects that already existed on the Drupal 7 site. It does nothing for aliases that changed because entity IDs were renumbered or because Pathauto patterns changed.</li> <li>Core's d7_url_alias migration copies the old aliases, which keeps old URLs working only when nothing else changed; it cannot tell you which paths now resolve nowhere.</li> <li>This module compares legacy paths with the new site's real aliases after the migrations and alias generation have run, creates a redirect only where the URL actually changed, and gives a list of unresolved paths (views, custom callbacks, file paths) so they can be mapped by hand before launch.</li> </ul> <h3>Manual reviews</h3> <ul> <li><a href="https://www.drupal.org/project/projectapplications/issues/3607891#comment-16801931">https://www.drupal.org/project/projectapplications/issues/3607891#comment-16801931</a> ([1.0.x] JSON-LD Generator)</li> <li><a href="https://www.drupal.org/project/projectapplications/issues/3609892#comment-16801932">https://www.drupal.org/project/projectapplications/issues/3609892#comment-16801932</a> ([1.0.x] Universal AI Provider)</li> <li><a href="https://www.drupal.org/project/projectapplications/issues/3573362#comment-16801935">https://www.drupal.org/project/projectapplications/issues/3573362#comment-16801935</a> ([1.0.x] Emporiqa)</li> <li><a href="https://www.drupal.org/project/projectapplications/issues/3623357#comment-16809215">https://www.drupal.org/project/projectapplications/issues/3623357#comment-16809215</a> ([1.0.x] wxrks TMGMT Connector)</li> <li><a href="https://www.drupal.org/project/projectapplications/issues/3627905#comment-16809217">https://www.drupal.org/project/projectapplications/issues/3627905#comment-16809217</a> ([1.0.x] Smart Redirects Manager)</li> <li><a href="https://www.drupal.org/project/projectapplications/issues/3630186#comment-16809218">https://www.drupal.org/project/projectapplications/issues/3630186#comment-16809218</a> ([1.0.x] Magic HTML Mail)</li> </ul> <h3>Project link</h3> <p><a href="https://www.drupal.org/project/migrate_redirect_map">https://www.drupal.org/project/migrate_redirect_map</a></p>