All support services

Drupal support for established websites

Keep Drupal supported, patched and workable for the people who rely on it.

We help organisations manage core and contributed-project updates, Composer dependencies, operational fixes and ongoing website needs.

No passwords needed for the first conversation.

What this service is for

Drupal maintenance requires awareness of supported versions, security advisories, dependencies and custom code. Webmasters.my brings these into a practical support rhythm.

The change we are working towards

From uncertainty to a website your team can confidently own.

01

Supported-version awareness

The site’s current branch and dependencies are reviewed against the platform’s support lifecycle.

02

Controlled patching

Updates are planned with backups, dependency review and checks suited to the website.

03

A route for inherited complexity

Custom modules, integrations and technical debt are surfaced instead of silently folded into routine work.

What we can cover

A clear scope around the work that matters.

Final coverage depends on the current website and the level of support agreed after review.

01

Core and project updates

Maintain the supported Drupal baseline.

  • Core patch updates
  • Contributed module and theme updates
  • Composer dependency management
  • Database update workflow
02

Operational support

Keep the website usable day to day.

  • Bug investigation
  • Content model and configuration support
  • Forms and integrations
  • Performance observations
03

Lifecycle planning

Prepare before a version becomes urgent.

  • Version and dependency inventory
  • Unsupported component review
  • Upgrade-readiness assessment
  • Prioritised technical recommendations

How we begin

Understand first. Then change what is safe to change.

1

Map the Drupal estate

We review versions, Composer setup, modules, custom code, environments and known issues.

2

Stabilise before routine care

Unsupported or overdue work is separated from the ongoing maintenance scope.

3

Patch, check and advise

Regular work follows an agreed workflow, with important lifecycle decisions raised early.

A good fit for

  • Corporate and public-information Drupal sites
  • Membership and organisational platforms
  • Drupal sites inherited from another vendor
  • Teams that need both maintenance and development support

Important boundaries

  • Unsupported Drupal branches may need an upgrade project before normal care is appropriate.
  • Custom and abandoned modules require individual review.
  • Highly critical advisories may require work outside the routine cadence.

Questions worth asking

Before we work on the website.

Ask about your situation
01Why does supported Drupal version matter?

Drupal Security Team coverage applies to supported versions. An unsupported branch may stop receiving standard security fixes, making upgrade planning part of responsible maintenance.

02Do you support Composer-based Drupal projects?

Yes, subject to reviewing the existing project structure, lock file, hosting workflow and custom dependencies.

03Can you maintain custom Drupal modules?

We can assess them. The code quality, documentation, dependencies and compatibility determine whether they fit routine support or need separate remediation.

04Can you take over from another Drupal agency?

Yes. We start with repository, hosting, environment and access handover, then document the baseline before ongoing work.

A useful first step

Let’s understand what your website actually needs.

Share the public website and the concern on your mind. A person from our Malaysian team will review the context and recommend a sensible next step.

Request my website review