ZTABS modernizes legacy applications for Seattle organizations trapped by aging technology — government and municipal systems modernization for King County, the City of Seattle, and Washington State agencies where COBOL mainframe applications, 20-year-old .NET systems, and paper-based processes serve millions of residents but cannot support mobile access, real-time data sharing, or the digital service delivery that citizens now expect from every interaction including permitting, licensing, public records, and benefit administration, enterprise application transformation for mid-market Seattle companies running business-critical applications on end-of-life platforms where Visual Basic 6, classic ASP, Oracle Forms, and aging Java applications still process millions of dollars in daily transactions but their original developers have retired, their platforms are unsupported, and every passing month increases the risk of catastrophic failure that could halt business operations, and mainframe-to-cloud migration for the financial institutions, insurance companies, and utilities in the Pacific Northwest that still run core processing on IBM mainframes where the COBOL developer workforce is aging out and the cost of maintaining mainframe infrastructure is growing 8-12% annually while cloud alternatives offer superior economics, scalability, and integration capabilities.
Legacy app modernization in Seattle addresses the growing urgency of replacing aging technology before it becomes a crisis. Seattle's legacy application landscape: despite Seattle's reputation as a technology hub, the region has a significant legacy application problem — particularly in government, financial services, utilities, and mid-market companies that automated early (1990s-2000s) and haven't had the resources or organizational will to modernize. The scope of the problem: King County (population 2.3 million — the 12th most populous county in the US) runs critical services on applications built 15-25 years ago. The City of Seattle (population 750,000) has 200+ applications in its portfolio, many running on unsupported platforms. Washington State government agencies run dozens of COBOL mainframe applications that process billions in benefits, taxes, and regulatory transactions. Private-sector legacy is equally prevalent: mid-market manufacturers, distributors, and professional services firms in the Puget Sound region automated business processes in the late 1990s and early 2000s using Visual Basic, Access databases, classic ASP, and early .NET frameworks. These applications still work — they process orders, manage inventory, track projects, and generate invoices — but they're becoming increasingly fragile and expensive to maintain. The risk grows daily: key personnel dependency — many legacy applications are maintained by one or two individuals who understand the codebase. When these individuals retire or leave (and many are nearing retirement age), the organization loses the ability to maintain or modify the application. This risk is acute in Seattle's competitive talent market where experienced developers have no interest in maintaining 20-year-old VB6 or COBOL applications. Platform end-of-life — the platforms these applications run on are reaching or have passed end-of-support. Windows Server 2012, SQL Server 2014, Oracle 10g, Java 8, and .NET Framework 4.x are all past or approaching end-of-support — meaning no security patches, no vendor support, and growing incompatibility with modern infrastructure. Integration impossibility — legacy applications were built before APIs, before cloud, before mobile, and before data analytics. They can't integrate with modern SaaS platforms, can't expose data for analytics, can't support mobile interfaces, and can't participate in automated workflows. Every new business requirement that involves the legacy application requires expensive workarounds — often involving manual data entry, CSV file transfers, or screen-scraping automation. Security vulnerability — legacy applications often have security architectures that predate modern threats. They may store passwords in plaintext, lack input validation (SQL injection vulnerability), have no encryption for data at rest, and use outdated authentication mechanisms. Every security audit flags these applications as critical risks. Government system modernization has become a political and operational priority in the Puget Sound region. Citizens who bank on their phones, order groceries through apps, and manage their lives digitally expect government services to be equally accessible. When applying for a building permit requires an in-person visit to a county office, or when checking the status of a benefits application requires a phone call during business hours, citizens experience a service gap that undermines trust in government. Washington State and King County have both increased technology modernization budgets, creating demand for legacy modernization expertise.
Seattle legacy app modernization demand spans government systems, enterprise applications, mainframe migration, and technical debt reduction. Government Systems: permitting and licensing (modernizing the systems that process building permits, business licenses, and regulatory approvals — replacing paper-based and legacy electronic systems with cloud-based platforms that support online application, real-time status tracking, automated review workflows, and mobile inspection reporting — for Seattle government: permitting modernization must handle the complexity of Seattle's regulatory environment — building permits involve multiple review departments (structural, mechanical, electrical, fire, environmental) with different review criteria and timelines, and the modernized system must coordinate these parallel reviews while providing applicants with real-time visibility into their permit status), benefits administration (modernizing the systems that administer public benefits — unemployment insurance, food assistance, healthcare coverage, and housing assistance — for Washington State: benefits systems must handle enormous transaction volumes during economic downturns (unemployment claims surged 10x during COVID) while maintaining accuracy, security, and compliance with federal and state program requirements), public records management (modernizing document and records management systems — enabling digital storage, searchability, retention policy enforcement, and public records request processing — for Seattle: public records modernization must comply with Washington State's Public Records Act (RCW 42.56) which requires government agencies to provide public records within 5 business days of request — modernized systems enable faster response and reduce the staff time devoted to records request processing), and citizen engagement platforms (building digital service delivery platforms that provide citizens with self-service access to government services — online applications, status tracking, payment processing, and communication with government staff — for Seattle: citizen platforms must be accessible (WCAG 2.1 AA compliance), multilingual (English, Spanish, Chinese, Vietnamese, Korean — reflecting Seattle's diverse population), and mobile-first (70%+ of citizens access government websites from mobile devices))). Enterprise Application Transformation: VB6/Access migration (migrating applications built on Visual Basic 6 and Microsoft Access to modern web-based platforms — for Seattle mid-market: VB6/Access applications are the most common legacy technology in small and mid-market companies — typically built by a technical employee who has since left the company, running on a single Windows PC, and doing something critical that no one fully understands until it breaks), .NET Framework modernization (upgrading .NET Framework applications to .NET 8+ or rewriting critical applications as cloud-native services — for Seattle enterprise: .NET modernization must preserve business logic that has been refined over years of operation while improving architecture, performance, and maintainability), Oracle Forms migration (replacing Oracle Forms applications with modern web interfaces while preserving the Oracle database and stored procedures — for Seattle: Oracle Forms migration is common in utilities, government, and financial services that adopted Oracle in the 2000s and now need web and mobile interfaces), and monolith decomposition (breaking monolithic applications into microservices or modular architectures that can be maintained, scaled, and evolved independently — for Seattle: monolith decomposition must be incremental — extracting one capability at a time from the monolith while keeping the overall system functional throughout the transition)). Mainframe Migration: COBOL application modernization (migrating COBOL applications from mainframe to cloud — approaches include: automated code conversion (using tools to convert COBOL to Java or C#), re-implementation (rewriting the business logic in a modern language using the COBOL code as specification), and encapsulation (wrapping mainframe functions with APIs to enable gradual migration) — for Seattle: COBOL migration must preserve the business rules embedded in decades of COBOL code — these rules represent institutional knowledge that may not be documented anywhere else), data migration (migrating data from mainframe databases (IMS, DB2 on z/OS, VSAM files) to modern databases (PostgreSQL, SQL Server, DynamoDB) — for Seattle: data migration must handle the data volumes and formats specific to mainframe environments — packed decimal fields, EBCDIC encoding, hierarchical database structures, and copybook-defined record layouts), and integration modernization (replacing mainframe-era integration (batch file transfers, screen scraping, terminal emulation) with modern API-based integration — for Seattle: integration modernization often delivers value before the mainframe migration is complete — wrapping mainframe functions with APIs enables modern applications to interact with mainframe data without waiting for the full migration)).
Our legacy app modernization for Seattle follows a risk-managed approach that preserves business continuity while systematically replacing aging technology. Phase 1 — Assessment and Strategy (2-4 weeks): understanding the legacy landscape before modernizing: application portfolio assessment (evaluating every legacy application — business criticality (what happens if it fails?), technical health (platform currency, code quality, security posture), maintenance cost and trajectory (is it getting more expensive to maintain?), and integration importance (do other systems depend on it?) — for Seattle: portfolio assessment produces a heat map that shows which applications need immediate attention (critical business function on end-of-life platform with single maintainer) vs. those that can be addressed over time), modernization approach selection (choosing the right modernization strategy for each application — rehost (move to cloud with minimal changes — fastest but least beneficial), replatform (move to cloud with platform upgrades — moderate benefit with moderate effort), refactor (restructure the code for cloud optimization — significant benefit with significant effort), rewrite (build a new application from scratch — maximum benefit but highest cost and risk), or retire (replace with a commercial product or eliminate the function entirely) — for Seattle: approach selection must balance risk, cost, and timeline — rewriting every legacy application would take years and millions of dollars, while rehosting everything would miss the opportunity to improve architecture and functionality), and migration roadmap (sequencing modernization projects based on: urgency (risk of failure), business impact (value of modernization), dependencies (which applications must be modernized before others), and resource availability (team capacity and budget) — for Seattle: migration roadmaps typically span 2-3 years with quarterly milestones and clear prioritization criteria)). Phase 2 — Modernization (8-20 weeks per application): executing the modernization: business logic extraction (understanding what the legacy application does — reverse-engineering business rules from source code, database schemas, and user interviews — for Seattle: business logic extraction is the most critical step because legacy applications often contain undocumented business rules that have been refined over decades — missing a rule during modernization means the new system will behave differently from the old one in ways that may not be discovered until they cause business problems), modern application development (building the replacement application using modern architecture — cloud-native deployment, API-based integration, responsive web interface, and mobile support — for Seattle: development must follow modern practices (CI/CD, automated testing, infrastructure as code) to avoid creating tomorrow's legacy application today), data migration (migrating data from legacy databases to modern platforms — with validation testing to ensure data integrity — for Seattle: data migration must preserve historical data that may be required for regulatory compliance, audit, or business reference — years of transaction history, customer records, and operational data), and parallel running (operating the new and legacy applications simultaneously to validate that the new application produces correct results — for Seattle: parallel running duration depends on criticality — financial applications may require 3-6 months of parallel running to validate through multiple business cycles))). Phase 3 — Transition and Decommissioning (2-4 weeks per application): switching to the new system: cutover planning (planning the transition from legacy to modern — timing (during low-activity periods), communication (notifying all stakeholders), training (ensuring users are prepared for the new system), rollback plan (ability to revert to the legacy system if critical issues arise), and support plan (intensive support during the first weeks of operation)), legacy decommissioning (shutting down the legacy application — archiving data, preserving documentation, terminating hosting and licensing, and verifying that no undiscovered dependencies exist — for Seattle: decommissioning must be thorough — legacy applications often have hidden dependencies that surface only when the application is turned off)).
Government / Municipal Permitting & Regulatory Services
A Pacific Northwest county — serving 900,000 residents across urban, suburban, and rural communities — needed to modernize its building permitting system. The county processed 42,000 permit applications annually (residential and commercial building permits, mechanical permits, electrical permits, plumbing permits, grading permits, and land use approvals) generating $28M in permit fee revenue. The existing permitting system was a custom application built in 2004 using classic ASP with a SQL Server 2008 backend. It had been modified extensively over 18 years by a succession of developers — the current codebase was 380,000 lines of ASP/VBScript with minimal documentation and no automated tests. The system was maintained by a single developer (a county employee with 15 years of tenure) who had announced plans to retire within 18 months. System limitations: no online application — all permit applications required an in-person visit to the county permit center. Applicants waited an average of 45 minutes to submit applications during peak periods (spring construction season). The permit center was open only 8 AM-4:30 PM Monday-Friday — requiring contractors and homeowners to take time off work to apply. No real-time status tracking — applicants could not check the status of their permit applications online. Status inquiries required phone calls to the permit center (average hold time: 12 minutes) or in-person visits. The county received 8,500 status inquiry calls per month, consuming 1,700 hours of staff time. Paper-based plan review — architectural and engineering plans were submitted as physical paper sets. Plan review involved routing paper plans between multiple review departments (structural, mechanical, electrical, fire, environmental). Plans were physically transported between departments and often sat in queues waiting for the next available reviewer. Average plan review time was 34 days (residential) and 68 days (commercial). No mobile inspection — inspectors recorded inspection results on paper forms in the field, then entered data into the legacy system when they returned to the office (typically the next day). This created a 1-2 day delay between inspection and system update, and inspector handwriting legibility was a recurring data quality issue. Integration limitations — the legacy system couldn't integrate with the county's GIS system (parcel data was manually cross-referenced), the assessor's system (property data was manually entered), or the county's financial system (permit fees were manually reconciled with revenue records). The county estimated that the permitting system's limitations cost: $1.4M annually in staff time devoted to manual processes that could be automated (data entry, status inquiries, paper routing, fee reconciliation), $2.8M annually in economic impact to the construction industry (contractor time wasted on in-person visits and delayed permits — estimated by the local homebuilders association), and unquantified citizen frustration reflected in consistently low satisfaction scores for permitting services (2.3/5 on the county's annual citizen survey — the lowest-rated county service).
We modernized the permitting system over 20 weeks — building a cloud-native platform that supported online application, digital plan review, mobile inspection, and real-time status tracking. Online Permit Application: self-service portal — citizens and contractors could apply for permits online 24/7: application wizard (a guided application process that asked questions in plain language — "Are you adding a new room to your house?" rather than "Select permit type from dropdown" — and determined the correct permit type, required documents, and applicable fees based on the answers), document upload (applicants uploaded plans, site plans, engineering reports, and other required documents as PDFs — with automated validation checking file format, resolution, and page dimensions), fee calculation and payment (automated fee calculation based on project scope and valuation — with online payment via credit card or ACH), GIS integration (the portal displayed the applicant's property on an interactive map — automatically pulling parcel data, zoning designation, flood zone status, and applicable overlay districts from the county GIS — eliminating manual data entry and ensuring accuracy), and contractor verification (for licensed contractors, the system verified their Washington State contractor registration (L&I license) in real-time — ensuring only properly licensed contractors submitted applications). Digital Plan Review: electronic plan review workflow — submitted plans were routed electronically to review departments: automated routing (plans automatically distributed to required review departments based on permit type and project characteristics — a commercial building permit was automatically routed to structural, mechanical, electrical, fire, environmental, and stormwater departments), digital markup (reviewers annotated plans digitally using Bluebeam-compatible tools — markups were visible to the applicant in real-time through the portal), parallel review (all departments reviewed simultaneously rather than sequentially — the system tracked review status by department and identified bottlenecks in real-time), review deadline tracking (SLA timers tracked review duration against county targets — automated escalation alerts when reviews approached deadlines), and consolidated review report (review comments from all departments consolidated into a single report for the applicant — clearly organized by department with specific plan sheet references for each comment). Mobile Inspection: field inspection app — inspectors used a mobile app on county-issued tablets: inspection scheduling (inspectors received daily inspection assignments based on geographic routing optimization — minimizing drive time between inspection sites), digital checklists (inspection-type-specific checklists with pass/fail criteria for each inspection point — ensuring consistent inspection standards across all inspectors), photo documentation (inspectors photographed conditions in the field — photos were automatically tagged with GPS location, timestamp, and inspection record — creating a visual record of construction progress), voice-to-text notes (inspectors dictated notes rather than handwriting — voice was transcribed in real-time and attached to the inspection record), real-time results (inspection results were posted to the permit record immediately — applicants and contractors could see results within minutes of the inspection rather than waiting 1-2 days), and offline capability (the app worked without internet connectivity — common in rural areas of the county — caching inspection data and synchronizing when connectivity was restored). Status Tracking and Communication: public-facing portal — applicants tracked permit status in real-time: permit dashboard (current status of all active permits associated with the applicant's account — submitted, under review, corrections requested, approved, inspection scheduled), review progress (visual progress indicator showing which departments had completed review and which were still in progress — with estimated completion dates based on current queue depth and processing times), automated notifications (email and SMS notifications for status changes — application received, review comments posted, corrections approved, permit issued, inspection results), and inspector scheduling (self-service inspection scheduling — applicants requested inspections through the portal for the next available date).
The system launched in a phased rollout — online application first (highest citizen impact), followed by digital plan review, mobile inspection, and full portal features over 8 weeks. Citizen Access (12 months): online application adoption: 78% of permit applications submitted online (up from 0%). In-person visits: decreased from 42,000 annually to 12,600 (70% reduction) — the permit center's walk-in volume decreased proportionally, enabling the county to reduce counter staff from 8 to 3 positions (5 staff redeployed to plan review, eliminating a backlog that had persisted for years). 24/7 availability: 34% of online applications were submitted outside traditional business hours (before 8 AM, after 4:30 PM, or on weekends) — demonstrating the demand for extended-hours access that was previously unmet. Status inquiry calls: decreased from 8,500 to 2,100 per month (75% reduction) — saving 1,275 staff hours per month that were redeployed to permit processing. Plan Review Performance: average residential plan review time: reduced from 34 days to 12 days (65% reduction) — driven by parallel review (all departments reviewing simultaneously rather than sequentially) and digital workflow (eliminating the physical plan routing between departments). Average commercial plan review time: reduced from 68 days to 28 days (59% reduction). Review cycle transparency: applicants could see exactly which department was reviewing their plans and the estimated completion time — eliminating the uncertainty that previously generated status inquiry calls. Inspection Efficiency: inspections per day per inspector: increased from 8.5 to 12.2 (44% improvement) — driven by geographic routing optimization and elimination of paperwork time at the end of each day. Inspection result availability: immediate (within minutes of completion) vs. previous 1-2 day delay. Data quality: inspection records were complete, legible, and photo-documented — eliminating the data quality issues from handwritten paper forms. Financial Impact (annual): staff efficiency: $680,000 in labor redeployment (8.5 FTEs of time freed from manual processes — counter staff, phone support, data entry, paper routing — redeployed to permit processing and plan review rather than eliminated through layoffs). Revenue acceleration: $420,000 in earlier permit fee collection (faster processing meant fees were collected weeks earlier — improving the county's cash flow). Inspection efficiency: $320,000 in vehicle and time savings (44% more inspections per day meant the same inspection volume could be handled with fewer inspector-days). Economic impact: the local homebuilders association estimated that faster permitting reduced construction project timelines by an average of 18 days — representing $4.2M in reduced construction financing costs across the county's construction industry. Citizen satisfaction: permitting satisfaction score improved from 2.3/5 to 4.1/5 on the county's annual citizen survey — moving from the lowest-rated to among the highest-rated county services. Platform development cost: $840,000 (20 weeks). Annual operating cost: $132,000 (AWS infrastructure, GIS integration, support). ROI: 1.7:1 in the first year on direct county savings (higher when including economic impact on the construction industry).
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.
Seattle legacy modernization providers include government technology specialists, enterprise modernization firms, mainframe migration companies, and general software development firms. (1) Government technology specialists (Tyler Technologies, Accela) — purpose-built government platforms but may not handle the specific requirements of each county/city's unique permitting processes. (2) Enterprise modernization firms — strong migration methodology but may lack the domain expertise for government, utilities, or financial services. (3) Mainframe migration companies (Micro Focus, Astadia) — specialized in COBOL migration but may default to automated code conversion that preserves mainframe-era architecture in cloud infrastructure. (4) General development firms — can build modern applications but may lack the legacy reverse-engineering skills needed to understand 20-year-old codebases. ZTABS combines legacy system expertise with modern development capabilities — understanding both the old technology (COBOL, VB6, classic ASP, Oracle Forms) and the new (cloud-native, microservices, modern web/mobile) to execute successful modernization.
Legacy app modernization in Seattle varies by application complexity, modernization approach, and data migration scope. Small application modernization (single department, limited complexity, 6-10 weeks): $100,000-$250,000. Enterprise application modernization (business-critical, complex logic, data migration, 12-18 weeks): $300,000-$600,000. Government/mainframe modernization (large-scale, multi-department, complex compliance, 16-24 weeks): $500,000-$1,200,000. Ongoing: $6,000-$18,000/month for cloud hosting, support, and continuous improvement. ZTABS delivers at $230-330/hr — modernization engineers with Seattle government, enterprise, and mainframe expertise.
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 Seattle businesses
Reverse engineering: we analyze the legacy source code, database schemas, and application behavior to reconstruct the business logic. This involves: automated code analysis (tools that map code structure, data flows, and logic paths), database schema analysis (understanding data relationships, stored procedures, and triggers), user observation (watching current users operate the system to understand workflows the code implements), and stakeholder interviews (talking to people who have used the system for years and understand its business purpose). This process typically takes 2-4 weeks depending on application complexity.
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 Seattle, WAZTABS is a remote-first web development agency serving Seattle businesses — including full-stack development, progressive web apps, api development. We work with Cloud Computing, E-commerce & Retail Tech, AI & Machine Learning companies in Seattle, WA 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 Seattle, WAZTABS is a remote-first web design agency serving Seattle businesses — including ui/ux design, responsive design, custom interfaces. We work with Cloud Computing, E-commerce & Retail Tech, AI & Machine Learning companies in Seattle, WA 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 Seattle, WAZTABS is a remote-first AI development agency serving Seattle businesses — including llm integration & fine-tuning, ai agents & automation, rag & knowledge systems. We work with Cloud Computing, E-commerce & Retail Tech, AI & Machine Learning companies in Seattle, WA 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 Seattle. Get a free consultation today.
