ZTABS modernizes legacy applications for Denver organizations — water utilities replacing 20-year-old SCADA and billing systems serving 1.5 million Front Range residents, federal agencies migrating Oracle Forms and mainframe applications at the Denver Federal Center, and municipal governments updating permitting and licensing systems built before the smartphone era.
Denver's legacy application modernization urgency is driven by organizations running mission-critical systems on technology that is: increasingly expensive to maintain, unable to integrate with modern tools, and dependent on a shrinking pool of developers who understand: COBOL, Oracle Forms, Cold Fusion, Visual Basic 6, and: other legacy technologies. Water and utility infrastructure: Denver Water, Aurora Water, and: the 30+ water districts serving the Front Range operate critical infrastructure systems that were built: when client-server architecture was cutting-edge. These systems manage: water treatment operations (SCADA systems controlling: treatment processes, chemical dosing, and: distribution — running on: legacy platforms that are: effective but increasingly difficult to maintain and: impossible to integrate with modern analytics), billing and customer service (customer information systems built in: the 2000s on: Oracle or custom databases — handling: 500,000+ customer accounts for Denver Water alone — systems that: work but provide: limited self-service capability, no mobile access, and: inflexible rate structures that cannot: accommodate modern pricing models like: tiered conservation rates or: time-of-use pricing), and asset management (water mains, valves, hydrants, and: treatment facilities tracked in: legacy databases or: GIS systems that are: not connected to: maintenance management — preventing: the predictive maintenance and: lifecycle cost analysis that modern asset management enables). Federal legacy systems: Denver Federal Center agencies operate some of the oldest federal IT systems still in production — permit processing systems built on: Oracle Forms, data management systems on: mainframes, and: scientific computing applications written in: Fortran. These systems are: mission-critical (federal operations depend on them daily), expensive to maintain (legacy skills command: premium rates — $180-250/hour for COBOL or Oracle Forms developers), and impossible to enhance (adding features to: a 25-year-old Oracle Forms application is: prohibitively expensive and risky — changes in one area cause: unexpected failures in another due to: decades of accumulated technical debt). Municipal legacy systems: Denver and surrounding municipalities operate: permitting systems (building permits, business licenses, and: zoning applications — many still running on: systems built 15-20 years ago with: limited online capability — citizens must: visit city offices in person for: many interactions that should be: available online), court and records systems (case management, records retention, and: public access — often running on: legacy platforms that: cannot support: modern public records requests or: electronic filing), and transportation systems (traffic management, transit operations, and: parking — legacy systems that cannot: integrate with: modern smart city technology).
Denver's legacy modernization demand spans water utilities, federal agencies, municipal government, healthcare, and enterprise business. Water Utility Modernization: Front Range water utilities need: SCADA modernization (upgrading: legacy SCADA systems that control: water treatment and distribution — modern SCADA provides: better monitoring, integration with analytics, and: cybersecurity features that: legacy systems lack — but: modernization must be: carefully phased to: never compromise: water treatment operations — water is: the most safety-critical infrastructure a city operates), billing system replacement (replacing: legacy billing platforms with: modern customer information systems (CIS) that support: online payment, mobile access, automated meter reading (AMR/AMI) integration, tiered and conservation-based rates, and: customer self-service — Denver Water's service area alone has: 500,000+ accounts that: cannot tolerate: billing disruption during migration), and asset management modernization (implementing: modern asset management that: integrates with GIS, connects to field operations, and: enables: lifecycle cost analysis and: capital planning — replacing: legacy databases and: paper-based processes for: tracking: $8+ billion in water infrastructure assets across the Front Range)). Federal System Modernization: Denver Federal Center agencies need: Oracle Forms migration (the most common federal legacy challenge: Oracle Forms applications built: 15-25 years ago — complex, customized, and: deeply embedded in: agency workflows — migration options: re-platform to Oracle APEX (lowest risk, staying in Oracle ecosystem), re-architect to modern web (higher effort but: better long-term platform), or: replace with SaaS (if commercial products meet: the agency's specialized needs)), mainframe decommission (for agencies still running mainframe workloads: migrating: COBOL batch processing and: hierarchical databases to: modern platforms — requiring: careful business logic extraction because: the COBOL code embodies: decades of business rules that: may not be documented anywhere else), and scientific application modernization (Fortran, MATLAB, and: legacy scientific computing applications — used by: USGS, NREL, and: other research agencies — modernization may mean: containerizing for cloud execution rather than: rewriting — preserving: validated scientific code while: enabling: modern deployment and scaling)). Municipal Modernization: Denver and surrounding municipalities need: permitting and licensing (replacing: legacy permitting systems with: modern platforms that support: online application, digital plan review, automated workflow routing, and: real-time status tracking — citizens and businesses should be able to: apply for permits, upload documents, track status, and: receive approvals online — rather than: visiting city offices with: paper applications), records management (digitizing: paper records and: migrating: legacy electronic records to: modern platforms with: proper retention scheduling, public records request handling, and: secure storage — many Denver-area municipalities have: decades of records in: legacy systems that must be: preserved and: made accessible), and 311/citizen service (modernizing: citizen service request systems — replacing: phone-only 311 with: multi-channel (web, app, phone, text) citizen service that: routes requests to appropriate departments, tracks resolution, and: reports on: service performance)).
Our legacy modernization methodology for Denver organizations prioritizes safety, data preservation, and operational continuity above all else. Phase 1 — Legacy Assessment (2-4 weeks): understanding what exists: application inventory (documenting: every legacy application — what it does, who uses it, what technology it runs on, what data it manages, and: what integrations it has — for organizations with: decades of IT history: this often reveals: applications that: nobody remembers building but: are still running and: serving a purpose), business logic extraction (the most critical and often most difficult step: understanding what the legacy application actually does — not what the documentation says (which is: usually outdated or incomplete) but: what the code actually implements — for COBOL and Oracle Forms: this requires: developers who can: read legacy code and: translate: business rules into: modern-language documentation — we use: a combination of code analysis, user interviews, and: test-case development to: capture: the business logic that the new system must replicate), data assessment (understanding: the legacy data — volume, structure, quality, and: relationships — legacy databases often have: undocumented relationships, data quality issues that have accumulated over decades, and: historical data that: must be preserved for: regulatory or legal reasons), and risk assessment (evaluating: the risks of modernization — what happens if the migration fails? What is the business impact of downtime? How long can the organization operate without: the legacy system? — this assessment drives: the migration strategy — higher risk demands: more conservative approaches with: longer parallel running periods)). Phase 2 — Modernization Strategy (2-3 weeks): choosing the right approach: strategy selection (for each legacy application: selecting the modernization approach — rehost (lift and shift to cloud — lowest risk, lowest benefit — appropriate for: stable applications that need: infrastructure modernization but: not functional change), re-platform (move to modern platform with: minimal functional changes — moderate risk, moderate benefit — for Oracle Forms: migrating to APEX preserves business logic while: modernizing the platform), re-architect (redesign the application using modern architecture — higher risk but: highest benefit — appropriate when: the legacy application's functionality needs significant enhancement), replace (replace with commercial software — appropriate when: the legacy application's function is now available in: standard commercial products), or: retire (decommission applications that are: no longer needed — surprisingly common when: business processes have evolved but: the application was: never turned off)), migration planning (developing: the detailed migration plan — timeline, resources, testing strategy, rollback plan, and: parallel running period — with: special attention to: data migration (the highest-risk element) and: user transition (the highest change-management challenge)), and stakeholder alignment (ensuring: all stakeholders understand and agree on: the modernization approach, timeline, and: their roles in: testing, validation, and: adoption — legacy modernization projects fail most often from: organizational resistance, not: technical problems)). Phase 3 — Modernization Execution (8-20 weeks): building the replacement: incremental delivery (modernizing in phases rather than: replacing the entire legacy system at once — each phase: replaces one functional area, is tested thoroughly, and: runs in parallel with: the legacy system before: cutover — for water utility billing: Phase 1 might be: customer self-service (new capability added while: legacy billing continues), Phase 2: meter reading integration, Phase 3: billing engine replacement — each phase delivering: value while: limiting risk), data migration (the most safety-critical technical element: extracting data from: legacy databases, transforming to: the new data model, loading into: the new system, and: validating — for water utilities: customer billing data migration must be: perfect — a billing error affecting: 500,000 customers would be: a front-page news event — we use: automated migration with: record-level validation, parallel billing runs (processing the same billing cycle in both systems and: comparing results), and: reconciliation audits)), and testing (comprehensive testing: functional testing (does the new system produce: the same results as the legacy system for: every business scenario?), data testing (is all data migrated correctly? Are calculations accurate?), performance testing (can the new system handle: peak loads — for water billing: month-end billing processing 500,000+ accounts), integration testing (do all connections to: other systems work correctly?), and: user acceptance testing (do the users who will: operate the system daily: confirm it meets their needs?)))). Phase 4 — Cutover and Stabilization (2-4 weeks): transitioning to the new system: parallel operation (running: both legacy and modern systems simultaneously — processing: real transactions in both — and: comparing: results — this period is: non-negotiable for: mission-critical systems — the duration depends on: risk tolerance — water billing: minimum 2 full billing cycles (2 months) in parallel), cutover execution (the planned transition from: legacy to modern system — with: documented rollback procedures that: can restore the legacy system if: any issue is detected — the rollback plan is: tested before: cutover, not created as a formality), stabilization support (intensive support during: the first 2-4 weeks after cutover — on-site support for: user questions and issues, rapid bug fixes, and: performance monitoring — this period determines: user confidence in the new system and: is critical for adoption), and legacy decommission (after: a defined stabilization period — turning off the legacy system — with: data archived for: regulatory or legal retention requirements — and: a final verification that: no business process still depends on: the legacy system)).
Water Utilities / Municipal Infrastructure
A Front Range water utility serving 180,000 residential and commercial accounts across: 4 municipalities and unincorporated county areas needed to replace its legacy Customer Information System (CIS) — a custom-built application running on: Oracle Database 10g with: a Visual Basic 6 desktop client. The system was: built in 2003, maintained by: a rotating series of contractors (the original developer had: left in 2010), and: had accumulated: 21 years of customizations, patches, and: workarounds. The CIS managed: customer accounts (180,000 accounts — with: service addresses, meter assignments, billing rates, payment history, and: account status), billing (monthly billing cycles: meter reading processing, consumption calculation, rate application, bill generation, and: payment processing — generating: approximately $95M in annual water revenue), and customer service (call center support: account inquiries, payment processing, service requests, and: complaint handling — 45,000 customer service interactions per year). Why modernization was urgent: (1) Technology risk: Visual Basic 6 was: discontinued by Microsoft in 2008 — the desktop client ran on: Windows 7 machines that were: also end of life — each Windows update risked: breaking the VB6 application — the utility was: running legacy Windows on: isolated machines to: prevent updates from: disrupting billing. Oracle Database 10g was: similarly end of life — security patches had stopped years ago — the database was: a known security vulnerability that: the utility's cybersecurity assessment had: flagged as: critical. (2) Customer expectation gap: the VB6 client had: no web interface — customers could not: view their accounts online, make payments online, or: report issues online. Every customer interaction required: a phone call during: business hours (7 AM - 5 PM Monday-Friday). Customer complaint rates about: accessibility had: increased 45% over 3 years as: customers expected: the self-service capabilities available from: every other utility and service provider. (3) Rate structure limitations: the utility was: implementing conservation-based tiered rates and: considering time-of-use rates to: encourage off-peak irrigation. The legacy CIS could not: support tiered rate calculations — it was designed for: flat-rate billing with: one rate per customer class. Implementing new rate structures in VB6 was: estimated at: $180,000 in development (at VB6 contractor rates of $200/hr) with: 6-8 months timeline and: significant risk of: billing errors that could affect: all 180,000 accounts. (4) Smart meter integration: the utility was deploying: AMI (Advanced Metering Infrastructure) — smart meters that transmitted: hourly consumption data via: cellular network. The legacy CIS could only process: monthly meter reads (a single number from: manual meter reading). Integrating AMI data required: accepting 720 readings per meter per month (vs. 1) — a data volume the legacy system could not: handle — and: the value proposition of AMI (leak detection, consumption analytics, time-of-use billing) depended on: a modern CIS that could: process and present: granular consumption data. (5) Data quality: 21 years of data in the system had: accumulated quality issues — duplicate accounts (estimated 3-4% of records), incorrect meter-to-address assignments (discovered during: AMI deployment), historical rate changes that created: billing edge cases the VB6 code handled through: hardcoded workarounds, and: 8 different address formats (from: 21 years of different data entry practices). Migrating this data to a new system required: extensive cleansing — but: the data could not be discarded because: billing history was: legally required for: rate case proceedings and: customer disputes.
We modernized the CIS over 20 weeks — replacing the VB6/Oracle 10g legacy system with a modern web-based platform while maintaining billing continuity for 180,000 accounts. Modern CIS Platform: technology stack (Next.js frontend (responsive web application — desktop and mobile), PostgreSQL database (replacing Oracle 10g), and: Python/FastAPI backend — deployed on: AWS with: multi-AZ redundancy — the utility had: never had: disaster recovery capability for billing — the cloud architecture provided: automatic failover that the legacy system lacked)). Billing Engine: rate structure flexibility (the new billing engine was designed for: multiple rate structures: flat rate (legacy support), tiered conservation rates (the utility's new rate structure — increasing price per unit at: higher consumption levels — incentivizing conservation), seasonal rates (different rates for summer irrigation season), time-of-use rates (higher rates during: peak demand periods — enabled by: AMI data), and: budget billing (level payment plans based on: predicted annual consumption) — rate structures configured through: an administration interface rather than: code changes — new rate structures could be: implemented in: hours rather than: months)). AMI Integration: smart meter data (the CIS accepted: hourly consumption data from: the AMI head-end system — processing: approximately 130 million meter readings per month (180,000 meters × ~720 readings/month) — storing: historical consumption at: hourly granularity (vs. monthly) — enabling: consumption analytics that the legacy system could not provide: daily consumption patterns (identifying: unusual usage that might indicate: leaks), hourly peak demand (supporting: time-of-use rate implementation), and: comparative analytics (showing customers: how their usage compared to: similar households — a proven conservation tool))). Customer Self-Service Portal: online account management (a customer-facing web portal — the first in the utility's history: account dashboard (current balance, usage trends, billing history, and: payment options), online payment (ACH, credit card, and: auto-pay enrollment — previously: payments by: mail, phone, or: in-person only), usage analytics (interactive charts showing: daily and hourly consumption — enabling: customers to: identify high-usage periods and: conservation opportunities), service requests (start/stop service, meter testing requests, and: account changes — submitted online and: routed to: appropriate staff), and leak alerts (automated notifications when: AMI data indicated: unusual continuous usage that likely represented: a leak — the utility estimated: undetected leaks cost: customers $2M+ per year in: wasted water and: high bills that: generated: complaint calls and: payment difficulties))). Data Migration: cleansing and migration (the most intensive part of the project: duplicate resolution (identifying and merging: 6,800 duplicate accounts — using: address matching, name matching, and: meter assignment verification — each merge reviewed by: a utility analyst before: execution), address standardization (normalizing: 8 different address formats to: USPS standard — using: CASS (Coding Accuracy Support System) certification — correcting: 12,400 address records), meter-account reconciliation (verifying: every meter assignment against: AMI deployment records — correcting: 340 incorrect assignments that would have caused: billing errors in the new system), and historical data preservation (migrating: 21 years of billing history — 45 million billing records — with: checksums at migration and: parallel billing validation))). Parallel Billing: dual-system operation (for 3 full billing cycles: both systems processed: the same billing data — the legacy VB6 system produced: bills as usual, the new system produced: shadow bills — a billing comparison report identified: any differences — this was the ultimate validation: if both systems produced: identical bills for 180,000 accounts: the new system was: accurately replicating: the legacy system's billing logic). First cycle: 127 discrepancies identified (from: 180,000 bills — 0.07%) — each investigated and: resolved (23 were: new system bugs, 104 were: legacy system bugs that: had been producing: incorrect bills for: months or years — these were: corrected in: both systems). Second cycle: 8 discrepancies (all: edge cases requiring: additional business rule refinement). Third cycle: 0 discrepancies — the new system was: billing-identical to the legacy system.
The CIS modernization completed in 22 weeks (20 weeks development + 2 weeks post-cutover stabilization). Billing Accuracy: parallel billing validation: 0 discrepancies in the final cycle — 180,000 accounts billed correctly. Historical data: 45 million billing records migrated with: zero data loss (verified by: checksum comparison and: random sample audit). Legacy bugs discovered: 104 billing inaccuracies identified in the legacy system during parallel testing — corrected, resulting in: more accurate billing for the first time in years. Customer Experience: online self-service adoption: 42% of customers registered for: online access within 6 months (from 0% — the utility had never offered online service). Online payment adoption: 38% of payments shifted to: online channels within 6 months — reducing: mail processing from: 180,000 payments/month to: 112,000/month. Customer service calls: reduced by 28% (from 45,000/year to 32,400/year) — self-service handled: account inquiries, payment processing, and: basic service requests that: previously required phone calls. Leak detection: AMI-powered leak alerts notified: 2,400 customers of: probable leaks in the first year — estimated water saved: 18 million gallons — estimated customer savings: $340,000 in: avoided excess water bills. Operational Capability: new rate structures: tiered conservation rates implemented within: 3 weeks of go-live (a change that would have cost: $180,000 and: 6-8 months on the legacy system — and was: included in the modernization at: no additional cost). AMI data processing: 130 million readings/month processed without: performance issues (the legacy system could not have: handled this data volume at any cost). Disaster recovery: the utility now had: automatic failover — the first time in: its history that billing operations were: protected against: infrastructure failure. Financial Summary: development cost: $482,000 (20 weeks — larger team due to: the criticality and data migration complexity). Annual platform cost: $84,000 (AWS, PostgreSQL, monitoring). Legacy system cost eliminated: $156,000/year (Oracle licensing: $96,000, VB6 contractor maintenance: $60,000). Customer service reduction: $126,000/year (12,600 fewer calls × $10/call average handling cost). Payment processing savings: $98,000/year (online payments vs. mail processing). Conservation rate implementation: included (vs. $180,000 if done on legacy). Total annual benefit: $380,000 (recurring) + $180,000 (one-time rate implementation savings). ROI: 99% in the first year — accelerating in subsequent years as: the annual benefit compounds and: the one-time development cost is amortized.
Modernize one module at a time — reducing risk, delivering value early, and keeping the business running throughout.
We extract and document the business rules embedded in legacy code so nothing gets lost in the new system.
Migrate from legacy databases (Access, FoxPro, SQL Server) to modern PostgreSQL or cloud-managed databases.
Build modern REST or GraphQL APIs that let the new system talk to legacy components during the transition period.
Create comprehensive test suites that verify the new system behaves identically to the old one for every critical workflow.
Deploy the modernized application on AWS, Azure, or Vercel with CI/CD pipelines, monitoring, and auto-scaling.
Denver's legacy modernization market includes large system integrators, utility technology vendors, and general software firms. (1) System integrators (Deloitte, Accenture, CGI) — handle large modernization projects but: at 3-5x ZTABS rates, with 18-36 month timelines, and expensive change order processes. (2) Utility technology vendors (Oracle Utilities, SAP, Itron) — provide commercial CIS platforms but: $1-5M implementation costs, 12-24 month timelines, and ongoing licensing fees that exceed custom solution costs. (3) General software firms — can build modern applications but: lack legacy system expertise (cannot read VB6 or COBOL to extract business rules), limited experience with mission-critical data migration, and no utility industry expertise. ZTABS modernizes legacy applications with: legacy code expertise, safe data migration practices, and Denver industry knowledge — delivering faster and at lower cost than enterprise alternatives.
Legacy app modernization in Denver ranges by application complexity and data volume. Simple Modernization (single application, limited data, 6-10 weeks): $100,000-$200,000. Complex Modernization (mission-critical application, large data, compliance, 12-20 weeks): $250,000-$500,000. Enterprise Modernization (multiple applications, federal compliance, 16-30 weeks): $400,000-$900,000. Data migration (additional to application cost): $30,000-$150,000 depending on volume and quality. ZTABS delivers at $175-275/hr — engineers with legacy code expertise and Denver industry knowledge.
Verified reviews from real client engagements — sourced from our public testimonial archive and Clutch profile.
My experience is throughout positive. Communication, service, the short response times and the flawless execution of a challenging topic was absolutely great. ZTABS is definitely my first choice again.
Christian Neff
Bank Software Advisory · Bank Software Advisory
Fintech
Fantastic Agency! I couldn't fault them even if I tried. They always go above and beyond to meet your expectations and always produces quality work. Thank you ZTABS.
Stephanie Kal
CEO · Beauty Finder Australia
Marketplace
It has been great working with ZTABS. They bounce off the ideas along the way. Amazing Experience.
Joel Rowe
CEO · Drill Quoter
Marketplace
We don't just contract. We ship and operate our own software. 23 products in production.
Common questions about legacy app modernization for Denver businesses
Five safeguards: pre-migration backup (complete backup of legacy system before any migration activity), automated migration with validation (scripted migration with record-level checksums — every record verified after transfer), parallel operation (both systems processing real data simultaneously — results compared automatically), reconciliation audits (random-sample manual verification of migrated data — especially financial and compliance data), and rollback capability (the ability to revert to the legacy system for 90 days post-migration). For water utility billing data: we add billing comparison (identical billing runs in both systems with automated comparison of every bill). We have never lost data in a legacy migration.
ZTABS is a remote-first legacy app modernization agency serving Houston businesses — including incremental modernization, business logic preservation, data migration. We work with Energy & Oil/Gas, Healthcare & Biotech, Aerospace & Defense companies in Houston, TX via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Legacy App Modernization in New York, NYZTABS is a remote-first legacy app modernization agency serving New York businesses — including incremental modernization, business logic preservation, data migration. We work with Finance & Fintech, Media & Advertising, Fashion & Retail companies in New York, NY via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Legacy App Modernization in Los Angeles, CAZTABS is a remote-first legacy app modernization agency serving Los Angeles businesses — including incremental modernization, business logic preservation, data migration. We work with Entertainment & Media, E-commerce & DTC Brands, Gaming & AR/VR companies in Los Angeles, CA via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Web Development in Denver, COZTABS is a remote-first web development agency serving Denver businesses — including full-stack development, progressive web apps, api development. We work with Outdoor & Lifestyle Tech, Aerospace & Defense, Cannabis Tech companies in Denver, CO via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Web Design in Denver, COZTABS is a remote-first web design agency serving Denver businesses — including ui/ux design, responsive design, custom interfaces. We work with Outdoor & Lifestyle Tech, Aerospace & Defense, Cannabis Tech companies in Denver, CO via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
AI Development in Denver, COZTABS is a remote-first AI development agency serving Denver businesses — including llm integration & fine-tuning, ai agents & automation, rag & knowledge systems. We work with Outdoor & Lifestyle Tech, Aerospace & Defense, Cannabis Tech companies in Denver, CO via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Legacy App ModernizationLearn more about our legacy app modernization services nationwide.
Partner with ZTABS for expert legacy app modernization in Denver. Get a free consultation today.
