Short answer
Classic ASP and Microsoft Access are the most common legacy stack we replace at Bocati Solutions. Both are officially unsupported, both create hosting and security risks in 2026, and both can be replaced with a modern cloud platform in 6–12 weeks at a fixed price. We have done it for an Australian business with over one million rows and zero data loss.
The combination of Classic ASP (web application layer) and Microsoft Access (database) was a common and practical choice for Australian businesses building internal systems in the late 1990s and early 2000s. Classic ASP was the dominant web technology before .NET. Access was cheap, easy to use, and adequate for small-scale data management.
These systems were often built by a single developer who knew the business well, delivered quickly, and then kept running. The developer moved on. The system kept working. Nobody touched it. Ten years became fifteen. Fifteen became twenty. The system still works — mostly — and the business is reluctant to disturb something that has not broken yet.
This is the situation most Classic ASP clients are in when they contact us. The system has not catastrophically failed. But it is creating risk that compounds every year — and the window for a planned, controlled replacement is narrowing.
Classic ASP requires Windows IIS on server versions that are ageing out of support. Hosting providers that still offer Classic ASP-compatible environments are declining in number. Some clients come to us because their host has notified them of an upcoming end of support — not a gradual decline, but a hard deadline.
Classic ASP has not received security patches in years. Any vulnerability discovered in the Classic ASP runtime is a permanent, unpatched vulnerability. If your system handles customer data or personally identifiable information, this is not just a technical risk — it is potential liability under the Australian Privacy Act.
Classic ASP developers are a vanishing population. The developers who built these systems in 2000–2008 have retired, changed careers, or moved on. Finding someone to make changes safely — without breaking anything — is increasingly difficult and expensive.
Access was never designed for shared network use. It was designed for single-user desktop applications. The risks of using it as a shared production database are well-documented:
We replace Classic ASP + Access systems with a modern web stack: React + TypeScript frontend, a managed PostgreSQL database on cloud infrastructure, and a REST API layer. The new system runs in any browser on any device, anywhere — with separate portals per user type, automated daily backups, uptime monitoring, and 100% source code ownership at handover.
The Drill Guys project was a Classic ASP application backed by Microsoft Access that had been running for 16 years, managing patient and appointment records for a dental business on the Gold Coast. We replaced it with a three-portal cloud-native platform in 8 weeks — every record migrated with zero data loss, cutover on a Sunday, team on the new system Monday morning.
| Project scope | Typical cost (AUD) | Timeline |
|---|---|---|
| Simple system, single portal | $25,000–$45,000 | 6–8 weeks |
| Multi-portal with complex data migration | $45,000–$80,000 | 8–12 weeks |
| Large platform with integrations | $80,000–$120,000+ | 12–16 weeks |
All projects are quoted at a fixed price after a technical audit. The audit ($2,500–$5,000) maps the system and produces the quote — you know the full cost before any build work begins. Start with a free discovery call or read more about the legacy modernisation service.
Legacy Modernisation Guides
Yes. Classic ASP has received no security patches or feature updates for years. In 2026, running Classic ASP means running permanently unpatched software on a hosting environment with a shrinking number of providers. The question is not whether to replace it — it is when.
A modern web stack: React or Next.js frontend, API layer, and a managed PostgreSQL database on cloud infrastructure. The new system does everything the Classic ASP app did — plus remote access, API integrations, client portals, and automated backups — delivered in weeks.
For production use with multiple concurrent users and remote access: a cloud-hosted relational database with a purpose-built web interface. Access was designed for single-user desktop data management — the replacement is a proper web application, not another desktop database tool.
For simple single-user desktop tasks — yes. For anything used by a team, shared over a network, or accessed remotely — no. Access databases used as shared production systems are a well-documented source of corruption and data loss risk.
If your system is still running on Classic ASP or Microsoft Access, you already know the risks. Start with a free discovery call — we will map the system and give you a clear picture of what a replacement would involve.