Skip to main content
Drupal is a registered trademark of Dries Buytaert
Release: OpenID Connect / OAuth client 3.0.0-alpha9 New alpha version released for module openid_connect (3.0.0-alpha9). Usage Milestone: Google Analytics Module google_analytics crossed 1,000 active installs. Release: Timelinr 1.0.1 Minor update available for module timelinr (1.0.1). Release: GraphQL Compose Codegen 1.1.2 Minor update available for module graphql_compose_codegen (1.1.2). Release: Mapy.com 1.1.3 Minor update available for module mapycom (1.1.3). Release: Ckeditor5 entity browser 3.0.3 Minor update available for module ckeditor5_entity_browser (3.0.3). Release: Ckeditor5 entity browser 3.0.1 Minor update available for module ckeditor5_entity_browser (3.0.1). Release: Ckeditor5 entity browser 3.0.2 Minor update available for module ckeditor5_entity_browser (3.0.2). Release: Teamleader Integration 4.0.2 Minor update available for module teamleader (4.0.2). Module Revived: Entityqueue Buttons 1.1.2 Module entityqueue_buttons updated after 8 months of inactivity (1.1.2).

LocalGov Legacy Migration

Security covered Drupal 8–9 · not 10, 11 Localgov ecosystem
View on drupal.org

This module provides example migration configurations to help move content from old Drupal sites into LocalGov Drupal. It includes YAML files that map old entity and field names to their new equivalents, facilitating the transfer of data.

This is an example module to help demonstrate migration from old Drupal sites into LocalGov Drupal.

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.

Depends on

Dependencies of the latest stable release

Required by

Tracked projects that depend on this one

No tracked projects depend on this one yet.

Activity

Tracked releases
2
Tracked since
Mar 2025
Latest release
1 year ago
Releases (12 mo)
0 ▼ from 2
Maintenance
Dormant

Releases

Version Type Core Release date
0.1.1 Stable 8–9 Mar 13, 2025
0.1.0 Stable 8–9 Mar 13, 2025