Leading Low Cost Drupal Developers Sydney, Melbourne, Brisbane, Perth, Adelaide
Move the content and the addresses. Rebuild only what was custom.
For organisations whose website still runs on Drupal 7. We reduce the risk while it stays up, migrate the content to current Drupal or to something simpler, rebuild the custom parts, and keep every address working so search ranking survives.
More about this service
We are an Australian team working with businesses in the United States, the United Kingdom, New Zealand and Australia. Every engagement starts with a scoped technical assessment, so the estimate that follows is based on your code and your data.
- Assessment A scoped technical review before any estimate
- 18+ yrs Building business software
- Independent No licence commission, no reseller agenda
- US UK NZ AU Australian team, no account managers
Built here. Your data stays here.
- No offshore development. Everything is written by our own team in Australia. Nothing is subcontracted overseas.
- Your data stays onshore. Hosted in Australia, on infrastructure you own, under Australian law.
- Every state, not just ours. Perth, Melbourne, Sydney, Brisbane, Adelaide and everywhere between.
Your website stopped getting security fixes
Drupal 7 ran a very large number of association, government and education websites. It is now past end of life, which means no security fixes from the Drupal project, and add-on modules whose maintainers have largely moved on.
Read more
The difficulty is that Drupal 8 and later were rebuilt on a different foundation. Content can be migrated. Custom modules and themes cannot simply be carried over. So this is a migration and a partial rebuild, not an upgrade, and it is worth asking what the site really needs before starting.
Our Drupal developer service is for businesses in Sydney, Melbourne, Brisbane, Perth and Adelaide. It covers three kinds of work: code fixes and updates, migration to a modern technology stack, and ongoing maintenance and support.
Three ways forward for a Drupal 7 site
The first is a holding position, not a destination.
-
Reduce the risk now
While the site stays on Drupal 7, logins are locked down, unused modules are removed, the server is tightened, and paid security cover from a Drupal 7 support provider is considered. This buys months, not years.
-
Migrate to current Drupal
Content, users and files are migrated with the tools the Drupal project provides. Custom modules and the theme are rebuilt. Right for sites that rely on complex content, workflow and permissions.
-
Move to something simpler
Where the site is mostly pages and a few forms, the content moves to a lighter platform that costs less to run and to keep secure.
What we do with Drupal 7 sites
Six kinds of work. Most engagements are three or four of them.
-
Site audit
Content types, modules, custom code, users and traffic listed, with what is used and what is not.
-
Interim hardening
The existing site made as safe as it can be while the migration is planned and built.
-
Content migration
Pages, files, users and their relationships moved, with counts checked and broken links found.
-
Custom module rebuilds
The functions your custom code provided rebuilt for the new platform, or dropped where nobody needs them.
-
Theme rebuild
The design carried across, or refreshed, in a theme the new platform supports.
-
Addresses and redirects
Every old address made to resolve, so links, bookmarks and search ranking survive.
Holding, migrating within Drupal and leaving Drupal are different projects
The right one depends on how much of Drupal the site really uses.
-
Stay on Drupal 7 for now
Only as a short holding position, with the risk reduced. A public site without security fixes is exposed, and the exposure grows.
-
Current Drupal
Keeps the content model, workflow and permissions that complex sites depend on. The custom parts are rebuilt. It carries the running cost of a large system.
-
A simpler platform
Lower running cost and less to secure. Right when the site is mostly content. Anything that leaned on Drupal features has to be reconsidered.
What a Drupal 7 assessment looks at
The dates are from the Drupal project. The rest is about what your site is made of.
-
Support status
Drupal 7 reached end of life on 5 January 2025, and the Drupal project said there would be no further extensions. Drupal 10 reaches end of life on 9 December 2026. A migration started now should land on Drupal 11 or later.
-
Contributed modules
Each add-on module in use, and whether a maintained version exists for current Drupal. Some have direct successors, some have been replaced by features now built in, and some have nothing.
-
Custom modules
Code written for this site. It does not carry over, so each piece is rebuilt, replaced by something standard, or dropped.
-
The theme
Drupal 7 themes do not run on current Drupal. The design is rebuilt in the current theme system.
-
Content model
Content types, fields, taxonomies and how they relate. This is what the migration tools carry across, and where the checking goes.
-
Users and permissions
Accounts, roles and anything members can do when signed in.
-
Addresses and traffic
Which pages people and search engines use. Every address is kept or redirected.
-
Integrations and forms
Payment, membership, mailing list and other systems the site talks to, and the forms that feed them.
Still on Drupal 7, with no security fixes since January 2025?
What the assessment needs from you
A fixed-scope piece of work with a written result: the options, the risks of each, and a staged estimate. No production data is sent by email. We agree a secure way to share it first.
-
The site
Its address, and what it does beyond showing pages.
-
Access
An administrator login and access to the code, or to somebody who has them.
-
Size
Roughly how many pages, files and user accounts.
-
Custom work
Any custom modules or integrations you know of.
-
Hosting
Where it is hosted and who manages the server.
-
Who maintains it
Whether anybody looks after it today.
-
What is hurting
The two or three problems that started the conversation.
From assessment to a site that is supported again
By video call and screen share, at meeting times agreed to suit you.
-
Audit and assessment
We list what the site is made of and what is used, and put current Drupal and a simpler platform side by side. You get written options with the risks of each and a staged estimate.
-
Reduce the risk
The existing site is tightened so it is as safe as it can be while the new one is built.
-
Trial migration
Content is migrated into a test site early, so problems with the content show up before the build is finished.
-
Build
The theme and the custom functions are rebuilt, in stages agreed from the assessment.
-
Content check and redirects
Page counts, links and addresses are checked, and every old address is made to resolve.
-
Cutover and support
Each switch is planned with a way back. We watch the first days of live use, then maintain the system for as long as it stays in service.
What people ask us about Drupal 7
Is Drupal 7 still supported?
No. Drupal 7 reached end of life on 5 January 2025 and the Drupal project provides no further security fixes. Some companies sell paid security cover for Drupal 7 sites, which can bridge the time a migration takes.
Can we upgrade Drupal 7 to current Drupal directly?
Not as an upgrade. Drupal 8 onwards has a different foundation, so it is a content migration plus a rebuild of anything custom. The Drupal project provides migration tools, which help with the content.
Should we stay on Drupal at all?
It is worth asking. If the site is mostly content with a few forms, Drupal may be more machinery than you need. If you rely on complex content, workflow and permissions, it earns its place.
Will we lose our search ranking?
Not if keeping the addresses is part of the project from the start. Every old address needs to resolve. Rushed migrations that skip this do damage that takes a year to undo.
Our modules have no version for current Drupal. What happens?
Each one is assessed: a maintained equivalent, a rebuild, or dropped because nobody needs it any more. The third applies more often than people expect.
How urgent is this?
More urgent than most old software. A public website with no security fixes since January 2025 is a real exposure, and it is visible to anyone who looks.
Do you provide Drupal developers in Sydney, Melbourne, Brisbane, Perth and Adelaide?
Yes. We are an Australian team and we take on Drupal work for businesses in Sydney, Melbourne, Brisbane, Perth and Adelaide, and elsewhere in Australia. The work runs by video call and screen share, with secure access to a copy of your system. The service is the same in every city: code fixes and updates, migration to a modern technology stack, and ongoing maintenance and support.
How does this work from the United States, the United Kingdom or New Zealand?
By video call and screen share, at meeting times agreed to suit you, from discovery to handover. Confidentiality, who can reach your systems and where your data is held are agreed in writing before work starts.
What does it cost?
The assessment is a fixed-scope piece of work with an agreed fee. The estimate for anything after it comes from what the assessment finds, in stages, so you are not asked to commit to a whole project on a guess.
Sending your details…
You can stay on this page while we send it.
Tell us about your Drupal 7 site
The site address, what it does beyond showing pages, who looks after it today, and what is forcing the question. Include your country so we can suggest meeting times. Please do not send production data.
Prefer a quick chat? Call 0425 531 127. We answer it ourselves, in Australia.
Kasun Wijayamanna, founderYou deal with Kasun from scope to delivery. No account managers and no offshore handoff.