localgovdrupal / localgov_legacy_migration
Migration for legacy Croydon and BHCC websites.
Installs: 2 573
Dependents: 0
Suggesters: 0
Security: 0
Stars: 0
Watchers: 7
Forks: 1
Open Issues: 10
Type:drupal-module
Requires
- drupal/migrate_drupal_d8: ^1.0@beta
- drupal/migrate_plus: ^5.1
- drupal/migrate_tools: ^5.0
- drupal/redirect: ^1.6
- dev-master
- dev-feature/bhcc-site-specific
- dev-feature/d9-support
- dev-fix/d9-support
- dev-feature/croydon-site-specific
- dev-feature/33-replace-campaigns-with-subsites
- dev-feature/incremental-migration
- dev-feature/24-more-migration-groups
- dev-feature/7-revisions
- dev-fix/2-content-moderation
- dev-feature/12-file-migration
- dev-develop
- dev-feature/16-campaigns-migration
- dev-feature/16-path-aliases
- dev-feature/15-directory-migration
- dev-feature/11-basic-migration
- dev-fix/3-4-5-initial-migration-fields
This package is auto-updated.
Last update: 2024-12-13 16:45:49 UTC
README
YAML files with previous and new entity names, field name mappings, and where appropriate migration of data from/to different fields.
Running these Drupal 8 migrations can be done in two ways:-
The first is how they are presently set-up. Migrating from one database to another. This requires the SQL based migration source available at https://www.drupal.org/project/migrate_drupal_d8 The additional work required would be to add missing migrations for entities not documented such as Users.
The second way is to migrate within the exisiting database. The source
class for these migrations is based on the Entity API and is in Drupal core.
The source in the YAML wants to be changed from d8_node to
content_entity:node and so forth.
Both methods at the moment only handle the currently live revision of an entity.