How To Migrate My Drupal Site

Drupal migrations need version awareness. A Drupal 7 move, a Drupal 9/10 Composer project, and a legacy shared-host Drupal install have different file paths, PHP requirements, database assumptions, and cache rebuild steps.

Drupal Migration Checklist

• Detect the Drupal version from core files and database metadata before selecting the migration route.
• Move the codebase, public files, private files if present, database, and configuration files such as settings.php.
• Confirm Composer dependencies, PHP extensions, trusted host settings, file permissions, cron, and temporary file paths.
• Run cache rebuild and check admin login, content pages, forms, search, redirects, and media paths.

Common Drupal Blockers

Old PHP versions, missing extensions, private file directories outside the web root, hard-coded base URLs, large cache tables, and unsupported modules are the most common migration blockers. Migration Monkey flags these before the move when the source path can be scanned.

Use Migration Monkey

Start with the route finder, choose Drupal when detected, then use endpoint-to-endpoint transfer so the control plane tracks logs, warnings, and verification without storing the Drupal payload.