Download migrate-6.x-2.x-dev.tar.gztar.gz 260.04 KB
MD5: 48b9e6dde39dc3b082390ccc8f370d10
SHA-1: 940d90dac9b602311fc461eb24b9bb4161b9506b
SHA-256: 0fa227c35df575c3abc69299f67e3b86c68dab1d9a3109db507863de582395f7
Download migrate-6.x-2.x-dev.zipzip 300 KB
MD5: cc344855cec1da40c2ce4610150cef0c
SHA-1: 1d39eca0ab79f2bda2aaddfc4e01c65ea777edb1
SHA-256: 558308b009acb3e7ad030c14cb2d65701f0241817048fc9f0d736d23ff48a692

Release info

Created by: mikeryan
Created on: 26 May 2010 at 19:34 UTC
Last updated: 6 Jul 2016 at 20:22 UTC
Core compatibility: 6.x
Release type: New features

Release notes

A complete rewrite of the Migrate module. 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:

  • 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 initial development of Migrate 2 has been sponsored in part by

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.


The selected release is the release that will be used for automated testing. Optional projects are only used for testing.



No optional projects