Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.This project is not covered by Drupal’s security advisory policy.
This module is unsupported due to a security issue the maintainer didn’t fix. See SA-CONTRIB-2015-070 - Mover - Cross Site Scripting (XSS) - Unsupported for details.
If you want to use this module, your options are:
If you want to use this module, your options are:
- Choose another, actively maintained module instead
- File an issue in the queue with a patch to fix the module and then contact the security team to have your version reviewed and the project handed over to you following the unsupported project process.
- Hire someone to fix the security bug so the module can be re-published (see this guide on how to hire a Drupal site developer)
The Mover modules provide the ability to move content between Drupal sites. Out of the box this module supports nodes, users, taxonomy terms, URL aliases, and path redirects. The module currently supports D6 to D6 and D6 to D7. Drupal 7 exporting (for D7 to D7 migrations between different site builds) will be coming next.
This module has similarities to other migration modules, and is most similar to Node export which was the foundation for it's creation, but this module is significantly different than others. One major difference from Node export is that this module writes to separate text files for each piece of content, which is better for PHP memory usage during a batch import. Another difference is that Node export doesn't migrate users.
Compared to other migration modules a big difference is that the Mover module UI is only used for running processes, not for configuring or mapping data. All data mapping is done with custom modules that implement the appropriate hooks. The advantage is that programmers who learn the API can very quickly write complex migration scripts. No UI can account for all the possible options needed for a complex migration.
This module can be used by anyone for very simple content moving operations (such as between staging and production on a site), but the real power is the very flexible API for very large and advanced content migrations between completely different Drupal installations.
Mover Import can also be used for importing of content from other platforms, such as WordPress, if a separate script is written to generate similar data files (which are based on PHP objects). There are data preprocessing hooks in Mover Import that can be used to transform raw data objects into objects that look like Drupal objects.
Mover Import and Export are both Drush enabled as well. Here's an example of how to import nodes using Drush:
drush mover-import --process=import_nodes --start=1 --number=100 --progress
If a process isn't completed in a single call to the Drush script, you can
omit the --start and --number parameters and use --continue to resume the process:
drush mover-import --process=import_nodes --continue --progress
MOVER FOR DRUPAL 7: The Drupal 7 version is in progress. The current status is that you can import nodes, users, and terms that were exported with the Drupal 6 version of Mover, however some of the advanced features haven't been implemented yet. Mover Export functionality has also not yet been converted to Drupal 7. Please help by testing and reporting any issues!
Development sponsored by Digital Deployment
Based on work from Node export by danielb, James Andres, and chia
Project information
Unsupported
Not supported (i.e. abandoned), and no longer being developed. Learn more about dealing with unsupported (abandoned) projects- No further development
No longer developed by its maintainers. - Project categories: Import and export
- Created by benshell on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
