Advertising sustains the DA. Ads are hidden for members. Join today

Contributed module support

Many contributed Drupal modules are responsible for maintaining data - they define new field types or entity types, or maintain custom tables of their own. Usually to migrate data into these modules will require custom support (in the form of destination plugins and/or field handlers) to be programmed. Ideally the contributed module itself will implement this support, although some modules are still supported by the Migrate Extras module. This section of the Migrate documentation is the place to document the support for contributed modules (one subpage per module).

Address Field

In your migration class, pass the country value (two-letter ISO country code) as the primary value (i.e., mapped directly to the field

Geolocation field

This patch for Geolocation field module provides a destination handler which exposes geolocation fields for mapping.

Metatag

The Metatag module provides a destination handler which exposes all configured metatag fields for mapping. Making use of the handler is

Migrate Field Collections

This page will describe the process of migrating field collections.

MigrateDestinationCommerceProduct

The contrib module Commerce Migrate provides a few destination classes that extend the Entity API destination class provided by Migrate

Organic Groups

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

Pathauto

By default, if you have the Pathauto module enabled and relevant patterns defined for your content, those patterns will be used during

Range

The Range module provides a destination handler which exposes range fields for mapping.

Guide maintainers

mikeryan's picture