Service
Drupal modernization & migration
Drupal 7, 8, 9 and 10 platforms moved onto Drupal 11. Content migrates in full, custom code gets rewritten where it has to be, and the cutover is planned around a site that stays live. The Day newspaper moved with more than 1.5 million entities intact.
Migrations go wrong in the same place every time: the content gets treated as a detail and the theme becomes the project. We audit the source schema first, every field and reference and half-used content type, decide what actually survives, then move it with a pipeline we can re-run on demand. The Day newspaper came across that way, more than 1.5 million entities, with redirects and metadata handled deliberately enough that its search rankings held through the switch. The other half of the job is the code: custom modules ported to current APIs, contrib swapped for what is still maintained, and the front end rebuilt on a supported base theme rather than carried across with its deprecation warnings intact.
Scope
How the work is delivered
-
Source audit
A full inventory of the existing site: content types, fields, references, taxonomies, files, users, redirects, plus what is genuinely used versus cruft. The output is a migration map with the decisions made explicitly before any code runs.
-
Migration pipeline
Migrate API source / process / destination plugins, version-controlled and idempotent. We can re-run the whole import on demand, which means it is tested against real content dozens of times before the real cutover.
-
Content & structure fidelity
Rich text rewritten for the new editor and media library, entity references re-pointed, taxonomy and menus rebuilt, and paths and redirects preserved so SEO and bookmarks survive. We diff source against target, field by field.
-
Theme & module modernization
Custom modules ported to current APIs, contrib swapped for maintained equivalents, and the front end rebuilt on a supported base theme. Deprecation warnings get fixed rather than left in the log.
-
Zero-downtime cutover
A rehearsed go-live: content-freeze window, final delta import, DNS and cache flip, smoke checks. Validated under production-like load beforehand so launch day has no surprises.
Talk through the build
Send the platform, constraints, and timeline. We'll reply with the engineering questions that decide scope.
- Reply within one business day, weekday hours UA / EU.
- 30-minute discovery call when it is useful.
- Scope written around deliverables, risks, and ownership.