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

Destination classes

Each Migration implementation needs to create a destination object - a subclass of MigrateDestination (or its subclass MigrateDestinationEntity) - representing the Drupal object to be created during migration. Most destination classes accept an options array, containing settings which affect how the destination is constructed.

The MigrateDestination classes will also call handlers (subclasses of MigrateDestinationHandler) to process destination objects and the fields. See the handlers doc page for more information on the handler classes.

When using the Migrate Extras module, a number of extra destination handlers are provided. This module also makes it possible to specify a custom entity as a destination through MigrateDestinationEntityAPI.

Menus

Documentation for MigrateDestinationMenu and MigrateDestinationMenuLinks will be added here at some point.

MigrateDestinationComment

To migrate content into Drupal comments, use the MigrateDestinationComment class:

MigrateDestinationEntityAPI

The Migrate Extras module, provides the MigrateDestinationEntityAPI so you can specify a custom entity as a destination.

MigrateDestinationFile

File classes

MigrateDestinationNode

To migrate content into Drupal nodes, use the MigrateDestinationNode class:

MigrateDestinationNodeRevision

To migrate content into Drupal node revisions, use the MigrateDestinationNodeRevision class (assuming you've already migrated the nodes

MigrateDestinationRole

To migrate user role information into Drupal roles, uses the MigrateDestinationRole class:

MigrateDestinationTable

An easy way to simply migrate into a Drupal table (i.e., one defined

MigrateDestinationTerm

To migrate content into Drupal taxonomy terms, use the MigrateDestinationTerm class:

MigrateDestinationUser

To migrate user accounts into Drupal, use the MigrateDestinationUser class:

Guide maintainers

mikeryan's picture