Migrate Run
Component type
Categories
Maintenance status
Development status
Downloads
Component created
Component changed
The Migrate Drush Runner
Credits
This is a fork of Migrate Tools Drush runner. All credits goes to Migrate Tools team.
This is a fork of Migrate Tools Drush runner. All credits goes to Migrate Tools team.
This module asking API facebook for wall message from 1 to multi account and render a JSON unified listing of messages.
It's under active development and will deliver quickly
This module is extending the current Feeds module with a new fetcher and parser plugin for Cision feeds.
This module provides ability to migrate your bibliographic data from the Bibliography (biblio) module (Compatible with 6.x and 7.x versions).
Import nodes or taxonomies using spreadsheet files. Supports CSV asd xls file formats.
The module allow to manage importers and their field mapping. Importers are configurable entities. The module can be extended using plugins:
Import and conversion of REST resources into Drupal 8 entities.
Currently, only JSON is supported, further development can include XML and HAL.
The scope of the operations are create, update, delete.
It is based on a mapping defined in in the EntityMapper class that
It's a starter kit that might save some migration cost.
It might also be interesting for the sample data and
even for non Drupal destinations (although the generated
intermediate csv is strongly tailored against Drupal).
This module enables creation of media entities during a core D6->D8 upgrade.
It creates one media entity per file entity, autopopulating mimetype and owner uid, and using bundles and media providers to fill in other fields (e.g. image width and height).
Multiple configuration destinations are often used to store configuration specific to environment or even to separate on a site-by-site basis.
A common workflow is to leverage "sync" (the default and out-of-the-box configuration destination) as the destination for storing shared/global configuration. Overridden and additional configuration is stored in subsequent configuration destinations. A config import with the "partial" option allows for the secondary destination to bring in only that which is overridden or added.
A deeper dive into this workflow:
This module helps in exporting and importing Menu Items among cloned sites which is not possible using CMI.
This module exports the menu entity as config YAML and will be imported on subsequent instances.