https://github.com/localgovdrupal/localgov_legacy_migration
Documentation of field and entity changes in the form of Drupal Migration YAML
https://github.com/localgovdrupal/localgov_legacy_migration
Last synced: 3 months ago
JSON representation
Documentation of field and entity changes in the form of Drupal Migration YAML
- Host: GitHub
- URL: https://github.com/localgovdrupal/localgov_legacy_migration
- Owner: localgovdrupal
- Created: 2020-06-22T07:56:19.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2022-05-13T10:56:00.000Z (about 4 years ago)
- Last Synced: 2025-02-20T09:44:36.903Z (over 1 year ago)
- Language: PHP
- Size: 124 KB
- Stars: 0
- Watchers: 7
- Forks: 1
- Open Issues: 10
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Testable Entity and Field Documentation - Migration
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.