Migrations do not work with newer version of Drush that are incompatible with migrate_tools

Created on 9 June 2025, 5 days ago

Problem/Motivation

Migrate modules require the migrate_tools module which is not installed with newer versions of drush because most of the features have been integrated into drush.

Proposed resolution

Remove the dependency for migrate_tools from the migration modules.

🐛 Bug report
Status

Active

Version

2.0

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @joshua-jake
  • Merge request !22Resolve #3529194 "Migrations do not" → (Closed) created by joshua-jake
  • Pipeline finished with Success
    5 days ago
    Total: 436s
    #517892
  • ivnish Kazakhstan

    Hi joshua-jake! I'm using the latest drush and I have no problem with migrate_tools

    Can you explain your issue and add steps to reproduce?

  • My apologies for not being more clear. Migrate_tools is not completely incompatible with the latest versions of drush just unnecessary and over-rides the built-in functionality that has been more recently upgraded in drush 13. Nearly all the functionalities of migrate_tools have been implemented (at least the ones used by these migrations) and makes the use of migrate_tools redundant. In my case drush 13 built in functions run migrations much faster with larger migration than the migrate_tools (read 2 million plus records to reproduce), trimming literal days off of migration processes (not for privatemsg specifically but for all of my migrations). Since migrate_tools is no longer required (as the functionality is built into drush) it seems logical to remove the dependency from the migration modules.

Production build 0.71.5 2024