eComHut helps organisations build, improve and migrate Drupal websites where content structure, editor workflow and long-term maintainability matter. Work can cover new Drupal development, upgrades, migrations, custom modules, integrations, forms, search and content architecture. The starting point is the current site and publishing model rather than an assumption that every project should become headless.
Drupal development services
- Content types, fields, taxonomy and reusable content structures.
- Views, listings, search, forms and role-aware editor workflows.
- Theme and template improvements with semantic, accessible markup.
- Custom module development where contributed modules or configuration are not enough.
- External API integrations and JSON:API or decoupled delivery when the business case supports it.
- Technical SEO foundations including metadata, canonicals, redirects and structured page hierarchy.
Drupal upgrade planning
An upgrade should be planned around the current core version, PHP/runtime, Composer dependencies, contributed modules, custom modules and theme behaviour. Compatibility is checked before production work begins so deprecated code, abandoned modules and theme assumptions do not become surprises late in the release.
Upgrade work can include dependency review, custom-code remediation, configuration changes, representative regression testing and launch verification for content editing, forms, search, navigation, permissions and integrations.
Drupal migration services
A migration needs more than a node count. The work maps content types, fields, taxonomy, users and roles where needed, files/media, menus, forms, metadata and URLs. Representative source records are compared with the destination before cutover, and important historical URLs are mapped to real equivalents where the structure changes.
- Source-content inventory and ownership decisions.
- Field, taxonomy and media mapping.
- Module and feature parity decisions.
- URL/redirect mapping and metadata checks.
- Editor acceptance and permissions testing.
- Launch validation for high-value pages, forms, menus and search.
Editor experience and content governance
A technically clean Drupal build can still be difficult to operate if editors need developer help for routine content. eComHut can review reusable components, permissions, moderation, content relationships and page-building patterns so the CMS reflects how the organisation actually publishes.
Headless and hybrid Drupal
Drupal can work well as a structured content backend for another frontend, but decoupling adds responsibilities for preview, routing, caching, search, analytics and deployment. A headless architecture should be chosen because those trade-offs help the business, not because it is fashionable. Conventional or hybrid Drupal remains a strong option when it keeps publishing simpler.
Integration and migration risk
Forms, identity, search, analytics, CRM handoff and external APIs should be included in the dependency map before an upgrade or migration. A migration is not complete because pages render; editors, URLs, forms and downstream systems must still work.
Typical deliverables
Deliverables can include a Drupal audit, upgrade plan, module compatibility review, content model, migration map, custom code, API contracts, test evidence, redirect mapping and release checklist. Hosting migration, large-scale content rewriting and third-party licences are separate unless included in scope.
Discuss a Drupal project
Send the site URL, current Drupal version if known, editor pain points, important modules and whether the goal is development, support, upgrade, migration or restructuring.
Discuss Drupal development