ZTABS modernizes legacy applications for Los Angeles's public agencies, entertainment companies, healthcare systems, and established businesses — public transit system modernization for LA Metro and municipal transit operators running scheduling, dispatch, fare collection, and passenger information systems on platforms built 15-25 years ago that can't integrate with modern mobility services, real-time passenger apps, or the data analytics that federal funding now requires, entertainment production pipeline migration helping studios and VFX houses move from on-premise legacy tools and proprietary workflows built over decades to cloud-native, AI-ready platforms that enable remote collaboration and the production velocity the streaming era demands, and government system replacement for LA County and City departments running mission-critical services on COBOL mainframes, legacy Oracle forms, and end-of-life platforms that create security vulnerabilities, operational bottlenecks, and the inability to deliver modern citizen-facing digital services.
Los Angeles legacy app modernization addresses organizations trapped by aging technology that constrains operations and creates risk. Public transit legacy systems: LA Metro — the county's primary transit agency, operating 93 bus routes and 6 rail lines carrying 900,000+ daily boardings — runs core operations on systems designed in a different era. Scheduling systems that were cutting-edge in 2005 can't handle the dynamic service adjustments needed for modern transit (real-time rerouting around incidents, demand-responsive service, integration with ride-share and micro-mobility). Fare collection systems designed for cash and magnetic-stripe cards struggle to incorporate mobile payment, account-based fares, and fare capping. Passenger information systems that rely on scheduled timetables can't provide the real-time arrival predictions that riders expect. Modernizing these systems while maintaining daily service for 900,000+ riders is one of the most complex technology challenges in Los Angeles. Government COBOL problem: LA County government departments — social services, public health, property tax, voter registration, and criminal justice — still run critical applications on mainframe systems, many written in COBOL. These systems process millions of transactions daily and can't simply be turned off. But they create significant problems: the COBOL programmer workforce is aging and retiring (average age: 60+), mainframe hardware maintenance costs escalate annually, the systems can't integrate with modern digital services (online portals, mobile apps, APIs), and security vulnerabilities in end-of-life systems create cyber risk. The State of California has been pushing county departments to modernize — but replacement of systems that have been customized over 20-30 years requires careful planning to preserve business logic and data integrity. Entertainment pipeline debt: LA's entertainment production companies and VFX studios have accumulated decades of technology debt — proprietary tools, custom scripts, and manual workflows that were innovative when created but now limit operational efficiency. A VFX studio might run a proprietary shot management system built in 2008, connected to a custom render farm manager from 2012, integrated with an asset management system that only runs on a specific Linux distribution from 2015. These interconnected legacy systems work — but they can't be extended, they require specialized knowledge to maintain (often knowledge held by a single engineer who built the system), and they prevent adoption of modern cloud, AI, and collaboration tools. Healthcare platform aging: LA healthcare organizations run clinical and administrative applications that are reaching end of life — older versions of EHR systems that vendors no longer support, custom billing applications built on deprecated frameworks, and clinical decision support tools that can't incorporate current evidence. Modernizing these systems while maintaining clinical operations — you can't take a hospital's systems offline for migration — requires careful planning, parallel running, and incremental cutover.
Los Angeles legacy app modernization demand spans transit, government, entertainment, and healthcare. Transit System Modernization: scheduling and dispatch (modernizing transit scheduling and dispatch systems — from static-schedule-based operations to dynamic, real-time systems that optimize vehicle deployment based on demand patterns, traffic conditions, and service goals — for LA Metro: the modernized system must handle the complexity of LA's transit network — 2,000+ buses across 93 routes with different service patterns (local, rapid, express), real-time rerouting capability for incidents (and LA has many — accidents, road closures, special events), and integration with the upcoming congestion pricing program), fare collection modernization (replacing legacy fare collection with modern, account-based systems — mobile payment (TAP app), contactless bank cards, fare capping (daily and weekly caps that reward frequent riders), and reduced-fare programs (seniors, students, low-income riders) — for LA transit: the new fare system must handle the 900,000+ daily boardings across bus and rail with sub-second tap times — a fare transaction that takes 2 seconds instead of 0.5 seconds creates boarding delays that cascade across the entire system), and passenger information (modernizing passenger information from static timetables to real-time predictions — GPS-based vehicle tracking, arrival predictions using machine learning (accounting for traffic patterns, weather, and historical performance), and multi-modal trip planning (combining bus, rail, bike-share, and ride-hail into optimized trip recommendations) — for LA transit: passenger information must be accessible in English, Spanish, Chinese, Korean, and other languages — and must work across the website, mobile app, station displays, and bus stop signs)). Government System Modernization: mainframe migration (migrating applications from mainframe/COBOL to modern platforms — for LA County: mainframe migration follows a structured approach — extracting business rules encoded in COBOL (often undocumented, accumulated over 20-30 years), rewriting in modern languages (Java, Python, C#), validating that the new system produces identical outputs to the legacy system for all test cases, and gradually transitioning processing from mainframe to modern platform — the risk: mainframes process millions of daily transactions for social services, property tax, and other critical functions — any data loss or processing error affects residents who depend on these services), citizen-facing digital services (building modern web and mobile interfaces to replace the paper forms, in-person visits, and phone calls that legacy systems require — online benefit applications (CalFresh, Medi-Cal, CalWORKs), permit applications (building permits, business licenses), and information requests (property records, court records, vital records) — for LA government: digital services must be accessible — WCAG 2.1 compliant, multilingual, and designed for the full range of LA's population including residents with limited technology access), and data modernization (migrating data from legacy formats (flat files, hierarchical databases, proprietary formats) to modern databases and data warehouses — enabling analytics, reporting, and integration that legacy data stores can't support — for LA government: data modernization must preserve historical data integrity — decades of records that support ongoing cases, claims, and legal proceedings must be migrated accurately and remain accessible)). Entertainment Pipeline Modernization: production tool migration (migrating proprietary production tools to modern platforms — custom shot management systems to ShotGrid (Autodesk) or ftrack, custom asset management to modern DAM platforms, and custom pipeline tools to standardized, maintainable alternatives — for LA VFX: pipeline migration must maintain production continuity — studios can't stop taking projects while migration happens — we migrate tools incrementally, running old and new systems in parallel, and transition project-by-project), cloud migration (migrating on-premise infrastructure to cloud — render farms to cloud compute, local storage to cloud object storage, on-premise workstations to cloud desktops — for LA entertainment: cloud migration enables the remote and hybrid work that modern production requires — but the migration must handle the massive data volumes (petabytes of media assets) and the performance requirements (artists need sub-20ms latency to their cloud workstations)), and workflow automation (replacing manual workflows with automated pipelines — automated quality checks, automated asset processing, automated delivery packaging, and automated compliance verification — for LA entertainment: workflow automation replaces the tribal knowledge of "how we do things here" with documented, repeatable, and improvable processes — reducing dependency on specific individuals and enabling the scaling of operations)). Healthcare System Modernization: EHR migration (migrating from end-of-life or unsupported EHR versions to current platforms — including data migration (preserving complete patient histories), workflow redesign (adapting clinical workflows to the new system), integration reconnection (rebuilding interfaces with labs, pharmacies, and other systems), and training (ensuring clinicians can use the new system effectively) — for LA healthcare: EHR migration must maintain clinical operations — you can't tell a hospital "no new patients for 2 weeks while we migrate" — migration is done in waves, department by department, with parallel running to catch issues before full cutover), and custom application replacement (replacing custom-built clinical and administrative applications with modern alternatives — for LA healthcare: many healthcare organizations have custom applications built 10-20 years ago on deprecated platforms (.NET Framework 2.0, Classic ASP, PHP 5) — these applications often contain critical business logic that isn't documented — modernization requires extracting that logic and reimplementing it on supported platforms)).
Our legacy app modernization for Los Angeles follows a risk-managed methodology. Phase 1 — Assessment (2-3 weeks): understanding the legacy landscape: application inventory (cataloging all legacy applications — technology stack, dependencies, integrations, data stores, user base, and business criticality — for LA: legacy landscapes are often larger than organizations realize — a "single application" may actually be 5-10 interconnected components, each with different technology and different maintenance challenges), business rule extraction (identifying and documenting the business rules encoded in legacy applications — for government COBOL: this is the most critical and challenging step — business rules accumulated over 20-30 years are often undocumented, embedded in code, and understood by only 1-2 people — extracting these rules before they're lost to retirement is essential — we use automated code analysis tools combined with stakeholder interviews to capture business logic), and risk assessment (evaluating the risks of modernization vs. the risks of not modernizing — for LA transit: modernization risks include service disruption, data loss, and user adjustment — but not modernizing risks include system failure (the legacy system eventually breaks with no path to recovery), increasing maintenance costs, and inability to improve service — the assessment quantifies both sides to inform the modernization strategy)). Phase 2 — Strategy (1-2 weeks): choosing the modernization approach: approach selection (selecting the right modernization strategy for each application: rehost (move to cloud without code changes — fastest but least beneficial), replatform (move to modern infrastructure with minimal code changes), refactor (restructure code for modern architecture), rebuild (rewrite from scratch using modern technology), or replace (adopt a commercial product) — for LA: each legacy application may warrant a different approach — some are best rebuilt, others are best replaced — the strategy matches the approach to the application's business value, technical condition, and organizational readiness), migration planning (planning the migration sequence — which applications move first, dependencies between migrations, data migration strategies, and rollback plans — for LA transit: migration planning must account for service schedules — major system changes happen during low-ridership periods (overnight, weekends) — with rollback capability if issues are detected before the morning rush), and parallel running design (designing the parallel operation period — how long old and new systems run simultaneously, how transactions are processed in both systems, how results are compared, and the criteria for cutting over from old to new — for LA government: parallel running is essential for mission-critical systems — processing the same social services cases through both old and new systems and comparing results catches discrepancies before the legacy system is decommissioned)). Phase 3 — Modernization (8-24 weeks): executing the migration: incremental migration (migrating in phases rather than big-bang cutover — for transit: one bus route or one rail line at a time — for government: one program or one function at a time — for entertainment: one project or one tool at a time — incremental migration limits risk and enables learning from each phase), data migration (migrating data from legacy stores to modern databases — with validation at every step — for LA government: data migration for systems with 20-30 years of history requires extreme care — a single missing record could affect a resident's benefits, tax assessment, or legal case — we implement triple-validation: source count verification, transformation validation, and target data integrity checks), and integration rebuilding (reconnecting integrations between the modernized application and other systems — for LA healthcare: EHR integrations with labs, pharmacies, imaging centers, and billing systems must be rebuilt and tested — a broken lab interface means test results don't reach the ordering physician — integration testing is comprehensive and includes failure scenario testing)). Phase 4 — Stabilization (2-4 weeks): ensuring the modernized system operates reliably: hypercare (providing enhanced support immediately after migration — extended monitoring, faster response times, and on-site presence during critical periods — for LA transit: hypercare during the first week includes on-call engineers during morning and evening rush hours — ready to respond instantly if the new system shows issues), performance tuning (optimizing the modernized system's performance — identifying and resolving bottlenecks that only appear under production load — for LA government: performance tuning ensures the modernized system handles peak loads — social services systems experience peak usage at the beginning of each month when benefits are processed — the system must handle this load without degradation), and legacy decommissioning (safely shutting down the legacy system after the modernized system is validated — archiving legacy data, documenting the decommissioned system for historical reference, and terminating legacy infrastructure — for LA: legacy decommissioning includes cost recovery — canceling mainframe contracts, recycling hardware, and reallocating data center space — these savings often offset a significant portion of the modernization investment)).
Transportation / Municipal Transit System Operations
A municipal transit operator serving 3 cities in Los Angeles County — operating 42 fixed-route bus lines and 6 paratransit/dial-a-ride services with a fleet of 280 vehicles carrying 48,000 daily boardings — ran operations on systems installed between 2003 and 2010. Legacy system landscape: scheduling system (Trapeze — version from 2008, running on a Windows Server 2008 instance that was 4 years past end of support — the system created static schedules that operators followed rigidly — no capability for real-time service adjustments, no integration with traffic data, and no demand-responsive scheduling), CAD/AVL system (computer-aided dispatch and automatic vehicle location — a 2006 installation that tracked bus positions using cellular communication with 30-60 second update intervals — dispatchers saw bus locations on a map but couldn't correlate position with schedule adherence in real-time — the system's mapping hadn't been updated to reflect road changes in 8 years), fare collection (GFI Odyssey fareboxes installed in 2005 — accepting cash and magnetic-stripe cards only — no contactless payment, no mobile payment, no account-based fares — data was extracted nightly via serial connection at the bus yard), passenger information (static schedules posted at bus stops — no real-time arrival information — the agency's website showed PDF timetables — no real-time information, no trip planner, no mobile app), and reporting (ridership, on-time performance, and financial data were compiled manually from nightly data downloads — monthly NTD (National Transit Database) reports required 3 weeks to compile — FTA (Federal Transit Administration) reporting for federal grants consumed significant staff time). Operational impact: on-time performance was 71% (below the 80% target) — partly because the scheduling system couldn't account for actual traffic conditions and partly because dispatchers couldn't intervene effectively without real-time data. Ridership had declined 18% over 5 years — attributed partly to the lack of real-time information and mobile tools that riders expected. The agency was pursuing a $45M FTA grant for bus rapid transit — the grant required demonstration of modern technology capabilities that the legacy systems couldn't provide.
We modernized the transit operations platform over 20 weeks, replacing legacy systems while maintaining daily service for 48,000 riders. Modern CAD/AVL Platform: replacing the 2006 tracking system with a real-time operations platform. Vehicle tracking: GPS tracking with 3-second update intervals (vs. 30-60 seconds previously) — providing dispatchers with real-time vehicle positions accurate to within 5 meters. Schedule adherence: real-time comparison of actual vehicle position to scheduled position — displaying whether each bus was early, on-time, or late — with automated alerts when a bus deviated beyond threshold (3+ minutes late, 2+ minutes early). Dynamic dispatch: dispatchers could communicate with operators in real-time (text messages to the driver's MDT — mobile data terminal), adjust service in response to incidents (reroute buses around an accident), and deploy reserve vehicles to fill gaps. Automated passenger announcements: next-stop announcements triggered by GPS position rather than manual operator activation — ensuring ADA compliance and improving the rider experience. Intelligent Scheduling: replacing static schedules with data-informed, optimizable scheduling. Historical analysis: the new system analyzed historical ridership data, traffic patterns, and on-time performance to identify scheduling inefficiencies — routes where buses consistently ran late due to traffic, time periods where demand exceeded capacity, and deadhead (out-of-service) miles that could be reduced. Schedule optimization: creating schedules that accounted for actual traffic conditions — allocating more running time on congested segments rather than using uniform speeds — reducing the gap between scheduled and actual performance. Service adjustments: the system enabled seasonal and event-based schedule adjustments — increasing frequency during school hours, adjusting for major events (Dodgers games, concerts at the Forum), and implementing holiday schedules — changes that were cumbersome with the legacy system became straightforward. Fare Modernization: a new fare collection system supporting modern payment methods. Account-based fares: riders registered accounts (online or via mobile app) linked to contactless cards (new TAP-compatible cards) or mobile phones — fares were calculated based on actual trips taken rather than requiring advance purchase of specific fare products. Mobile payment: riders paid by tapping their phone (NFC) on the farebox validator — Apple Pay, Google Pay, and the agency's own mobile app — eliminating the need for exact change or physical fare cards. Fare capping: the system tracked daily and weekly fare expenditure — once a rider reached the equivalent of a day pass ($5) or weekly pass ($18), additional trips were free — fare capping provided day-pass and week-pass benefits without requiring riders to pre-commit to a pass purchase. Reduced fare: automated reduced-fare programs for seniors, students, and low-income riders — verified through the account system rather than requiring visual inspection by operators. Real-Time Passenger Information: providing riders with the information they expected. Real-time predictions: machine learning models predicted arrival times based on current vehicle position, traffic conditions, historical patterns, and schedule — predictions were more accurate than schedule alone (especially during congested periods when buses ran late). Multi-channel delivery: real-time arrival information delivered through: the agency website (responsive design), a mobile app (iOS and Android), Google Maps integration (predictions appeared in Google Maps trip planning), digital signs at 120 high-ridership bus stops, and a text-message service (riders texted a stop number and received next arrival times). Trip planner: multi-modal trip planning that combined the agency's bus service with LA Metro rail, neighboring transit agencies, and bike-share — showing riders the fastest route using any combination of transit modes. Data and Reporting Platform: a modern analytics platform replacing manual reporting. Automated NTD reporting: ridership, vehicle revenue miles, vehicle revenue hours, and other NTD metrics calculated automatically from operational data — monthly NTD reports generated in hours rather than weeks. Performance dashboards: real-time and historical dashboards showing on-time performance, ridership by route and time period, fare revenue, and vehicle utilization — accessible to operations staff, management, and board members. FTA grant compliance: the data platform generated the performance reports required for the $45M BRT grant application — demonstrating the technology capabilities that the legacy system couldn't provide.
The modernization was deployed in 3 phases — CAD/AVL and dispatch (Phase 1, Weeks 8-12), fare collection (Phase 2, Weeks 12-16), and passenger information (Phase 3, Weeks 16-20). Each phase was deployed during a weekend with fallback procedures ready. Service Performance: on-time performance: improved from 71% to 84% within 6 months — the combination of realistic scheduling (based on actual traffic patterns) and real-time dispatch (intervening when buses fell behind schedule) dramatically improved reliability. Service interruption response: average time to reroute service around an incident reduced from 28 minutes to 6 minutes — real-time vehicle tracking and dispatch communication enabled rapid response. Schedule efficiency: deadhead miles reduced by 14% — scheduling optimization reduced unproductive vehicle movement. Ridership Impact: ridership: increased 8.2% in the first year — reversing the 5-year decline — attributed to: improved reliability (riders trust the schedule), real-time information (riders know when the bus is actually coming, reducing perceived wait time), and mobile payment (removing the exact-change barrier). New rider acquisition: 22% of mobile app users were riders who hadn't used the system in the prior year — the modern rider experience attracted new and returning riders. Fare Revenue: fare revenue: increased 12% — driven by ridership growth and reduced fare evasion (account-based fares and validators made fare payment easier and more visible). Cash handling: reduced from 34% of fare transactions to 8% — mobile and card payments dominated — reducing cash counting, secure transport, and reconciliation costs by $180K annually. Fare capping: 28% of regular riders reached daily or weekly caps — these riders previously purchased individual fares (paying more in total) — fare capping provided better value while increasing ridership from these frequent riders. Operational Efficiency: NTD reporting: reduced from 3 weeks to 2 days per month — freeing staff for operational improvement rather than data compilation. Dispatch effectiveness: dispatcher intervention (holding, expressing, rerouting) increased from 12 per day (limited by visibility) to 48 per day (enabled by real-time data) — each intervention improved rider experience by maintaining service reliability. FTA Grant: the $45M BRT grant application was submitted with the technology demonstration that the legacy system couldn't provide — the agency was selected for the grant, enabling the bus rapid transit project that will transform service on the agency's highest-ridership corridor. Financial Summary: modernization project: $1.2M (20 weeks including hardware). Annual operating cost: $180K (cloud hosting, system licenses, cellular data for vehicle tracking). Year 1 value: fare revenue increase ($640K — 12% increase on base revenue), cash handling reduction ($180K), staff efficiency ($220K — reporting and dispatch), and ridership growth (contributing to farebox recovery ratio improvement that supported the $45M FTA grant eligibility). Total Year 1 value: $1.04M against $1.38M total first-year cost (project + operating). Year 2 onward: annual value of $1.04M+ against $180K operating cost. The $45M FTA grant — directly enabled by the modernized technology platform — represented the highest-value outcome of the modernization, transforming the agency's capital program.
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.
Los Angeles legacy app modernization providers include transit technology vendors, government IT contractors, and general modernization consultancies. (1) Transit technology vendors (Trapeze, Clever Devices, Conduent) — sell products rather than custom modernization services. (2) Government IT contractors (CGI, Deloitte, Accenture) — handle large-scale government modernization but at significant cost. (3) General modernization consultancies — technical capability but lacking domain expertise in transit operations, government workflows, and entertainment production pipelines. ZTABS provides legacy modernization with domain expertise — understanding not just how to modernize the technology but how the business operates and what the modernized system must do.
Legacy app modernization in Los Angeles varies by application complexity and migration approach. Assessment and Strategy (legacy audit, business rule extraction, migration planning, 2-4 weeks): $30,000-$80,000. Application Modernization (single application, rebuild or replatform, 8-16 weeks): $150,000-$450,000. Platform Modernization (multi-application, phased migration, 16-30 weeks): $500,000-$1,500,000. Ongoing: $5,000-$20,000/month for post-migration support and optimization. ZTABS delivers at $200-300/hr — modernization engineers with LA transit, government, and entertainment domain 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 Los Angeles businesses
We deploy changes during low-ridership periods (overnight, weekends) with full rollback capability. The legacy system remains operational until the new system is validated in production. For fare collection, we run new and old systems in parallel — riders can use either payment method during the transition. For CAD/AVL, we install new vehicle equipment incrementally (10-20 buses per week) and run old and new tracking simultaneously until the entire fleet is converted. Service to riders is never interrupted.
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 Chicago, ILZTABS is a remote-first legacy app modernization agency serving Chicago businesses — including incremental modernization, business logic preservation, data migration. We work with Finance & Trading, Manufacturing, Transportation & Logistics companies in Chicago, IL 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 Los Angeles, CAZTABS is a remote-first web development agency serving Los Angeles businesses — including full-stack development, progressive web apps, api development. 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 Design in Los Angeles, CAZTABS is a remote-first web design agency serving Los Angeles businesses — including ui/ux design, responsive design, custom interfaces. 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.
AI Development in Los Angeles, CAZTABS is a remote-first AI development agency serving Los Angeles businesses — including llm integration & fine-tuning, ai agents & automation, rag & knowledge systems. 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.
Legacy App ModernizationLearn more about our legacy app modernization services nationwide.
Partner with ZTABS for expert legacy app modernization in Los Angeles. Get a free consultation today.
