VB6 Systems Assessment

Get a clear, evidence-based understanding of your VB6 estate: what you have, how it behaves, where it’s fragile, and what your realistic options are.

Your VB6 system is too important to guess about. A VB6 Systems Assessment replaces anecdotes and assumptions with a structured, written view of your architecture, dependencies, and risks. It’s the foundation for any serious decision about maintenance, modernisation, or replacement.

Who this is for

  • Organisations with business-critical VB6 applications and no clear plan for the future.
  • Teams where key VB6 knowledge has left or is about to leave.
  • CIOs and CTOs who need to explain VB6 risk to boards, regulators, or auditors.
  • Programme leaders planning modernisation or transformation initiatives that depend on VB6 systems.
  • Any organisation considering auto-conversion tools and wanting an independent view of the risks.

Problems this service addresses

  • You don’t know how big your VB6 problem really is.
  • Different stakeholders have conflicting views of the system’s importance and risk.
  • There is no single, up-to-date picture of the VB6 codebase, integrations, and dependencies.
  • You’re under pressure to “do something” about VB6 but lack evidence to choose a path.
  • Vendors are pitching tools or solutions, but you can’t compare them against your reality.

Benefits and outcomes

Clarity

Move from vague concern to a structured, written understanding of your VB6 estate. See architecture, dependencies, and hotspots in one place.

Risk visibility

Identify technical, operational, and organisational risks, including single points of failure, unsupported components, and knowledge gaps.

Decision support

Get concrete options with pros, cons, and preconditions so you can make informed, defensible decisions about VB6.

How the assessment works

1. Discovery and context

We start by understanding your business context: what the VB6 system does, who uses it, how critical it is, and what pressures you’re under. This includes interviews with key stakeholders and review of any existing documentation.

2. Technical and architectural review

I analyse the VB6 codebase and its environment: structure, modules, dependencies, integrations, data access patterns, and deployment model. The goal is to understand architecture and hotspots, not to read every line of code.

3. Risk and dependency mapping

We identify where the system is most fragile: single points of failure, unsupported components, undocumented integrations, and areas where change is particularly risky. Organisational risks, such as reliance on a single individual, are also considered.

4. Options, scenarios, and recommendations

Based on the findings, you receive realistic options—stabilise and maintain, staged rewrite, partial replacement, or combinations—each with implications, timelines, and dependencies. Clear recommendations and suggested next steps complete the picture.

Deliverables

  • Assessment report covering system overview, architecture, dependencies, and risk analysis.
  • Modernisation options and scenarios with pros, cons, and preconditions.
  • Executive summary suitable for leadership and non-technical stakeholders.
  • Discussion session to walk through findings, answer questions, and refine priorities.

Why choose this assessment

You’re not buying a generic “health check”. You’re getting a focused, VB6-specific assessment from someone who has spent decades working with real VB6 systems—not just reading about them. The output is designed to be used: to support decisions, justify budgets, and guide programmes. It’s written in clear, jargon-free language, with enough technical depth for your teams and enough clarity for your leadership.