ZTABS modernizes legacy applications for Doha organizations — migrating VB6, .NET Framework, Oracle Forms, and custom desktop systems to modern web and cloud-native platforms while preserving Arabic workflows and Qatari business logic.
Doha's organizations run critical business operations on legacy applications that are becoming increasingly difficult and risky to maintain. These are not theoretical concerns — they are systems processing real transactions today: a government authority running its core licensing system on Oracle Forms 6i (released in 1998), a bank operating an Islamic finance calculation engine built in Visual Basic 6 (VB6, released in 1998, runtime support ended 2008), a construction company managing QAR 2B+ in project contracts on a Delphi desktop application that only runs on Windows XP, and an energy company operating asset management on a custom C++ system that only three engineers in the world understand. These legacy systems share common characteristics: they work (the business logic is proven over decades of operation — these systems process millions of transactions correctly), they are fragile (any change risks breaking functionality that nobody fully understands — documentation is nonexistent or outdated, original developers have retired or left), they are expensive to maintain (finding VB6 or Oracle Forms developers in 2026 requires premium rates — and each year, fewer developers have these skills), they are security risks (running on unsupported operating systems and frameworks — Windows Server 2003, .NET Framework 2.0, Java 6 — with known vulnerabilities that cannot be patched because patches are no longer released), they cannot integrate (modern APIs, mobile access, cloud services — legacy systems were designed for a world without these requirements, and adding integration is difficult without modern API frameworks), and they are Arabic-limited (legacy systems often have basic Arabic support — hardcoded Arabic text, limited RTL layout, no Arabic search — not the quality Arabic experience that Qatari users now expect from modern applications). Legacy app modernization in Doha means replacing these aging systems with modern equivalents — while preserving the business logic that has been refined over decades of actual use. This is the challenge: the new system must do everything the old system does (including edge cases that nobody documented but everybody relies on), while adding modern capabilities (web access, mobile access, API integration, proper Arabic support, cloud deployment). Getting this wrong means either: building a new system that doesn't replicate critical business logic (causing operational failures), or a modernization project that never completes (the "perpetual migration" that consumes budget without delivering value).
Doha's legacy modernization demand comes from organizations where aging systems are creating operational, security, or compliance risks. Government: Qatari government entities operating legacy systems built during the rapid government digitization of the 2000s and early 2010s. Common legacy platforms: Oracle Forms (the dominant government application platform in the GCC during that era — many authorities running Forms 6i or Forms 10g applications for citizen service processing, licensing, permits, and regulatory functions), custom .NET Framework applications (desktop applications built on .NET Framework 2.0-4.0, deployed on government workstations, with SQL Server backends), and lotus Notes/Domino (email and workflow applications — some authorities still running critical workflow on Notes databases). Modernization drivers: the systems cannot support Qatar's e-Government mandate (Hukoomi integration requiring web APIs that legacy systems cannot provide), they cannot be accessed on modern devices (tablets, phones — critical for field inspectors, auditors, and officials working remotely), and they run on infrastructure that is reaching end-of-life (Oracle Forms requires WebLogic Server, which requires specific Java versions, which require specific OS versions — each component constraining the others). Banking: Qatar's banks operating legacy systems for: Islamic finance product engines (custom systems calculating profit distributions, managing Murabaha contracts, processing Ijara leases — built on VB6, PowerBuilder, or early .NET — containing decades of refined Islamic finance calculation logic that is correct but undocumented), core banking extensions (modifications to core banking platforms — Temenos T24, Infosys Finacle — that were made decades ago by implementation partners that no longer exist, using undocumented customization points), and regulatory reporting (custom reporting applications extracting data from core banking systems, transforming per QCB requirements, and generating regulatory submissions — built on technologies that nobody currently employed understands). Energy: QatarEnergy and operating companies running: asset management systems (custom C/C++ applications managing physical assets — pipelines, processing equipment, storage tanks — with inspection schedules, maintenance records, and lifecycle data spanning decades), HSE systems (health, safety, and environment applications built on Access databases or early web technologies — containing incident records, permit-to-work data, and safety compliance records), and production monitoring dashboards (custom applications displaying SCADA data — built on technologies like Wonderware or custom Visual Basic applications interfacing directly with OPC servers). Construction: Qatar's construction sector running: project management systems (custom Delphi or VB6 applications managing construction projects — contracts, milestones, variations, payments — with Arabic document generation and QAR calculations), contract management (desktop applications containing years of contract data — variation orders, claims, payment certificates — critical for dispute resolution and audit), and estimating systems (custom cost estimation tools built on Excel VBA or Access — containing pricing databases and estimation methodologies refined over decades of Qatari construction experience).
Our Doha legacy modernization follows a structured methodology that prioritizes business continuity and knowledge preservation. Discovery and assessment (weeks 1-4): understanding the legacy system before attempting to replace it. Code archaeology: we reverse-engineer the legacy application — reading source code (VB6, Oracle Forms PL/SQL, Delphi, C++), running the application, and documenting every function, business rule, and edge case. This is painstaking work — legacy code often contains: undocumented business rules embedded in code (an IF statement that applies a 2.5% surcharge for specific transaction types — nobody remembers why, but removing it would cause incorrect calculations), workarounds for historical issues (code that reformats data because an upstream system sent it incorrectly 15 years ago — the upstream system has since been fixed, but the workaround remains), and Arabic text handling (hardcoded Arabic strings, character encoding workarounds for older systems that didn't support Unicode — these workarounds must be understood to ensure the modern system handles the same Arabic text correctly). Database analysis: the legacy database contains decades of accumulated data — and the data model contains accumulated complexity. We document: table relationships (often implicit — no foreign keys, just matching column names), data quality issues (inconsistent formats, orphaned records, duplicate entries — these must be addressed during migration), and historical data requirements (how much history must the new system contain — 5 years? 10 years? Everything?). User workflow documentation: observing actual users operating the legacy system — understanding not just what the system does, but how people use it. This reveals: workarounds (users copying data from the system into Excel for calculations the system can't perform), undocumented processes (steps that users perform that aren't in any procedure manual — "I always check this field because sometimes the system puts the wrong value"), and performance expectations (how long operations take in the legacy system — the new system must be at least as fast, or users will resist adoption). Modernization strategy (week 3-4): selecting the right approach for each component. Rewrite (build new): for systems where the legacy technology is completely obsolete (VB6, Oracle Forms 6i, Delphi) and the business logic is well-understood. Advantages: modern architecture, modern UI, modern integration capability. Risk: missing business rules during rewrite. Mitigation: extensive discovery, parallel running. Strangler fig pattern: for large, complex systems that can be decomposed — building new microservices around the legacy system, gradually routing functionality to the new services while the legacy system continues operating. Advantages: incremental migration (each step is small and reversible), no big-bang switchover. Best for: core banking systems, large government platforms. Replatform: for systems where the business logic is sound but the runtime is obsolete — migrating .NET Framework to .NET 8, or Java 6 to Java 21, preserving most of the code while updating the platform. Advantages: lower risk than rewrite, preserves proven business logic. Best for: systems with well-structured code that primarily need platform modernization. Encapsulate and extend: for systems where the legacy system must continue operating but modern capabilities (APIs, mobile access) are needed — wrapping the legacy system with modern APIs, adding new functionality in modern services while the legacy system handles core processing. Advantages: fastest path to modern capabilities, no business logic risk. Best for: systems where modernization budget is limited or timeline is urgent. Development (weeks 4-16): building the modern replacement. Technology stack (for rewrite): Next.js (Arabic-first web interface with RTL layout, Arabic search, Hijri date support), Node.js or .NET 8 (API layer — depending on the team's existing skills), PostgreSQL (database — with Arabic full-text search, proper Unicode support), and Redis (caching — critical for performance parity with desktop legacy applications, which feel fast because they run locally). Arabic-first design: every screen designed in Arabic first — not an English interface translated to Arabic. Arabic typography optimized for screen readability, Arabic search with morphological awareness, Arabic document generation (replacing legacy Arabic document generation that often used workarounds like RTF templates with hardcoded Arabic text). Business logic implementation: each business rule from the discovery phase implemented and tested individually — with test cases comparing the modern system's output to the legacy system's output for the same inputs. This "oracle testing" approach: using the legacy system as the reference for correctness. Data migration (weeks 12-18): migrating decades of accumulated data. Data cleaning: addressing data quality issues identified during discovery — deduplication, format standardization, orphan record resolution, and encoding conversion (legacy systems often storing Arabic text in Windows-1256 encoding — migrating to UTF-8). Migration scripts: automated, repeatable migration scripts (not manual data manipulation) — tested on copies of production data, refined, and re-tested until migration produces correct results. Migration validation: automated validation comparing source and target data — every record verified, every calculation cross-checked, every relationship confirmed. Parallel running (weeks 16-20): operating both systems simultaneously. Users: entering data into both systems (or the new system replicating transactions to the legacy system automatically). Output comparison: reports from both systems compared — any discrepancies investigated and resolved. The parallel run: providing confidence that the new system produces identical results to the legacy system — and identifying any missed business rules before the legacy system is decommissioned.
Government / Regulatory
A Qatari regulatory authority (responsible for licensing and compliance oversight of 3,000+ regulated entities) operated its core licensing system on Oracle Forms 10g (released 2006), running on Oracle Database 11g, WebLogic Server 10, and Red Hat Enterprise Linux 5. The problems: (1) Technology obsolescence: Oracle Forms 10g: desupported by Oracle in 2016. WebLogic Server 10: desupported in 2017. Oracle Database 11g: desupported in 2020 (extended support ended). RHEL 5: desupported in 2017. Every component of the technology stack: running without vendor support. Security patches: unavailable for any component. The authority's IT team: managing known vulnerabilities with workarounds (network isolation, additional firewall rules, restricted access) — but these workarounds: limiting the system's accessibility and usability. (2) Arabic limitations: the Oracle Forms application was built with basic Arabic support — Arabic labels and field values displayed in RTL, but: form layout was LTR (fields positioned left-to-right, then Arabic text rendered right-to-left within each field — creating a visually inconsistent experience), Arabic search: exact-match only (searching for "شركة" would not find "الشركة" or "شركات" — users had to know the exact stored value), Arabic printing: reports generated using Oracle Reports with Arabic text rendering issues (line breaks in the wrong positions, diacritical marks misaligned) — the authority printing bilingual certificates and licenses that looked unprofessional, and date handling: Gregorian only (no Hijri dates, despite the authority using Hijri dates in official correspondence). (3) No web or mobile access: the Oracle Forms application required: a Java applet plugin (no longer supported by modern browsers), VPN access to the authority's internal network, and a specific Java version (JRE 1.6 — which itself has critical security vulnerabilities). Inspectors: unable to access the system during field inspections. They carried printed checklists, made handwritten notes, and manually entered data back into the system at the office — typically 1-2 days after the inspection. Regulated entities: unable to submit applications or check status online — all interactions required physical visits to the authority's offices or postal mail. (4) Integration impossible: e-Government mandate: the authority needed to integrate with Qatar's Hukoomi government portal — enabling citizens and businesses to access licensing services through the unified government platform. The Oracle Forms application: having no API layer. Data was accessible only through the Oracle database (direct database queries) or through the Forms user interface. Building a modern API on top of the legacy database: technically possible but architecturally unsound (changes to the Forms application could break the API, and vice versa). (5) Knowledge concentration: the Oracle Forms application was built by a consulting firm that exited Qatar in 2014. The application: maintained by a single Oracle Forms developer (a contractor) who had been with the authority for 8 years. This developer: the only person who understood the application's 450 Forms, 280 Reports, and 120 PL/SQL packages. When this developer took leave: no changes could be made to the system. The authority had attempted to hire additional Oracle Forms developers: zero qualified applicants in Qatar over 2 years of searching.
We modernized the licensing system over 20 weeks: (1) Discovery (weeks 1-4): we conducted comprehensive discovery of the Oracle Forms application working alongside the sole Oracle Forms developer. Code inventory: 450 Forms (user interface screens), 280 Reports (printable outputs — licenses, certificates, compliance reports), and 120 PL/SQL packages (business logic — validation rules, calculation engines, workflow routing). Business rules documented: 840 distinct business rules extracted from PL/SQL code and Forms triggers — each rule documented with: description (what it does), condition (when it applies), examples (input → output), and regulatory basis (which regulation or decree mandates this rule). Critical findings: 47 business rules existed only in code — not in any regulation, policy, or procedure document. These "institutional knowledge" rules were validated with the authority's operations team — 38 were confirmed as necessary (evolved operational practices), 9 were confirmed as obsolete (relating to regulations that had been superseded). The 9 obsolete rules: removed from scope. Data analysis: 12 years of accumulated data — 3.2 million licensing records, 28 million transaction records, and 4.5 million document records. Data quality issues identified: 12,000 duplicate entity records (the same regulated company registered multiple times with slightly different names), 45,000 records with encoding issues (Arabic text stored incorrectly — mojibake characters from incorrect encoding conversion at some point in the system's history), and 8,000 orphaned transaction records (transactions referencing entities or licenses that no longer exist in the database — likely from a partial data cleanup years ago). (2) Modern platform (weeks 3-16): built on Next.js (Arabic-first web interface) + Node.js (API layer) + PostgreSQL (database with Arabic full-text search). Arabic-first interface: every screen designed in Arabic as the primary language — RTL layout designed from the ground up (not mirrored LTR), Arabic typography using Noto Naskh Arabic (optimized for screen readability), and bilingual capability (English as secondary language — switchable by user preference). Arabic search: PostgreSQL with Arabic stemming and fuzzy matching — searching for "شركة" finds "الشركة", "شركات", "الشركات", and even approximate matches with minor spelling variations. Hijri date support: all date fields supporting both Hijri and Gregorian display — with automatic conversion. Official documents and reports: generated with Hijri dates. Licensing workflows: all 15 license types implemented with their specific workflows — application submission (online by regulated entities — with Arabic form validation, document upload, and fee calculation), department review (parallel or sequential review depending on license type — with configurable review checklists and approval delegation), approval (digital approval with configurable approval chains — department head → director → executive director), license generation (bilingual Arabic/English license certificates — generated as PDF with professional Arabic typography, QR code for verification, and digital signature), and renewal and amendment workflows (existing licenses: renewed or amended through similar workflows). Inspection module: mobile-responsive web application for field inspectors — accessing entity information, previous inspection results, and compliance history on a tablet. Inspection findings: entered digitally during the inspection (with Arabic text input, photo attachment, and GPS location), submitted immediately — eliminating the 1-2 day data entry delay. Portal for regulated entities: self-service portal where regulated entities can: submit license applications (with document upload and online payment via QPay), track application status (real-time visibility into processing stages), receive notifications (email and SMS in Arabic — application received, additional documents needed, application approved/rejected), renew licenses online, and download license certificates. Hukoomi integration: REST API enabling the authority's services to be accessed through Qatar's unified government portal. (3) Data migration (weeks 14-18): automated migration scripts converting Oracle Database data to PostgreSQL. Arabic text encoding: all 45,000 records with encoding issues corrected during migration (automated detection and repair of mojibake characters). Duplicate entities: merged (12,000 duplicates consolidated into 6,400 unique entities — merge logic preserving the most complete data from each duplicate pair and creating audit records documenting the merge). Data validation: automated comparison of migrated data against source — every record verified, every financial calculation confirmed, every relationship checked. (4) Parallel running (weeks 18-20): both systems running simultaneously for 3 weeks. All new applications: processed in the new system. Existing in-progress applications: completed in the legacy system (to avoid mid-process migration). Reporting comparison: monthly reports generated from both systems and compared — all figures matching within rounding tolerance.
Processing time: average license application processing time from 14 business days (Oracle Forms — manual workflow routing, paper-based approvals) to 5 business days (new system — digital workflow with automated routing and parallel review). The improvement: driven by automated routing (applications instantly reaching the correct department vs. physically routed), parallel review (multiple departments reviewing simultaneously vs. sequential paper circulation), and digital approvals (approvers acting from any device vs. needing to be at their desk with VPN). Regulated entity experience: from physical office visits to online self-service — application submission, status tracking, document upload, and license download all available online. Physical visits to the authority's offices: decreased 70% in the first quarter. Regulated entity satisfaction survey: 4.2/5 (vs. no previous measurement — but qualitative feedback indicating significant improvement). Inspection efficiency: inspector productivity increased 35% — eliminating the 1-2 day data entry delay, providing real-time access to compliance history during inspections, and enabling digital photo documentation (vs. handwritten notes transcribed later). Arabic quality: the authority's communications director (responsible for official documents): "The Arabic on these certificates is beautiful. For the first time, our official documents look as professional in Arabic as they do in English." The Arabic search: inspectors and licensing officers specifically citing Arabic search as a major improvement — "I can find any company in seconds now, even if I don't remember the exact registered name." Knowledge risk: dependency on a single Oracle Forms developer eliminated. The new system: understood by the authority's 4-person IT team and ZTABS — maintainable with standard web development skills (JavaScript, TypeScript, SQL) rather than requiring Oracle Forms specialists. The Oracle Forms developer: transitioned to a business analyst role (his deep knowledge of the authority's licensing processes making him valuable in a new capacity). Security: from a completely unsupported technology stack (every component end-of-life) to a current, supported stack — Next.js, Node.js, and PostgreSQL all actively maintained with regular security patches. The network isolation workarounds: eliminated. The system: accessible securely via the internet with proper authentication and authorization. Hukoomi integration: the authority's services available on Qatar's unified government portal within 1 month of go-live — meeting the e-Government mandate. Development cost: QAR 780,000 (20-week modernization including discovery, development, data migration, and parallel running). Annual savings: QAR 220,000 (Oracle license costs eliminated — Forms, Reports, WebLogic, Database), QAR 95,000 (Oracle Forms developer contractor premium — now replaced by standard web developers), QAR 180,000 (operational efficiency — reduced processing time, eliminated data entry, reduced physical visits). Total annual savings: QAR 495,000. ROI: development cost recovered within 19 months from operational and licensing savings.
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.
Doha's legacy modernization market includes global system integrators (Accenture, Deloitte, IBM — all with Doha presence, QAR 400-700/hr), Oracle and Microsoft partners (focused on migrating within their vendor ecosystem — Oracle Forms to APEX, .NET Framework to .NET 8), regional IT companies (GCC-based — varying modernization capability), and the "do nothing" option (continuing to operate legacy systems with increasing risk and cost). Global SIs deliver comprehensive modernization but at premium pricing with long timelines (12-18 month programs for what could be done in 5-6 months). Vendor partners push their vendor's platform regardless of fit. Regional companies may lack the deep legacy code analysis capability needed for complex modernization. ZTABS provides end-to-end legacy modernization — discovery, rewrite, data migration, and parallel running — with Arabic-first design and deep understanding of Qatari business processes.
Legacy app modernization in Doha ranges from QAR 200,000 for small applications (single-purpose desktop application with <50 screens) to QAR 2,000,000+ for large enterprise systems (core business platforms with hundreds of screens, complex business logic, and decades of data). Global SIs in Doha: QAR 400-700/hr. ZTABS delivers at competitive rates — our modernization methodology providing predictable timelines and budgets based on thorough discovery.
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 Doha businesses
Three layers of protection: (1) Discovery — we reverse-engineer the legacy code, documenting every business rule with examples and regulatory basis. (2) Oracle testing — during development, we compare the new system's outputs to the legacy system's outputs for the same inputs, identifying any discrepancy. (3) Parallel running — both systems operate simultaneously before switchover, with automated report comparison verifying identical results. This three-layer approach catches business logic gaps at each stage.
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 Doha, QatarZTABS is a remote-first web development agency serving Doha businesses — including full-stack development, progressive web apps, api development. We work with Smart City & GovTech, FinTech, Energy Tech companies in Doha, Qatar 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 Doha, QatarZTABS is a remote-first web design agency serving Doha businesses — including ui/ux design, responsive design, custom interfaces. We work with Smart City & GovTech, FinTech, Energy Tech companies in Doha, Qatar 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 Doha, QatarZTABS is a remote-first AI development agency serving Doha businesses — including llm integration & fine-tuning, ai agents & automation, rag & knowledge systems. We work with Smart City & GovTech, FinTech, Energy Tech companies in Doha, Qatar 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 Doha. Get a free consultation today.
