Tag1 Rebuilds Drupal LMS While Keeping Union Training Platforms Running

A Hybrid Migration Preserved Courses, Learner Records and Live Services
Case study graphic titled "Rebuilding Without Starting Over" with the subtitle "How Tag1 modernised Drupal learning platforms while preserving existing courses and learner records." A blue illustration shows "Drupal Sites" connected to three separate websites labeled "site1.example.com" "site2.example.com" and "site3.example.com". The graphic features the "CASE STUDY" label alongside the "TAG1" and "THE DROP TIMES" logos and the website "https://www.thedroptimes.com/".

Tag1 Consulting rebuilt a heavily customised Drupal learning management system while keeping training services available to members of the American Federation of Teachers (AFT) and AFL-CIO. In a technical account published on 11 November 2026, senior Drupal engineer Marcin Grabias describes how the team extracted legacy Opigno code, replaced tightly coupled course logic and migrated learner records into the contributed Drupal LMS project without first replacing the sites or their databases.

The work spans several years rather than a single deployment. According to Tag1, Share My Lesson, an AFT platform with more than two million registered educators, needed e-learning added to its existing Drupal site, while AFT eLearning and AFL-CIO’s LaborLab relied on established training structures and histories. The existing Opigno distribution could not simply be installed over Share My Lesson’s database, prompting a shift toward reusable Drupal modules. The figures and project outcomes in the account are Tag1’s reported results, not independently reproduced benchmarks.

From an Opigno Distribution to Owned Code

Tag1 originally adopted an early Drupal 8 version of Opigno for courses, activities and Group-based membership. Over time, interdependent submodules, locally maintained patches and legacy data patterns complicated upgrades. Grabias reports that on 14 September 2022, colleague Nat Catchpole removed Composer dependencies on opigno_learning_path and opigno_module and moved 665 files containing more than 100,000 lines from contributed to custom code. This gave the team direct control of changes while it developed a replacement.

The next step was to separate course decisions from presentation code. Starting with a 51-line service class committed in October 2022, Grabias expanded TrainingManager over approximately 18 months and more than 70 targeted commits. It came to manage learner progress, navigation, prerequisites, scoring and maintenance operations. Tag1 says functionality previously scattered across nearly 6,000 lines of navigation and tracking code was consolidated into roughly 1,000 lines of service code. Forms and controllers could then call a central service rather than each implementing course rules.

Group Module Changes Reached the Database

The legacy platform had remained on an early Group 1.0 release candidate for years. Moving toward Group 3.x in early 2024 required addressing changes from group_content and group_content_type to group_relationship and group_relationship_type. Tag1 reports that the change affected database tables, entity hooks, queries and Views relationships used by course rosters and gradebooks.

The account credits Group maintainer Kristiaan Van den Eynde with providing an update hook that reduced the need for a full migration of Group data. This distinction matters: the team still had substantial integration and schema work to complete, but the source does not support describing it as an entirely manual replacement of every Group record. The project also benefited from newer Group integration with Drupal access and caching mechanisms, according to Tag1.

Two LMS Implementations Ran Side by Side

By spring 2024, the refactored custom code was serving production users, and Grabias began turning the replacement into the open-source Drupal LMS project. The rewritten architecture adopted typed plugins, PHP attributes, Single Directory Components and structured answer storage rather than preserving the inherited procedural implementation.

In June 2025, Tag1 adopted a hybrid repository strategy. Its working 0.2.x LMS implementation remained in web/modules/custom/lms/, while the modern contributed code was developed in web/modules/contrib/lms/ within the same repository and database environment. Tag1 says the arrangement allowed ongoing training and assessment activity while developers prepared the replacement. Contributors including Claudiu Cristea, Oberon Ray and Nat Catchpole worked on dependency injection, components, activity plugins and caching. This was a project-specific approach, not a general instruction to enable two packages with the same module identifier on an ordinary Drupal site.

Migrating Learning History Without Rebuilding Every Record

Developer Mauricio Dinarte built the LMS Migrate pipeline to transfer course structures and learning history in place. Because the existing user accounts, files and media remained in the same Drupal databases, they did not need to be copied into a separate destination site. Migration plugins could also call existing application APIs to reconstruct learning states not stored in a straightforward entity table.

Course URLs needed special handling. Tag1 says its migration moved legacy aliases under an administrative prefix, assigned familiar public aliases to replacement LMS course entities and created 301 redirects where paths differed. The pipeline was also adapted to populate revision fields after versioning requirements emerged during development. These details make URL preservation, historical status calculations and revisions essential parts of the case study, rather than peripheral considerations.

The public LMS Migrate project provides reusable migration foundations, but it should not be described as a universal, production-validated replacement for a site-specific migration plan. Drupal.org lists a 1.0.0-alpha2 release dated 21 July 2026 and notes that the project is not covered by the Drupal Security Team advisory policy.

What the New Drupal LMS Architecture Provides

Grabias also documents technical features of the replacement: Drupal Form API and AJAX modal subforms for nested course editing; session-backed storage for anonymous learners’ attempts, with later persistence when they authenticate; and plugin-supplied field configuration for individual learning activity types. These are architectural descriptions from the implementing team, not independent measurements of security or performance.

Tag1 reports that the broader codebase was reduced from more than 100,000 lines of legacy code to approximately 40,000 lines of modern PHP. The Drupal LMS project page now lists stable version 1.2.6, released on 13 November 2026, after the 1.2.5 release cited in the original draft. The stable status of Drupal LMS does not extend automatically to the separate alpha-stage migration project.

A Retrospective on Migration Risk

Grabias presented the work at DrupalCon Rotterdam on 30 September 2026. The conference materials describe an in-place production migration completed earlier in 2026, making the November article a detailed retrospective rather than an announcement of a new rollout. Tag1 describes keeping production training available throughout the transition; its public account does not publish independent availability audits or a migration-by-migration validation dataset.

The case illustrates a method for replacing highly customised Drupal software without discarding an established site: first secure control of the legacy code, isolate business rules, accommodate dependency and schema changes, run the replacement alongside existing functionality, and migrate records in place. The approach required multiple years of engineering and custom migration work; it does not establish that other Opigno or Drupal LMS installations can follow the same path without significant adaptation.

See something incorrect?
Help us improve this page.
Let us know

Disclosure: This content is produced with the assistance of AI.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.

Related Organizations

Upcoming Events

Latest Opportunities