Download Size md5 hash
migrate-7.x-2.x-dev.tar.gz 4.26 MB fbc8d05ce74040c3371911379534c90c
migrate-7.x-2.x-dev.zip 4.43 MB 75c9fbabc085590ac83f1547d0e1889a
Development snapshot from branch: 7.x-2.x
Last packaged version: 7.x-2.2+89-dev
Last updated: February 6, 2012 - 00:23

A complete rewrite for Drupal 7. This is Independence Day for migrate. No longer do we depend on Views, Schema, and Table Wizard. In order to fetch data from the source tables, one provides a SQL query in your migration code.

Some other highlights:

  • A strong Drupal 7 citizen. We take full advantage of the new Fields in core, and the new DBTNG database layer.
  • Migrate has modelled itself after Feeds and Ctools. It supports an OO plugin system whereby new sources can be developed (imports from XML files, flat HTML files, etc.) and new destinations (email newsletter subscriptions, ubercart transactions, etc.).
  • Migrate is now a native drush application. Migration status, import, rollback, stop and so on are drush commands. There is no UI right now for importing via the web. We do expect to add that again in a migrate_ui module.
  • All configuration is in code. This makes deployment easy. For now, there is no UI based mapping of columns.
  • Migrate ships with a migrate_example module which is a complete example migration, including sample legacy data. This is our documentation, and it rocks. More tutorial based documentation is expected in the future.

The port to Drupal 7 has been sponsored in part by Examiner.com

Note that Migrate 2 is fundamentally architecturally different from Migrate 1 - there is no automated upgrade path. If you are currently using Migrate 1 on a project, you should stick with that - we encourage new projects to start with Migrate 2.

Once the API has settled down initial beta releases will be made available - in the meantime, there are development releases to play with but be warned that incompatible API changes continue to be made, so be very careful about updating your code.