Downloads

Download tar.gz 210.39 KB
MD5: 9bd7202a8a021295f05f39fd1ad6cbba
SHA-1: 7eb518fc20ce08a8b934156ab7f71ef585800073
SHA-256: fdb6cc710d1f9be151ec50c2fb69e65fe742de0f26706e4bbc4c3ac0f30cbf3b
Download zip 238.05 KB
MD5: e0ecf3e8ca3c63bc9e0751aab6bcd503
SHA-1: c8cdfcd044a53f887960055bd21924a5b46c221b
SHA-256: b2ad3d5cc570f667038e0053df0519cf6cd3ce724730090d7513578fd9696259

Release notes

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 Drupal nodes, taxonomy terms, comments, and
users are included. Plugins permit migration of other types of content.

Requirements
------------
Migrate 2 on Drupal 6 requires the autoload (version 2.x) and dbtng modules.

Usage
-----
For now, all we offer is documentation by example. Enable the migrate_example module and browse to admin/migrate to see its dashboard. The data for this migration is in migrate_example/beer.inc. Mimic that file in order to specify your own migrations. All imports/rollbacks/etc. are initiated by drush commands.

The Migrate module itself has support for migration into core objects. Support for migration involving contrib modules is in the migrate_extras module. The exception to this is CCK - because the equivalent (Field API) is implemented in core for Drupal 7, to ease maintaining both D6 and D7 implementations of Migrate 2 the CCK support is builtin under Drupal 6.

Upgrading
---------
Do not attempt to upgrade directly from Migrate 1 to Migrate 2! There is no automated path to upgrade - your migrations (formerly known as "content sets") must be reimplemented from scratch. It is recommended that projects using Migrate 1 stay with Migrate 1, and that Migrate 2 be used for any new migration projects.

Created by: mikeryan
Created on: 28 Nov 2010 at 23:18 UTC
Last updated: 12 Apr 2014 at 15:03 UTC
Unsupported

Other releases