Description: Migrate Extras is a package of files that integrate the Migrate Module with many of the non-core modules available for drupal, allowing you to import content from other modules, older versions of drupal, or a non-drupal CMS.
Hear Awesome Lullabot Podcast: Migrate mentioned at 1h:19m
Master Node Map Table - If you are importing more that one node content set, then this is helpful because it will store all mappings to the master node map table, which makes it easier to import things like comments and files in their own content sets. You have to setup the relationship in tw if you want to use this with views.
Current Integrations / Submodules
IMPORTANT: Make sure the major version of Migrate Extras matches the major version of Migrate! That is, with Migrate 1.x use Migrate Extras 1.x; with Migrate 2.x use Migrate Extras 2.x.
Migrate 2: For compatibility between Drupal 6 and Drupal 7 implementations of Migrate 2, all features in core for Drupal 7 are supported by the Migrate 2 module itself on both 6 and 7. Notably, that means while CCK support was in migrate_extras for Migrate 1, it is in migrate itself for Migrate 2.
Migrate 1: All non-core-drupal integrations have been moved here as of 1/15/10. Make sure you are using Migrate module version 6.x-1.0-beta4 or later, as it implements the hook_migrate_api() needed for the integrations. All integrations are turned off by default, except for CCK (content). To enable, go to the migrate settings tab.
* Migrate Extras: Provides the integrations, plus:
o option to use all core user fields
o md5pass field: import pre-encrypted passwords.
* Content Profile
* Organic groups
* Email Registration
* Private Messages
* Location module
Integrations in development
These modules have been coded, but are in the process of being cleaned up before release.
* Userpoints - waiting on userpoints patch. #441678: Use drupal_write_record(). Needed to be able to import transactions with migrate_extras
* User Relationships
* Location: still need to do location_user and location_cck
If you need to import content for a module not listed here, you can add a feature request to the issue queue, or you can use these modules as an example of the migrate api and write the module yourself. Creating these integration modules is usually straight forward, but may require a proper understanding of a contrib module's apis, along with their features and limitations. For more information on the migrate api, see the Migrate Documentation. If you end up with something useful, please contribute it back. All contributions to this project are greatly appreciated.
In the future, these integrations will be submitted back to the actual modules that use them . That way the integrations will be maintained by the same people who maintain the modules and will be bundled with the module itself. Adding an integration is now easy with the new hook_migrate_api() function. You just have to implement a few lines of code in your module, and put the integration code in MYMODULE.migrate.inc somewhere inside your module folder.
Be careful with your data! Back it up
The Migrate module's apis are pretty solid now but it is still in beta, so things may still change. Modules that Migrate Extras integrates with are changing all the time as well. What this means for you is that you should make careful backups of all your data before enabling this module.
Related: migrate, Module, Modules, integrations, extras, Import, Content, drupal, Version, Integration, means, hook migrate api, major, careful, things
O/S:BSD, Linux, Solaris, Mac OS X
File Size: 20.5 KB