Poll migration

Polls contain bits that are not covered by regular node migrations. Here is a method that can be used to migrate Drupal 6 polls to Drupal 7. Updates and corrections are welcome.

First we add in the active and runtime columns from the poll table:

Process plugin: callback

This plugin allows source value to be passed to a callable that returns the processed value. It allows simple processing of the value, such as strtolower(). The callable takes the value as the single mandatory argument. No additional arguments can be passed to the callback as this would make the migration YAML file too complex.

Example of usage:

      plugin: callback
      callable: strtolower
      source: source_field


Migrating to Drupal 8 from a previous version

This is a stub page referenced from update.php in Drupal 8 core.

@see https://drupal.org/node/2168011

We will eventually need to document the process of migrating a Drupal 7 site to Drupal 8 using Drupal 8's migrate module.

For Example
Enable the migrate_drupal module, go to admin/structure/migrate/run , enter database credentials, the file path, click migrate configuration if succeeded continue with migrate content. If migrate configuration failed, reinstall, fix and try again.

Improving migration performance


Disable hooks during migration

Quite frequently, hooks defined by other modules firing during migration (as a result of node_save(), user_save(), etc.) cause various problems - most often it's simply a performance impact (use the timer instrument to identify these), but sometimes it's actually dangerous (such as sending email notifications). With Migrate 2.6 (currently this feature is in the development version only since it was added after 2.6-rc1), hooks belonging to other modules can be disabled in the migration configuration.

Organic Groups

This page has been written to be up-to-date with Organic Groups 7.x-2.2

Organic groups 7.x-2.x is built to work with the Migrate module (https://drupal.org/project/migrate). No additional modules is needed.


Create a migration class for your group entity or content type as you normally would using MigrateDestinationNode or your own MigrateDestinationEntity/MigrateDestinationEntityAPI subclass. On this entity you will have two fields which are related to Organic Groups, normally named group_group and og_roles_permissions.

  • group_group takes a value 0 or 1. 1 means that the node or entity is a group.
  • og_roles_permissions also takes a value 0 or 1. In this case, 1 means that the group may define its own roles and permissions.

In case you are happy with the default values for these fields applying to all your imported groups, you don't have to do anything. Your migration will just work. However, it is possible to change the default values:

// Organic Groups

Group content


Subscribe with RSS Subscribe to RSS - migrate