Migrate Redirect Map

Migrate Redirect Map builds the 301 redirects a Drupal 7 to Drupal 10/11 migration needs and shows you, before launch, which legacy URLs would return 404.

Migrate Drupal moves the content but not the addresses. This module reads the migrate map tables of your node, term, user and media migrations, the legacy url_alias table and the legacy Redirect table, resolves every old path to the new entity's alias, and classifies each one: redirect, unchanged, already redirected, or unresolved. A dry run gives you the full CSV; one more click (or one Drush command) creates the redirects in batches, with no duplicates and no loops.

Features

• Handles core d7_node_complete:bundle migrations and the upgrade_d7_* migrations created by the Migrate Drupal UI
• Follows Drupal 7 translation sets, so translated nodes land on their migrated source node
• Re-points redirects the Drupal 7 site already had, keeps external ones
• Per-language aliases; languages the new site does not have become language-neutral redirects
• Unresolved paths (views, custom callbacks, files) are listed, never guessed
• Admin UI with batch creation at Configuration » Search and metadata » Migration redirect map, plus drush migrate-redirect-map:build
• CSV export of the whole map for sign-off before launch

Requirements

Drupal 10.3+ or 11, the Redirect module, and the migrate database connection Migrate Drupal already uses. Drush 12.5+ or 13 for the command (optional).

Usage

Run it after the content migrations and after the new aliases exist. Dry run first, read the unresolved rows, then create. Full instructions are in the README.

Maintained by Gspikes, who run Drupal 7 to 11 migrations and publish the State of Drupal 7 census.