ZTABS modernizes legacy applications for Riyadh organizations — COBOL mainframe migration to cloud-native architectures, Oracle Forms and PowerBuilder replacement with modern web platforms, and ERP modernization aligning Saudi government and enterprise systems with Vision 2030 digital transformation mandates.
Saudi Arabia's Vision 2030 digital transformation has created an urgent mandate: modernize legacy systems or fall behind. Government entities and large Saudi enterprises — banks, utilities, petrochemical companies, and: healthcare providers — operate critical business processes on systems built 15-30 years ago. These systems work (some remarkably well), but they create barriers that Vision 2030 demands be removed: integration impossibility (legacy systems cannot connect to modern digital services — mobile apps, citizen portals, AI and analytics platforms, and: partner APIs all require: modern integration interfaces that: mainframe COBOL programs, Oracle Forms applications, and: PowerBuilder clients cannot provide), talent cliff (the engineers who built and maintain these systems are retiring. Finding a COBOL developer in Riyadh in 2026 is: nearly impossible. Finding one who understands: both the COBOL codebase and the Saudi business process it implements: essentially impossible. Each retirement removes: irreplaceable institutional knowledge), scaling limitations (legacy systems designed for: office-hour usage by internal staff cannot handle: citizen-facing digital services where 35 million Saudis access government services 24/7; the performance characteristics, session management, and: user experience assumptions are fundamentally incompatible with: digital-first service delivery), and cybersecurity exposure (systems running on: unsupported operating systems, unpatched middleware, and: deprecated security protocols create: attack surfaces that: modern cybersecurity controls cannot adequately protect; NESA cybersecurity requirements increasingly difficult to meet with: legacy infrastructure). The Saudi modernization challenge is distinct from markets like the US or Europe because: pace is accelerated (Vision 2030 deadlines create: hard timelines for digital transformation — government entities cannot: modernize gradually over a decade; the mandate is: digitize critical services within specific program timelines), Arabic requirements (modernized systems must support: Arabic language interfaces, right-to-left UI, Hijri calendar, and: Saudi-specific business rules; legacy systems often: hardcode these requirements in ways that make: migration more complex than simple language translation), sovereign cloud (Saudi data must remain in Saudi Arabia — government data in particular must be hosted on: Saudi-resident cloud infrastructure; modernized applications must deploy on: local cloud providers or hyperscaler Saudi regions), and integration with national platforms (modernized systems must integrate with: Absher (citizen identity), Yakeen (ID verification), SADAD (payment), and: other Saudi national digital platforms — these integrations didn't exist when: the legacy systems were built). Common legacy systems in Riyadh include: COBOL mainframes (government financial systems, banking core systems, and: insurance processing — running business logic written: 20-30 years ago on IBM AS/400 or similar platforms), Oracle Forms (enterprise applications built on Oracle Forms 6i/10g — HR systems, inventory management, procurement, and: financial reporting applications; the Oracle Forms technology: deprecated by Oracle with: no modern development path), PowerBuilder (client-server applications — common in: Saudi banking and financial services; desktop applications with: direct database connections; impossible to: deploy as web or mobile applications), and custom COBOL/RPG on AS/400 (Saudi-specific business applications on IBM AS/400 — payroll systems implementing: Saudi labor law calculations, government fee processing systems, and: utility billing systems with: decades of accumulated business rules).
Riyadh legacy modernization demand spans government, banking, utilities, and healthcare. Government: Saudi government legacy modernization needs: citizen service digitization (government entities transforming: counter-based services into: digital self-service through Absher, Tawakkalna, and: ministry-specific portals; the backend systems processing these requests: often still mainframe-based — the citizen sees a modern mobile app, but: the request is processed by a COBOL batch job running overnight), financial systems (government financial management systems — budgeting, accounting, procurement, and: payment processing running on: legacy platforms; Ministry of Finance modernization requiring: migration to modern ERP or cloud-native financial platforms), HR and payroll (government employee management systems — 1.2 million government employees managed through: legacy HR systems implementing: Saudi labor law, Government Employment Act provisions, and: complex compensation rules accumulated over decades; modernization must preserve: every business rule while enabling: self-service HR through modern interfaces), and document management (government records management transitioning from: paper-based and legacy document management systems to: digital-first records with: electronic signatures, workflow automation, and: archival compliance). Banking: Saudi banking legacy modernization needs: core banking modernization (Saudi banks running: core banking systems implemented 15-25 years ago — primarily Temenos T24, Misys/Finastra, or custom COBOL; these systems process: millions of daily transactions reliably but: cannot support: real-time open banking APIs, instant payment integration with SARIE, and: the digital banking experiences that: customers increasingly demand), channel integration (mobile banking, online banking, ATM, branch, and: call center systems each: built separately over different decades; modernization creating: an omnichannel platform where: customers have a consistent experience regardless of channel), card processing (credit and debit card processing systems — issuance, authorization, settlement, and: fraud detection — running on: legacy platforms; SAMA regulations requiring: real-time fraud detection and: instant card controls that: batch-processing legacy systems cannot provide), and regulatory reporting (SAMA reporting requirements growing in: complexity and frequency — legacy systems producing reports through: manual data extraction and Excel-based compilation; modernization enabling: automated regulatory reporting from: integrated data sources). Utilities: Saudi utility legacy modernization needs: billing modernization (electricity, water, and: telecom billing systems processing: millions of accounts monthly on legacy platforms; customer self-service requiring: real-time usage data, online payment, and: account management that: batch-processing billing systems cannot provide), smart grid integration (Saudi electricity transitioning to: smart meters and IoT-connected infrastructure; legacy billing and operations systems: incompatible with: real-time smart meter data ingestion and processing), and field service (utility field operations managed through: paper-based or early-generation mobile systems; modernization deploying: mobile workforce management integrated with: GIS, asset management, and: customer service systems). Healthcare: Saudi healthcare legacy modernization needs: EHR migration (hospitals running: legacy electronic health record systems — some still partially paper-based; Ministry of Health's Seha platform requiring: integration with modern EHR systems that: legacy hospital information systems cannot provide), claims processing (health insurance claims processing through: legacy systems implementing: CCHI regulations; modernization enabling: real-time eligibility verification, automated claims adjudication, and: fraud detection), and laboratory integration (laboratory information systems running on: outdated platforms; modernization enabling: integration with: national health data exchange, electronic prescribing, and: patient portal access to results).
Our Riyadh legacy modernization follows a structured methodology: assessment, strategy, migration, and stabilization — designed for Saudi business context. Assessment: (1) We begin with comprehensive legacy system analysis: code analysis (automated scanning of: legacy codebase — COBOL, RPG, Oracle Forms, PowerBuilder — measuring: codebase size, complexity, dead code, and: dependency mapping; understanding: what the code actually does vs. what documentation says it does — legacy documentation is invariably: incomplete or inaccurate), business rule extraction (the most critical activity: identifying and documenting: every business rule embedded in the legacy code; Saudi-specific rules: Saudi labor law calculations in payroll, Zakat and tax computations, Hijri calendar-dependent processing, and: government regulation implementations — these rules are: intellectual property that must not be lost in modernization), integration mapping (documenting: every system the legacy application connects to — databases, file transfers, API calls, batch interfaces, and: manual data exchanges; understanding: the full integration landscape is essential for: planning the modernization without breaking: downstream and upstream system dependencies), and user workflow analysis (observing: how users actually use the legacy system — often: differently from how it was designed; Saudi government clerks and bank operators have: developed workarounds, shortcuts, and: informal procedures around the legacy system's limitations; the modernized system must accommodate: these real workflows, not just the documented ones). Strategy: (1) We select the modernization approach based on assessment findings: replatform (move the application to modern infrastructure without significant code changes — the fastest path but: limited modernization benefit; suited for: applications that work well functionally but run on: unsupported infrastructure), refactor (restructure the codebase for modern architecture while preserving business logic — moderate effort with: significant modernization benefit; suited for: applications with sound business logic but: outdated code structure), rebuild (develop a new application implementing: the extracted business rules on a modern platform — highest effort but: maximum modernization benefit; suited for: applications where the codebase is: unmaintainable and the business logic must be preserved in a completely new implementation), and replace (adopt a commercial platform (ERP, CRM, or domain-specific software) configured to: implement the required business rules; suited for: applications where commercial software now covers: the functionality that was custom-built 20 years ago because commercial options didn't exist). Migration execution: (1) We execute migration with data preservation as the supreme priority: parallel operation (legacy and modern systems running simultaneously for: a defined period — typically 2-6 months; every transaction processed by both systems and: results compared; discrepancies investigated and resolved before: cutover), data migration (migrating: decades of accumulated data — customer records, transaction history, financial data — with: full validation; Saudi government and banking data: migration must account for: Arabic text encoding variations, Hijri date formats, and: historical data that may predate: modern encoding standards), phased cutover (migrating: one module or one department at a time — not a big-bang switch; each phase: validated and stabilized before: the next phase begins; the cutover plan: defining rollback procedures for each phase in case: critical issues emerge), and knowledge transfer (ensuring: the client's team can operate and maintain the modernized system; training: Saudi IT staff on: the new technology stack, operational procedures, and: troubleshooting; addressing: the knowledge gap between: legacy technology expertise and: modern technology skills).
Government / Public Services
A Saudi government entity responsible for commercial licensing modernized its legacy license processing system. The problems: (1) System age: the core processing system was built in 2003 on Oracle Forms 6i with an Oracle 9i database running on: on-premises SPARC Solaris servers. The system processed: 450,000 license applications annually — new registrations, renewals, amendments, and cancellations. The system had been modified continuously for 20 years: 2,400 Oracle Forms screens, 1,800 PL/SQL packages, and approximately 3.2 million lines of code. (2) Operational risks: the Solaris servers: running Oracle 9i (desupported since 2010) on SPARC hardware that: HP/Oracle no longer manufactured replacement parts for. One critical server failure: would require 6-8 weeks to source replacement parts. The IT team: 4 developers who understood the system — all in their 50s and 60s, all planning retirement within 5 years. No new graduates: had Oracle Forms or PL/SQL skills. (3) Citizen service limitation: the system processed applications in: batch mode — applications submitted during the day, processed overnight, results available next business day. The Vision 2030 mandate: real-time digital licensing through the national service portal — citizens applying and receiving: instant or same-day responses. The Oracle Forms system: fundamentally incapable of: real-time web-based processing. (4) Integration requirement: the entity needed to integrate with: Absher (citizen identity verification), Yakeen (information validation), SADAD (payment processing), and: Etimad (government procurement) — all through: modern REST APIs. The legacy system: communicated through: database links and flat file exchanges — no API capability. (5) Arabic data integrity: 20 years of Arabic data stored in: various character encodings — some records in: Windows-1256, others in: UTF-8, some in: ISO-8859-6; Arabic names in the database had: inconsistent encoding creating: duplicate records and: search failures for Arabic text.
We executed a 14-month modernization program: (1) Assessment (months 1-2): full code analysis of 3.2M LOC — identifying: 1.8M lines of active code (800K LOC was dead code that had been accumulated through 20 years of patches and modifications never cleaned up; 600K LOC was test/debug code left in production). Business rule extraction: 2,847 business rules identified and documented — every calculation, validation, workflow decision, and: fee determination logic extracted from PL/SQL packages and Oracle Forms triggers. Saudi-specific rules cataloged: 340 rules specific to Saudi commercial law, 85 rules for Zakat calculation, 120 rules for government fee schedules, and: 45 rules for inter-entity coordination. (2) Technology selection (month 2): the modernized system built on: Next.js frontend (Arabic-first web application with: responsive design for mobile and desktop), Node.js microservices backend (business logic decomposed into: 12 microservices — application processing, fee calculation, document verification, payment, notification, reporting, and: 6 supporting services), PostgreSQL database (migrating from Oracle 9i — eliminating: Oracle licensing costs of approximately SAR 2.4M annually), and deployment on: Saudi cloud infrastructure (local cloud provider compliant with: NCA requirements and data sovereignty regulations). (3) Business rule implementation (months 3-6): every extracted business rule implemented in the new system with: automated verification. We developed: a rule comparison framework that processed: 10,000 test cases (real historical applications, anonymized) through both: the legacy system and the new system — comparing: outcomes for every decision point, fee calculation, and: workflow routing. Initial comparison: 97.2% match. The 2.8% discrepancies: investigated one by one — 1.8% were legacy bugs that had never been caught (incorrect fee calculations for: edge-case business types), 0.7% were rules that had been superseded by: newer regulations but: the legacy code had not been updated (the PL/SQL still calculated: fees based on a 2018 schedule while clerks manually adjusted), and 0.3% were: new system implementation errors that we corrected. After corrections: 100% match on all valid test cases. (4) Arabic data migration (months 4-7): the most complex migration element. 12 million records spanning 20 years — each record containing: Arabic business names, owner names, addresses, and: activity descriptions in: mixed character encodings. Migration process: encoding detection (automated algorithm detecting: the encoding of each text field in each record — analyzing: byte patterns to determine: Windows-1256, UTF-8, or ISO-8859-6), unified conversion (all Arabic text converted to: UTF-8 with: validation against known Arabic character ranges; visually ambiguous characters resolved through: manual review of 4,500 records where: automated conversion produced: uncertain results), deduplication (Arabic name normalization — removing: encoding-caused duplicates where: the same business appeared: 2-3 times in the database with: identical Arabic names stored in: different encodings; 18,000 duplicate records identified and merged: preserving the most complete record in each case), and historical integrity (every migrated record: maintaining: its original creation date, modification history, and: processing trail; the migration audit log: documenting: every transformation applied to every record — creating: a forensic trail should any data integrity question arise). (5) National platform integration (months 5-8): modern API integrations replacing: legacy flat file exchanges: Absher integration (real-time citizen identity verification during: application submission — eliminating: the overnight batch verification that added: 24 hours to processing time), Yakeen integration (applicant information validation — pre-populating: application forms with verified data, reducing: data entry errors from: 12% to 0.3%), SADAD integration (fee payment through: the national payment system — instant payment confirmation vs. previous: 3-5 day bank transfer verification), and Etimad integration (procurement-related licensing connected to: the government procurement platform). (6) Parallel operation (months 9-12): both systems running simultaneously — every application processed by: both legacy and modern systems. The parallel operation validated: processing accuracy (zero discrepancies on: 112,000 applications processed during parallel run), performance (modern system processing: applications in real-time — average 4 seconds from submission to decision for straightforward renewals vs. 24 hours in the legacy batch system), and reliability (modern system: 99.95% uptime during parallel run — exceeding: the legacy system's 99.2% availability). (7) Cutover and legacy decommission (months 12-14): phased cutover — renewals first (highest volume, simplest processing), then amendments, then new applications. Each phase: validated for 2 weeks before: the next phase activated. Legacy system: maintained in read-only mode for 6 months post-cutover for: historical record access. Solaris servers: decommissioned after: confirming all historical data accessible in the new system.
Processing time: application processing reduced from 24 hours (overnight batch) to 4 seconds (real-time) for standard renewals. Complex applications (new registrations requiring: multiple verifications): reduced from 5-7 business days to same-day. The entity met: the Vision 2030 digital service mandate — real-time licensing through the national portal. Cost elimination: Oracle license savings: SAR 2.4M/year. Solaris hardware maintenance: SAR 400K/year eliminated. Total annual cost reduction: SAR 2.8M/year — the modernization paying for itself within 3 years. Data quality: 18,000 duplicate records eliminated through Arabic text normalization. Data entry errors: reduced from 12% to 0.3% through Yakeen pre-population. Arabic text search: now functioning correctly across: all 12 million historical records — previously: Arabic search returned incomplete results due to: encoding inconsistencies. Citizen satisfaction: citizen survey satisfaction: increased from 2.8/5 to 4.4/5. The primary driver: elimination of the 24-hour processing delay and: the ability to track application status in real-time through the national portal. Knowledge risk elimination: the dependency on 4 aging Oracle Forms developers: eliminated. The modernized system maintained by: 6 engineers with: modern technology skills (Node.js, React, PostgreSQL) — skills available in: Saudi Arabia's growing technology workforce. The entity could: recruit and train replacement engineers without: the specialized legacy knowledge requirement. Development cost: SAR 4,200,000 (14-month program). Annual savings: SAR 2,800,000 (Oracle licensing + hardware). Break-even: 18 months. 5-year ROI: the SAR 14M in savings over 5 years minus SAR 4.2M development cost yields: SAR 9.8M net benefit — plus: immeasurable value from citizen service improvement and: elimination of operational risk from aging infrastructure.
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.
Riyadh legacy modernization options include: global SIs (Accenture, IBM, TCS, Wipro — SAR 5,000,000-30,000,000, enterprise-grade but expensive and: often lengthy engagements), Big Four technology practices (Deloitte, EY, PwC, KPMG — SAR 3,000,000-15,000,000, strong advisory but often subcontracting development), regional SIs (Elm, SITE, Solutions by STC — SAR 2,000,000-10,000,000, strong Saudi market knowledge), and niche modernization firms (specialized COBOL/Oracle modernization — SAR 1,000,000-5,000,000, focused expertise but: limited local presence). ZTABS delivers Saudi-specific legacy modernization with Arabic data migration expertise, national platform integration, and practical business rule extraction at mid-market pricing.
Legacy app modernization in Riyadh ranges from SAR 500,000 for focused module modernization to SAR 10,000,000+ for enterprise-wide legacy transformation. Government licensing system (as in the case study): SAR 4,200,000. Oracle Forms to web application: SAR 500,000-2,000,000. COBOL mainframe migration: SAR 1,500,000-6,000,000. ERP modernization (on-prem to cloud): SAR 1,000,000-4,000,000. Legacy assessment and modernization roadmap: SAR 80,000-150,000.
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. 17 products in production.
Common questions about legacy app modernization for Riyadh businesses
Depends on system complexity and scope. Single Oracle Forms application (50-100 forms): 4-6 months. Enterprise legacy system (1,000+ forms/programs): 12-18 months. COBOL mainframe with complex business logic: 12-24 months. We always recommend: phased modernization with value delivered at each phase — not a multi-year big-bang approach. The phased approach: reduces risk, delivers early value, and: allows course corrections based on lessons from each phase.
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 Riyadh, Saudi ArabiaZTABS is a remote-first web development agency serving Riyadh businesses — including full-stack development, progressive web apps, api development. We work with GovTech, FinTech, Energy Tech companies in Riyadh, Saudi Arabia 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 Riyadh, Saudi ArabiaZTABS is a remote-first web design agency serving Riyadh businesses — including ui/ux design, responsive design, custom interfaces. We work with GovTech, FinTech, Energy Tech companies in Riyadh, Saudi Arabia 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 Riyadh, Saudi ArabiaZTABS is a remote-first AI development agency serving Riyadh businesses — including llm integration & fine-tuning, ai agents & automation, rag & knowledge systems. We work with GovTech, FinTech, Energy Tech companies in Riyadh, Saudi Arabia 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 Riyadh. Get a free consultation today.
