Leading Low Cost Classic ASP Developers Sydney, Melbourne, Brisbane, Perth, Adelaide
It still runs. Nobody has checked whether it is still safe.
For businesses with a website or an internal system still running on Classic ASP. We review it for security, keep it supported, and migrate it to ASP.NET or another current stack a section at a time, behind the same addresses.
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.
Still running, still online, and nobody has checked it
Classic ASP applications are usually internal systems or early customer portals: a booking system, a stock lookup, an ordering site built when that was new. They are typically a set of .asp files with database queries written directly into the page, which was normal at the time and is now the main security concern.
Read more
Because IIS still runs them, nothing forces a change. The risk is not that they stop. It is that they face the internet, were written before safe database queries were routine, and nobody has looked at them in ten years.
Our Classic ASP 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 Classic ASP application
The first is worth doing whatever is decided afterwards.
-
Secure it and support it
The pages are read for the faults common to their era, the worst are fixed, and the server is brought onto a supported version of Windows. The application stays in Classic ASP and somebody is looking after it.
-
Migrate it a section at a time
New pages are written in ASP.NET or another current stack and take over from the old ones behind the same addresses. The database stays. Users and search engines see the same URLs.
-
Rebuild it
Where the application no longer fits how the business works, it is redesigned and rebuilt, with the data carried across.
What we do with Classic ASP applications
Six kinds of work. Most engagements are two or three of them.
-
Security review
Unsafe database queries, hand-built logins, file uploads and error pages that reveal too much, found and fixed.
-
Classic ASP maintenance
Changes and fixes in existing .asp pages and include files.
-
Server moves
Sites moved from an old Windows Server to a supported one, with their components registered and tested.
-
Component replacement
Old server components for uploads, email, PDF and images replaced with current equivalents.
-
Staged migration
Pages rewritten in ASP.NET or another stack, a section at a time, against the same database.
-
Addresses kept
Existing URLs kept or redirected, so bookmarks, links and search ranking survive the change.
Securing it, migrating it and rebuilding it are different projects
Each trades cost against how much old code remains afterwards.
-
Keep it in Classic ASP
Lowest cost. The application is made safe and supported on a current server. It remains tied to VBScript and to a shrinking number of people willing to work on it.
-
Migrate to ASP.NET in stages
The same database and the same addresses, with pages replaced as they are rewritten. Old and new run together during the change, so there is no single risky switch.
-
Rebuild on a different stack
A new design on whatever stack suits the business now. It takes longest, and is right when the application needs to change more than the technology does.
What a Classic ASP assessment looks at
Classic ASP itself is still supported. The risk is in how the pages were written and what they depend on. The support facts are from Microsoft.
-
Support status
Microsoft states that ASP is supported in all supported versions of IIS, with its life tied to the Windows version underneath. So the first question is which Windows Server the site runs on, and whether that is still supported.
-
VBScript
Most Classic ASP is written in VBScript. Microsoft has announced that VBScript is being retired from Windows in phases: an optional feature first, off by default from around 2027, and later removed. What that means for the server your site runs on is checked early.
-
SQL written into the pages
Queries built by joining text from the browser into a database command. It was normal at the time, and it is the main security concern now on anything reachable from the internet.
-
Server components
Components registered on the server for uploads, email, PDF and images. Many are 32-bit, and some come from companies that no longer exist. Each is identified, and kept working or replaced.
-
Logins and sessions
Hand-built sign in, passwords stored in readable form, and session handling that predates current practice.
-
The database
SQL Server, Access or something older, and the driver the pages use to reach it. An Access file behind a website is a risk of its own.
-
Shared code
How pages share code through include files, and how much logic is repeated across them. This sets the cost of every change.
-
Addresses and search ranking
Which URLs customers, bookmarks and search engines use. They are kept or redirected, so a migration does not cost traffic.
A Classic ASP site that works, and nobody dares touch?
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.
-
Server
The Windows Server and IIS version, and who hosts it.
-
Size
A rough count of pages, and whether the code is in source control.
-
The database
Product, version and size.
-
Components
Any server components you know the site needs.
-
Exposure
Whether it is reachable from the internet, and what personal or payment data it handles.
-
Integrations
Payment gateways, email, files in and out, other systems.
-
What is hurting
The two or three problems that started the conversation.
-
The way back
How long the business can run on the old system if a cutover has to be reversed.
From assessment to a supported application
By video call and screen share, at meeting times agreed to suit you.
-
Technical assessment
We read the pages, list the components and the database access, and check the server. You get a written list of findings and options, with the risks of each and a staged estimate.
-
Urgent fixes
Anything that exposes data to the internet is fixed first, on a copy, then released.
-
Proof of concept
One section is rewritten on the new stack and run behind the same addresses, against the same database.
-
Staged work
The work is done in stages agreed from the assessment, each with its own scope and estimate, starting with whatever is hurting the business most.
-
Comparison and user testing
Old and new pages are compared on the same data, and your staff test the work they do every day.
-
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 Classic ASP
Is Classic ASP still supported?
Yes. Microsoft supports ASP in all supported versions of IIS, tied to the life of the Windows version underneath. The language most pages are written in, VBScript, is being retired from Windows in phases, and that is the reason to plan.
Is Classic ASP a security risk?
The language itself is not the issue. The habits of the time are: database queries built from text the browser sends, logins written by hand, and no review in a decade. On a site that faces the internet, that combination is worth acting on.
Can Classic ASP be migrated to ASP.NET?
Yes, and it can be done in stages. There is no dependable automatic converter, because the two work differently. Pages are rewritten a section at a time and take over behind the same addresses, usually against the same database.
Can we keep the database and only replace the application?
Usually, yes, and it is the approach we prefer. With SQL Server already behind it, changing the application alone keeps the checking simple and the project shorter.
What about the components registered on the server?
We identify what each does. They are commonly handling file uploads, PDF creation or sending email, all of which have straightforward current equivalents.
IIS still runs it. Why change anything?
A fair question, and sometimes the answer is not yet. The trigger is usually a security review, a Windows Server upgrade, or a change nobody will make. Until one arrives, a security review and a supported server may be all that is needed.
Do you provide Classic ASP developers in Sydney, Melbourne, Brisbane, Perth and Adelaide?
Yes. We are an Australian team and we take on Classic ASP 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 Classic ASP application
What the application does, whether it faces the internet, the database behind it, 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.