The migrate module provides a flexible framework for migrating content into Drupal from other sources (e.g., when converting a web site from another CMS to Drupal). Out-of-the-box, support for creating core Drupal objects such as nodes, users, files, terms, and comments are included - it can easily be extended for migrating other kinds of content. Content is imported and rolled back using a bundled web interface (Migrate UI module) or included Drush commands (strongly recommended).
I'm afraid I've been very busy with project work and the Migrate in 8 effort and haven't been able to put Migrate 2.6 to bed yet. I'll take occasional stabs at catching up on the issue queue, prioritizing bugs>support requests>tasks/feature requests. And, looking at the overall Migrate ecosystem, migrate>migrate_d2d>wordpress_migrate.
Migrate 2.6 Release Candidate 1 is available. The main theme of this release is UX - the existing UI has been significantly rearranged, and a new API has been introduced to allow other modules to easily developed wizard-style UIs targeted to non-developers.
The most significant changes in Migrate 2.6:
For a more complete list of changes, see the issues tagged as Migrate 2.6.
Besides the UI changes, there are significant changes around migration registration and construction that are somewhat risky - before upgrading to the latest -dev or git code, be sure you backup your database. Please report any problems you have in upgrading in the issue queue - we want to be sure the upgrade to the final 2.6 release is as clean as possible.
Support for contributed modules
The place to implement migration support for a contributed module is in that module, not in the Migrate module. That way, the migration support is always self-consistent with the current module implementation - it's not practical for the Migrate module to keep up with changes to all other contrib modules.
Historically, if this did not seem practical, or as an intermediate step before submitting it to the contrib module itself, support for some contrib modules has gone into the Migrate Extras module. We're now deprecating this module - every effort should be put into integrating migration support directly into the target module.
Specialized migration modules
These modules use the Migrate framework to implement imports from specific sources.
- The Economist
- Stanford Law School
- National September 11 Memorial & Museum
- E-Business Platform for Basel Tourism
- Lifeguard Press osCommerce
- Elle Decor Lookbook App for iPad
- Andrew Morten's (drewish) slides and video from a Drupalcon Denver session explaining the Migrate module in technical terms.
- Mike Ryan's slides and video from a Drupalcon Denver session explaining the migration process in non-technical terms.
- Migrating old HTML files into Drupal, by Four Kitchens
Past sponsors include:
- GenomeWeb, and The Economist - Initial development of Migrate 1.
- Examiner.com - Initial development of Migrate 2 on Drupal 7.
- Martha Stewart Living Omnimedia - Backport of Migrate 2 to Drupal 6.
- World Economic Forum
- Warner Music Group
Thanks to Frank Carey for the Migrate Extras module.