Other Legacy Technologies

From Classic ASP to VB6 to FoxPro — legacy comes in many forms. While our standard analyzer focuses on .NET applications, we have experience and proven processes for many other platforms. If you don't see your technology listed, contact us anyway.

We've Seen (Almost) Everything

Every platform below has been through our hands. For each one, we've developed analysis approaches that produce the same quality of inventory and risk reporting you'd get from our standard analyzer.

.asp files with VBScript or JScript, COM object instantiation via Server.CreateObject, ADO database access, and inline HTML generation. Often found as the public-facing web tier for 2000s-era enterprise systems.

.asp VBScript JScript COM/ADO

.vbp project files, .frm forms, .bas modules, .cls class modules, and .ocx ActiveX controls. COM automation, DAO/ADO data access, and Windows API calls via Declare.

.vbp .frm .bas .cls .ocx

.prg program files, .scx/.sct form containers, .vcx/.vct visual class libraries, .frx/.frt report files, and .dbf tables. The embedded xBase database engine makes this a self-contained stack with no external database dependency.

.prg .scx .vcx .frx .dbf

.pas Pascal source units and .dfm form definition files from Borland/Embarcadero Delphi. Object Pascal with VCL components, BDE or FireDAC database access, and native Win32 compilation. Many Delphi applications are high-performance and mission-critical.

.pas .dfm .dpr VCL FireDAC

Mainframe (IBM z/OS JCL, CICS, IMS) and Windows COBOL (.cbl, .cob files). COBOL systems are often the most business-critical of all legacy applications — payroll, banking, insurance. Our analysis covers DATA DIVISION structures, PROCEDURE DIVISION logic, and CALL hierarchies.

.cbl .cob CICS JCL IMS

.cfm templates and .cfc ColdFusion components with CFML tag-based and script-based syntax. Often used for data-heavy web applications with cfquery, cfstoredproc, and cfform tags. Adobe continues to maintain ColdFusion, but the talent pool and ecosystem have contracted substantially.

.cfm .cfc CFML cfquery

Our Approach to Non-Standard Stacks

For technologies outside our standard automated analyzer, we apply a structured manual and semi-automated methodology that produces equivalent outputs. The end result — an inventory report and a business risk assessment — is the same.

Manual and Tooling-Assisted Review

We review your codebase using specialized tools appropriate to the technology — static analyzers, language-specific parsers, and script-based extraction tools. We don't rely on a single tool; we combine approaches to maximize coverage and accuracy.

Equivalent Inventory Reports

We produce the same structured inventory reports regardless of the source technology: object counts by type, lines of code, complexity scores, dependency maps, and data access patterns. Manually produced or with custom tooling — the output format is consistent.

Technology-Specific Risk Report

The business risk report is calibrated for the technology's specific market status: vendor support, talent availability, security posture, cloud compatibility, and regulatory considerations. Each technology has its own risk profile and its own urgency drivers.

Modernization Path Recommendation

We recommend target architectures based on your specific technology, your team's skills, your budget constraints, and your organization's tolerance for risk. There is no one-size-fits-all answer — a COBOL modernization path is very different from a VB6 modernization path.

Classic ASP — A Special Case

Classic ASP — Urgent Modernization Required

Classic ASP is among the most urgent modernization cases we encounter. IIS support for Classic ASP is informal and degrading — Microsoft has not invested in it for over 15 years, and each new Windows Server version introduces new compatibility friction.

.asp files with VBScript or JScript cannot run on Linux or in containers. You are permanently locked to Windows IIS.
VBScript was officially deprecated by Microsoft in 2011. It receives no security updates and is not available in modern scripting environments.
Classic ASP has no built-in CSRF protection. SQL injection is trivially easy via string concatenation patterns, which are endemic in Classic ASP code.
The security surface of a Classic ASP application is enormous by modern standards. PCI DSS and SOC 2 compliance is difficult to achieve and impossible to sustain.
Finding Classic ASP developers is nearly impossible. Most VBScript experience exists in developers who also remember Internet Explorer 6.

If your organization is still running Classic ASP in production, the modernization conversation is not optional — it's overdue.

VB6 — The Hidden Time Bomb

VB6 — The Highest Modernization Urgency We Encounter

Visual Basic 6.0 occupies a strange and dangerous position: technically "supported" by Microsoft for runtime compatibility, yet receiving zero security updates and actively incompatible with modern development practices.

The VB6 IDE does not run on Windows 11 ARM. As ARM-based hardware becomes standard, your ability to maintain VB6 code disappears entirely.
COM dependencies create deployment nightmares on 64-bit systems. Many VB6 components are 32-bit only and require a 32-bit process host, creating architecture constraints that compound over time.
Finding a VB6 developer who can maintain, debug, and extend production code is nearly impossible and commands extraordinary rates when you do find one.
The VB6 runtime binary has known, unpatched security vulnerabilities. There is no remediation path except migration.
VB6 applications cannot be containerized, cannot run on Linux, and cannot be deployed to any modern cloud-native infrastructure.

Of all the technologies we work with, VB6 carries the single highest combination of talent risk, security risk, and deployment risk. If you have VB6 in production, reach out today.

Whatever You're Running, Let's Talk

The first conversation is always free. No commitment, no sales pitch, no pressure. Tell us what you have — and we'll tell you honestly what we can do and what it would take. We've seen it all, and we'll be straight with you.

Every engagement starts the same way: a conversation. We don't charge for the first call, and we don't require you to have everything figured out before you reach out.

Send a quick message describing your technology and situation. Fast, informal, and we respond same day.

Chat on WhatsApp

Email

Describe your application, your technology stack, and what's driving the modernization need. We'll reply within one business day.

Send an Email

Schedule a Call

Pick a 30-minute slot that works for you. No agenda required — just bring your questions. First call is always free.

Book on Calendly

Other Legacy Technologies

We've Seen (Almost) Everything

Classic ASP

Visual Basic 6.0

FoxPro / Visual FoxPro

Delphi / Object Pascal

COBOL

ColdFusion