ZTABS modernizes legacy applications for Doha organisations in government, banking, energy and construction. Doha organisations operate critical systems on Oracle Forms, VB6, .NET Framework and custom platforms that are becoming increasingly difficult to maintain. Oracle Forms developers are scarce. VB6 IDE support ended in 2008, though the core runtime remains supported on current Windows versions under Microsoft lifecycle policy; third-party OCX components require separate assessment. Systems may run on older operating systems requiring lifecycle review. ZTABS is remote-first by design from our Houston, Texas office.
Doha legacy modernization demand spans government licensing and regulatory systems, banking Islamic finance calculation engines, energy asset management and HSE platforms, and construction project management systems.
Legacy app modernization in Doha at a glance
| Need | What we build | Key requirement |
|---|
| Government | Licensing and regulatory systems | Hukoomi, Arabic-first |
| Banking | Islamic finance engines | QCB, QFC, Sharia logic |
| Energy | Asset management and HSE | Safety-critical, SCADA |
| Construction | Project and contract management | Arabic documents, QAR |
| Enterprise | Desktop to web migration | Mobile access, cloud |
Government legacy modernization
Qatari government entities operate legacy systems built during the rapid government digitization of the 2000s and early 2010s. Oracle Forms was the dominant government application platform in the GCC during that era.
Oracle Forms migration. Authorities run Forms 6i or Forms 10g applications for citizen service processing, licensing, permits and regulatory functions. Per Oracle's Lifetime Support Policy, Application Server 10g R2 (which includes Forms, Reports and Developer Suite) ended Premier Support in December 2011 with Extended Support not available and Sustaining Support indefinite but without new security patches. Forms and Reports 11g R2 ended Premier Support in December 2016 and Extended Support in December 2018. WebLogic Server 10.3.0 ended Premier in January 2014 and Extended in January 2017; 10.3.1 and later ended Premier in December 2018 and Extended in December 2021. Sustaining Support is indefinite but provides no new security patches. The exact deployed release, active support contract and security patch status are assessed per system, along with licences, interfaces and upgrade alternatives including APEX, before selecting the modernization approach.
Hukoomi integration. Qatar's e-Government programme encourages legacy systems to expose services through modern APIs. Legacy Oracle Forms applications with limited or no API layer benefit from modernization enabling Hukoomi integration through REST APIs.
Arabic-first design. Screens for agreed Arabic audiences designed in Arabic as the primary language. RTL layout designed from the ground up, not mirrored LTR. Arabic typography optimized for screen readability. Arabic search with morphological awareness evaluated for agreed workflows and term coverage. Hijri and Gregorian date support with conversion for agreed calendar conventions. Bilingual Arabic and English capability with user preference switching.
Modernizing your Doha government or banking system?
Tell us about your legacy platform, Arabic requirements and Hukoomi integration needs. We start with assessment covering business rule extraction, data analysis and modernization strategy.
Banking legacy modernization
Qatar's banks operate legacy systems for Islamic finance calculations, core banking extensions and regulatory reporting.
Islamic finance engines. Custom systems calculating profit distributions, managing Murabaha contracts and processing Ijara leases built on VB6, PowerBuilder or early .NET. Islamic finance calculation logic refined over years but often undocumented. Each calculation rule extracted, documented, tested with agreed fixtures and tolerances, and reimplemented in modern code with domain-owner approval of results.
Core banking extensions. Modifications to core banking platforms including Temenos T24 and Infosys Finacle made decades ago by implementation partners that no longer exist. Undocumented customization points requiring careful analysis.
Regulatory reporting. Custom reporting applications extracting data from core banking systems, transforming per QCB requirements. Built on technologies that current staff do not understand.
Energy legacy modernization
QatarEnergy and operating companies operate legacy asset management, HSE and production monitoring systems.
Asset management. Custom C or C++ applications managing physical assets including pipelines, processing equipment and 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.
Production monitoring. Custom applications displaying SCADA data built on technologies like Wonderware or custom Visual Basic applications interfacing with OPC servers.
Construction legacy modernization
Qatar's construction sector operates legacy project management, contract management and estimating systems.
Project management. Custom Delphi or VB6 applications managing construction projects with contracts, milestones, variations, payments and Arabic document generation.
Contract management. Desktop applications containing years of contract data critical for dispute resolution and audit. Variation orders, claims and payment certificates.
Qatari regulation
Law 13/2016. Qatar's national data protection law applies based on the entity, data type, processing purpose and applicable exceptions.
QFC. The QFC Data Protection Regulations have separate Article 7 territorial scope covering entities incorporated, registered or with ongoing arrangements through QFC to the relevant extent. Not all Qatar operations fall under QFC jurisdiction.
NAPS. The National ATM and POS Switch handles electronic payment switching.
NPC. The National Planning Council has a statistics function and is not a payment body.
NISCF. The National Information Security Compliance Framework covers organisation-level ISMS scope.
WPS. The Ministry of Labour Wage Protection System covers employment and entity roles. Pension and end-of-service calculations depend on the employee's actual regime, basic or last wage and contract terms.
Cloud providers. Google Cloud Doha region and Azure Qatar offerings assessed per actual product availability, rights and full-stack requirements.
Arabic and English. Agreed audience for each system and document type. Working languages, translated materials and terminology are agreed per engagement.
Qatar VAT. Qatar has not implemented VAT. If VAT readiness is relevant, the current status should be verified via the General Tax Authority before scoping.
Strangler fig for Doha systems
Seam selection. Government seams: licensing, permits, regulatory processing, citizen portal. Banking seams: Islamic finance calculations, core banking, regulatory reporting. Energy seams: asset management, HSE, production monitoring. Construction seams: project management, contract management, estimating.
Single authoritative write. One system authoritative for each transaction type during coexistence. Banking dual-write dangerous for Islamic finance calculations and QCB reporting. Government dual-write dangerous for licensing records. CDC with versioning and conflict detection.
Reconciliation. Idempotency keys enforced by receiving side. Finite retries with DLQ. Unknown outcomes require reconciliation before replay, especially for Islamic finance calculations, government licensing decisions and QCB regulatory submissions.
Data migration methodology
Oracle database migration. Legacy Oracle schemas with denormalized tables and cryptic column names mapped to modern PostgreSQL schemas. Arabic text stored in Windows-1256 encoding migrated to UTF-8. Data quality issues from decades of accumulation addressed during migration.
Arabic text handling. Legacy systems often store Arabic text with encoding workarounds. Character encoding conversion from Windows-1256 to UTF-8. Mojibake character detection and automated repair. Arabic search morphological indexing built during migration.
Data type mapping. Types, nulls, time zones, currency, rounding, identifiers, encoding, history and crosswalks reconciled. Qatar-specific: QAR currency precision, QID handling per data protection requirements, Hijri date conversion, Arabic text encoding.
Cutover rehearsal. Observable acceptance with measurable RTO, RPO and latency targets. Government cutover planned for lower-volume periods. Banking cutover timed for settlement cycles.
Inventory and discovery
Doha enterprise modernization begins with complete inventory: applications, users, scheduled jobs, database procedures, reports, file and API dependencies, vendor contracts, supported versus end-of-life versions.
Code archaeology reverse-engineers legacy applications reading source code in VB6, Oracle Forms PL/SQL, Delphi and C++. Agreed covered business rules, processing paths and integration dependencies documented with gaps and unknowns recorded for domain-owner review. Undocumented rules embedded in code and workarounds for historical issues identified to the extent feasible within the agreed discovery scope; completeness of edge-case coverage is not guaranteed and domain-owner approval of documented coverage is required before implementation proceeds.
Illustrative Example
Hypothetical: Qatari regulatory authority modernizing Oracle Forms 10g licensing system
A Qatari regulatory authority operates its core licensing system on Oracle Forms 10g with Oracle Database 11g. Forms 10g ended Premier Support in December 2011 and is in Sustaining Support without new security patches; the database version's support stage depends on the exact release and active contract. The system processes licensing for thousands of regulated entities but cannot be accessed on modern devices and is not integrated with Hukoomi. A single Oracle Forms developer contractor is the only person who understands the codebase.
Strangler fig modernization would create a modern citizen portal with Arabic-first design and Hukoomi integration first while legacy Forms continues processing. Business rules extracted from PL/SQL and Forms triggers. Integration hub replacing SOAP web services with REST APIs. Decision engine migrating regulatory logic to a declarative rule engine testable by policy staff.
Assumptions: Oracle Forms code accessible for analysis, regulatory staff available for rule validation, Hukoomi integration specifications current, and parallel processing feasible. Residual risks include undiscovered business rules in PL/SQL, Arabic text encoding inconsistencies, developer knowledge concentration and regulatory amendment pace. No guarantee of specific processing time, cost reduction or citizen satisfaction improvement.
This is a hypothetical scenario for illustration. Actual scope, timeline and cost depend on your requirements.
Integration and dependency management
Government integrations. Hukoomi e-Government portal, QPay payment gateway, MOI identity verification, inter-agency data exchange and document management systems.
Banking integrations. QCB regulatory reporting, SWIFT payment networks, NAPS ATM and POS switch connections and correspondent bank integrations.
Energy integrations. SCADA systems, safety incident reporting, environmental monitoring, production accounting and asset lifecycle management systems.
Assessment methodology
Application archaeology for Doha systems covers Oracle Forms and PL/SQL analysis for business rule extraction, VB6 and Delphi code analysis for application logic, database schema analysis for data model understanding and integration cataloguing for system dependency mapping.
Modernization approach selection
Doha enterprises need clear criteria for choosing between approaches.
Rewrite. Build new system from scratch. Recommended when legacy technology is completely obsolete and business logic is well understood. Most Oracle Forms and VB6 systems fall here.
Strangler fig. Build modern services around legacy system. Best for large complex systems. Incremental migration with each step small and reversible.
Replatform. Migrate to a supported target framework selected after lifecycle review, preserving most code. Lower risk. Best for systems with well-structured code.
Encapsulate and extend. Wrap legacy with modern APIs while legacy continues operating. Fastest path to modern capabilities.
Regression and testing
Representative business-critical paths: government licensing lifecycle with Hukoomi integration, Islamic finance calculation with QCB reporting, energy asset management with safety compliance. Meaningful integration, performance and manual UAT with domain expert approval.
Cost and timeline
Legacy system modernization follows the published cost guide.
| Tier | Range | Timeline | Example |
|---|
| UI Modernization | $40K to $100K | 8 to 16 weeks | New frontend, API wrapper, improved UX |
| Re-Platforming | $100K to $250K | 16 to 32 weeks | Modern stack, containerization, cloud, data migration |
| Re-Architecture | $250K to $400K | 8 to 14 months | Decompose monolith, event-driven, modern data layer |
| Full Rebuild | $400K to $500K+ | 12 to 18+ months | Ground-up rebuild, agreed availability and cutover rehearsal |
Vendor comparison
Ranges reflect re-platforming a 10 to 15 year old business-critical system using a strangler fig approach, modern stack, API wrappers, phased data migration and regression harness.
| Vendor type | Typical cost | Timeline |
|---|
| Freelance or dev collective | $40K to $130K | 5 to 12 months |
| Offshore systems integrator | $60K to $200K | 8 to 14 months |
| Boutique modernization specialist (ZTABS tier) | $100K to $280K | 6 to 12 months |
| Big 4 consultancy | $300K to $1M+ | 10 to 18 months |
| SaaS replacement vendor | $50K to $200K implementation | 4 to 9 months |
Ranges are 2026 US-buyer guide-based planning benchmarks. Where applicable to the agreed migration, parallel-running infrastructure, senior-staff knowledge transfer and compliance revalidation for actual SOX, HIPAA or FDA requirements can add a planning allowance of $100K to $500K or more across vendor paths. Scope covers agreed engineering and revalidation support; any independent assurance engagement is scoped separately. These are engagement planning allowances, not an empirical market survey or an automatic surcharge for every system.
Proposal evaluation criteria
When evaluating vendor proposals for legacy modernization, assess these areas with named role responsibilities:
- Scope and system discovery. What applications, databases, integrations and scheduled jobs are inventoried? Who performs code archaeology, business-rule documentation and gap analysis? What is included versus excluded from the engagement scope?
- Integration and migration acceptance. What are the agreed data migration tolerances, reconciliation method and domain-owner sign-off criteria? Who builds and validates migration scripts? How are legacy formats, encoding and data quality exceptions handled?
- Security and data rights. Who owns source code, data and deployed infrastructure after handover? What are data retention, deletion and portability terms? How is Law 13/2016 or QFC compliance responsibility allocated between customer and vendor?
- Verification, rollback and operations. What regression, performance and UAT methodology is proposed? What is the rollback plan after schema and data changes? Who monitors production post-cutover and for how long?
- Delivery ownership and cost dependencies. What is fixed-scope versus time-and-materials? What are infrastructure, licensing and parallel-running cost responsibilities? What triggers change orders? Are independent CPA SOC 2 opinions scoped separately from readiness preparation?
- Training, validation, support and working arrangements. Who trains end users, in what agreed working languages, and with what approved translated materials? Who provides ongoing support and at what SLA? What on-site arrangements are separately agreed if required? What customer staff participation is needed for domain validation and UAT?
Need help modernizing Doha enterprise systems?
Share your legacy system landscape, Arabic requirements and modernization constraints. We provide a scoped estimate based on system complexity.
How delivery works
ZTABS is remote-first by design from our Houston, Texas office. Overlap with Doha business hours for coordination and review. Working languages and translated materials agreed per engagement.
When ZTABS is not the right fit
- The system still works and nobody is asking for changes. Wait for a real forcing function before committing to modernization.
- Oracle APEX migration within Oracle ecosystem for this engagement. A separately engaged Oracle partner handles licensed APEX implementation.
- On-site embedded team required for this engagement. ZTABS is remote-first by design. On-site staffing is a separately agreed arrangement.
- QCB or QFC regulatory advisory for this engagement. Regulatory advisory is a separate engagement from platform engineering.
- Sharia compliance advisory for this engagement. ZTABS implements technical calculations; Sharia rulings are a separately engaged advisory scope.
White-label AI products
ZTABS builds custom white-label AI products for clients to brand and resell. Doha technology companies can commission white-label AI platforms for distribution under their own brand.
Logs and retention
Logs minimise and redact secrets and regulated payloads with actual retention and legal holds. QCB banking records retained per supervisory requirements. Government licensing records retained per administrative statute. Not all logs have the same retention period. QID and personal identifiers minimised where full identifier unnecessary.
Risks and mitigations
Arabic text encoding. Mojibake detection and automated repair during migration. UTF-8 standard encoding in all modernized systems.
Islamic finance logic preservation. Calculation rules documented and verified with agreed fixtures and tolerances through parallel operation against legacy system outputs. Domain-owner approval required for results; historical legacy logic is not assumed inherently correct for every edge case.
Oracle licensing reduction. Migration to PostgreSQL reduces Oracle Database, Forms, Reports and WebLogic licensing costs for migrated workloads. Retained workloads, parallel-running periods and existing contract terms affect actual licensing changes.
Handover
Modernization handover includes runbooks, data lineage, licensing, support contacts and accountable owners. Government handover includes Hukoomi integration documentation and regulatory compliance records. Banking handover includes QCB reporting specifications and Islamic finance calculation documentation.
Ready to modernize your Doha legacy systems?
Share your legacy system landscape, Arabic requirements and modernization constraints. We start with assessment covering application archaeology, compliance mapping and modernization strategy.