This project is not covered by Drupal’s security advisory policy.
Workbench Moderation Migrate migrates Drupal 7 Workbench Moderation flows to Drupal 9 and alters node revision migrations to migrate them with the right moderation state.
Requirements
- Migrate Drupal (included in Drupal core)
- Node (soft dependency, included in Drupal core)
- Content Moderation (included in Drupal core)
- Applied core patch #1: #3200949-9: Non-default entity revisions are migrated as default revision because EntityContentComplete does not allows creating forward (and non-default) revisions
- Applied core patch #1: #3052115-32: Mark an entity as 'syncing' during a migration update
Core patch required for being able to update previously migrated records with
1. Core Migrate API with highwater property, or
2. Migrate Tools with its --update
opt:
Usage
- Enable this module and Migrate Drupal UI.
- Visit
/upgrade
and configure your Drupal 7 source database. - Perform the upgrade!
Workbench Moderation Migrate module supports only complete node migrations (their plugin ID is d7_node_complete:<node_type>
).
The migrate import command in Drush 10.4+ (or Migrate Tools) aren't building migration dependency graph[1], they're running both the complete[2] and deprecated[3] node migrations, causing data integrity problems. Please keep this in mind if you don't use Drupal core's Migrate Drupal UI.
Footnotes:
- [1]: At the end this means they're executing the migrations in incorrect order and also executing migrations which should be skipped.
- [2]: Complete node migrations are the migrations with ID
d7_node_complete:<node_type>
. - [3]: Deprecated node migrations are the migrations with IDs
d7_node:<node_type>
,d7_node_revision:<node_type>
ord7_node_translation:<node_type>
.
Project information
- Module categories: Import and Export
- 20 sites report using this module
- Created by huzooka on , updated
- This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.