A defensible migration route
Upgrade-in-place, staged migration and rebuild options are compared against the actual estate.
All support services
Plan the next supported Drupal chapter
Turn an overdue Drupal upgrade into a controlled migration plan.
We assess the current build, content, modules and integrations before choosing what can be upgraded, replaced or redesigned.
No passwords needed for the first conversation.
What this service is for
Major Drupal upgrades are application projects, not oversized patch updates. Webmasters.my helps organisations define the route, dependencies, risks and testing needed.
The change we are working towards
From uncertainty to a website your team can confidently own.
Known dependencies
Content types, modules, integrations, custom code and editorial needs are identified before build work.
Testable acceptance
Critical journeys and content are defined so the new platform can be verified, not merely launched.
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
Discovery
Understand the existing application and organisational needs.
- Version and module inventory
- Content model review
- Custom code and integrations
- Editorial and operational requirements
02
Migration planning
Define what moves and how.
- Target architecture
- Migration mapping
- Replacement decisions
- Risk and sequencing plan
03
Delivery and transition
Build, verify and prepare the team for handover.
- Development and migration
- Functional and content checks
- Launch planning
- Documentation and ongoing care
How we begin
Understand first. Then change what is safe to change.
Assess before estimating
We review the real site and dependencies instead of treating every Drupal migration as equivalent.
Agree on the target
Scope, architecture, content handling and acceptance criteria are documented.
Migrate in controlled stages
Build, data movement, testing and launch follow a route suited to business continuity.
A good fit for
- Unsupported or ageing Drupal sites
- Drupal websites due for redesign
- Complex content and integration migrations
- Organisations needing a documented handover
Important boundaries
- A major-version migration cannot be accurately scoped from the public website alone.
- Not every contributed or custom module has a direct equivalent.
- Content cleanup and redesign are separate decisions even when delivered in the same programme.
01Is a Drupal major upgrade just a software update?+
Usually not. Major upgrades can affect modules, custom code, content models, themes, integrations and hosting requirements, so discovery and testing are essential.
02Can content be migrated automatically?+
Often much of it can, but mappings, media, revisions, relationships and inconsistent legacy content need review. We validate the migration route against the actual model.
03Should we redesign at the same time?+
It can be efficient, but it also adds decisions and testing. We help separate technical necessity from optional design improvement so the scope stays clear.
04Can the existing site remain online during migration?+
Typically yes, with a planned content-freeze or final synchronisation window. The exact transition depends on how frequently content and data change.
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