ZTABS delivers legacy app modernization in Abu Dhabi — Oracle Forms migration, government system replacement, ADGM financial platform upgrades, and energy operational technology modernization — Arabic-first with zero-downtime transitions.
Legacy app modernization in Abu Dhabi confronts a technology landscape where critical systems — processing government licences, managing energy production, tracking financial portfolios, and coordinating healthcare — are running on platforms deployed 10-20 years ago, increasingly unable to support modern requirements while simultaneously too embedded in operations to simply switch off. Abu Dhabi's legacy modernization landscape is shaped by: Oracle Forms dominance in government (Abu Dhabi government entities widely deployed Oracle Forms 10g and 11g during 2005-2015 — these thick-client applications managing core government operations: licensing, permits, inspections, case management, and financial processing. Oracle Forms: requiring desktop installation, direct database connections, and specific Java Runtime Environment versions — incompatible with: mobile access (government officers cannot access systems from tablets or smartphones), online citizen services (Forms cannot be embedded in web portals for citizen self-service), modern integration (Forms lacking APIs for inter-entity integration through Tamm), and Arabic web interfaces (Forms' Arabic support limited to basic character display — not the rich Arabic web experience citizens expect). Oracle ending Forms mainstream support — organisations facing increasing maintenance costs, security risks from unpatched vulnerabilities, and inability to find Forms developers (a shrinking talent pool as the technology ages)), financial platform debt (ADGM firms operating on legacy financial platforms — portfolio management systems deployed 8-15 years ago, trading platforms built on deprecated technology, and compliance systems implemented pre-FSRA that do not meet current regulatory expectations. The financial legacy challenge: these systems contain years of transaction history, client data, and business logic that took years to refine — migration risks are high because financial data accuracy is non-negotiable. A migration error that loses a single transaction record could trigger FSRA investigation. Legacy financial systems: also missing modern capabilities — API connectivity for fintech partnerships, real-time data for AI analytics, and mobile interfaces for client engagement), energy OT modernization (ADNOC and Abu Dhabi energy operators running operational technology systems deployed 15-30 years ago — SCADA systems, DCS (Distributed Control Systems), and historians from an era before cybersecurity was a primary concern and before OT/IT convergence was possible. These systems: controlling physical equipment (pumps, compressors, valves) — modernization cannot risk operational disruption. A failed modernization of an OT system could shut down a processing facility costing millions of dirhams per day. Energy legacy challenge: modernizing while maintaining continuous safe operations — systems cannot be taken offline for migration, data integrity must be absolute, and the modernized systems must maintain the real-time performance characteristics that operations depend on), and healthcare system fragmentation (Abu Dhabi healthcare legacy: hospital information systems deployed 10-15 years ago, departmental systems (laboratory, radiology, pharmacy) from different vendors on different technology generations, and insurance processing systems built before electronic claims were standard. Healthcare legacy challenge: patient safety — modernization must ensure continuous access to patient data during transition, no data loss or corruption, and maintained interoperability between systems that are being modernized at different times).
Abu Dhabi's legacy modernization demand spans government, financial services, energy, and healthcare. Government modernization: Oracle Forms to web. Government legacy patterns: Oracle Forms replacement (the most common government modernization: replacing Oracle Forms 10g/11g applications with modern web applications. The target: Arabic-first web applications accessible through browsers on any device — desktop, tablet, and mobile. API-enabled: the modernized application exposing data through REST APIs for Tamm integration, mobile app consumption, and inter-entity data sharing. The challenge: Forms applications often contain complex business logic embedded in PL/SQL database procedures — logic that has been refined over 10-15 years by government officers and IT staff. Modernization must: preserve this business logic (not lose years of refinement), improve the user experience (Arabic web interface vs. Forms thick client), enable new capabilities (online citizen access, mobile, APIs), and ensure data continuity (15+ years of transaction data must be fully accessible in the modernized system)), legacy database modernization (government entities running Oracle 11g or older databases — approaching or past end-of-support. Modernization options: upgrade to Oracle 19c (least disruption but continued Oracle licensing costs), migrate to PostgreSQL (open-source, reducing licensing costs by AED 200,000-500,000 annually, but requiring application changes), or migrate to Azure SQL (managed database service on Azure UAE North — reducing operational overhead). The database decision: influenced by the entity's broader cloud strategy and ADDA's technology direction), and departmental system consolidation (government departments running standalone Access databases, Excel solutions, and small applications for specific functions — tracking permits, managing inventory, scheduling inspections. These "shadow IT" systems: containing critical operational data but without proper security, backup, or integration. Modernization: consolidating departmental systems into enterprise-grade applications — capturing the business functionality while adding proper data management, security, and integration). Financial modernization: platform migration. ADGM financial modernization: portfolio management upgrade (migrating from legacy portfolio management platforms to modern solutions — Charles River, Bloomberg AIM, or custom platforms built on modern architecture. The migration: transferring years of portfolio history, transaction records, and client configurations — with audit trail continuity for FSRA examination. Testing: reconciliation testing against the legacy system ensuring that portfolio valuations, performance calculations, and regulatory metrics produce identical results in the new system), compliance system modernization (legacy compliance systems — AML transaction monitoring, trade surveillance, and regulatory reporting — built before FSRA's current regulatory expectations were established. Modernization: implementing systems that meet current FSRA requirements while preserving historical compliance data for the mandatory 5-year retention period), and trading platform upgrade (upgrading trading infrastructure — from legacy FIX protocol implementations to modern trading connectivity, from batch reconciliation to real-time position management, and from end-of-day risk calculation to real-time risk monitoring)). Energy modernization: OT refresh. Energy legacy modernization: SCADA/DCS upgrade (upgrading control systems — from legacy proprietary platforms to modern standards-based systems. The critical constraint: zero unplanned production impact. Modernization approach: parallel installation (new system running alongside old system, with data comparison), staged migration (migrating one process area at a time — not the entire facility simultaneously), and fallback capability (ability to revert to the legacy system within minutes if issues arise)), historian migration (migrating time-series production data from legacy historians (PI, PHD) to modern data platforms — preserving decades of production data for analytics while enabling modern data access patterns. The data: often petabytes of time-series data spanning 20+ years — migration must maintain data integrity, timestamp accuracy, and tag mapping)), and SCADA cybersecurity retrofit (adding cybersecurity controls to legacy OT systems that were designed without security considerations — network segmentation, access controls, monitoring, and incident response. Not modernizing the OT systems themselves but adding a security layer around them)). Healthcare modernization: EHR and integration. Healthcare legacy modernization: HIS replacement (replacing hospital information systems — the highest-risk healthcare modernization due to patient safety implications. Approach: parallel running (old and new systems operating simultaneously during transition), data migration (complete patient history transferred with clinical validation), and phased go-live (department by department rather than big-bang — starting with lower-risk departments)), and integration modernization (replacing point-to-point interfaces between healthcare systems with modern integration — HL7 FHIR APIs replacing older HL7 v2 messages, enabling new interoperability patterns and preparing for Abu Dhabi-wide health information exchange).
Our Abu Dhabi legacy modernization methodology minimises risk while maximising the speed and completeness of transformation. Modernization strategy: choosing the right approach for each system. Assessment framework: evaluating each legacy system to determine the optimal modernization approach. Factors: business criticality (how important is this system to operations? Can it tolerate any downtime?), technical condition (how outdated is the technology? What is the security risk of continuing to operate it?), business logic complexity (how much domain-specific logic is embedded in the system? How well is it documented?), data volume and importance (how much historical data must be preserved? What are the regulatory retention requirements?), and integration dependencies (how many other systems depend on this one? How complex are the integration touchpoints?). Modernization approaches: replatform (move the application to modern infrastructure without changing functionality — lowest risk, fastest, but limited improvement), refactor (restructure the application code for modern architecture while preserving business logic — moderate risk, significant improvement), rebuild (develop a new application based on the legacy system's requirements — higher risk, complete modernization), and replace (implement a commercial off-the-shelf product to replace the legacy system — highest risk of functionality gaps, fastest for standard processes). For Abu Dhabi government Oracle Forms: typically rebuild — Forms applications contain deeply customised government workflows that commercial products do not replicate. For ADGM financial systems: typically replace (with proven financial platforms) or refactor (custom systems with complex domain logic). For energy OT: typically replatform or refactor — preserving operational characteristics while adding modern interfaces and security. Migration: zero-downtime transition. Parallel running: the legacy and modern systems running simultaneously during transition. Data synchronisation: changes in the legacy system automatically reflected in the modern system (and vice versa during the parallel period). Phased cutover: migrating user groups or functional areas one at a time — each group using the modern system for a defined period before the next group transitions. Rollback: at any point during parallel running, the organisation can revert to the legacy system — the parallel period only ending when the modern system has proven reliable over a sustained period (typically 4-8 weeks of stable operation). Data migration: structured, verified, complete. Abu Dhabi legacy data migration: extraction (pulling data from legacy databases — often requiring reverse-engineering of undocumented database schemas and understanding data relationships that are not explicitly defined in foreign keys), transformation (converting legacy data formats to modern data models — Arabic name standardisation, address restructuring, date format conversion (some legacy systems storing Hijri dates, others Gregorian), and code mapping (legacy system codes translated to modern classification schemes)), loading (inserting transformed data into the modern database — in batches with verification after each batch), and verification (automated verification: record counts match, financial totals match, key fields match, and sample record comparison. Arabic verification: Arabic text correctly encoded, Arabic names properly formatted, and Arabic search functioning correctly on migrated data). Arabic-first modernization: every modernized system designed Arabic-first — not the legacy approach of English systems with Arabic patches, but modern web applications designed for Arabic users with English as a parallel option.
Government / Licensing & Regulation
An Abu Dhabi government entity (managing commercial licensing for 40,000+ businesses across 15 activity categories — processing 120,000 regulatory transactions annually including new applications, renewals, amendments, and cancellations) was running its core licensing system on Oracle Forms 10g deployed in 2010. The Oracle Forms system: 14 years old, processing every licensing transaction the entity handled — the single most critical system in the entity's operations. What worked: the system accurately managed the licensing workflow — application intake, officer review, approval routing, fee calculation, licence generation, and renewal tracking. 14 years of business logic: handling 250+ business rules (fee calculations, eligibility criteria, document requirements, and approval authorities) refined over the years by subject matter experts and developers. What did not work: no online access (businesses applying for licences by visiting the entity's service centre — submitting paper forms, paying at the counter, and returning to collect the licence. No ability to apply, pay, or check status online. 65,000 annual walk-in visits attributable to the licensing system — averaging 45 minutes per visit), no mobile access (inspectors using paper forms in the field, returning to the office to enter findings into Forms. Officers unable to access the system from meetings, conferences, or home — limited to their desktop where Forms was installed), no Arabic web experience (Forms displaying Arabic characters but with: English-labelled fields (Arabic text entered into English-named fields), no RTL layout (Arabic text displayed left-to-right in form fields), and limited Arabic printing (printed licences with Arabic text often misaligned)), no integration (the licensing system isolated — no API for Tamm integration, no data sharing with other entities, and no integration with the entity's newer CRM and inspection systems. Inter-entity verification: other entities calling the licensing team to verify business licence status — 25,000 calls annually), and technology risk (Oracle Forms 10g: past end of life. Java Runtime Environment: running JRE 6 — multiple known security vulnerabilities with no patches available. The entity's cybersecurity assessment: flagging the Forms system as the highest technology risk in the organisation. Oracle database: 11g — approaching end of support, requiring upgrade regardless of the Forms decision). Staff impact: 6 developers maintained the Forms system — all over 50 years old, the youngest having 18 years of Forms experience. Recruiting replacement Forms developers: impossible — no new graduates learning Oracle Forms. If any of the 6 developers left, the entity would struggle to maintain the system. Previous modernization attempt: the entity had attempted modernization 3 years prior — a project to rebuild the licensing system using a commercial low-code platform. The project: failed after 18 months and AED 2.8M spent — the low-code platform unable to replicate the 250+ business rules, the project team unable to extract and document all the business logic from the Forms application and PL/SQL procedures. The failure: creating organisational anxiety about modernization — leadership concerned that another attempt would also fail.
We approached the modernization as a systematic extraction and reconstruction over 24 weeks. Business logic archaeology (weeks 1-6): extracting 14 years of knowledge. The key insight: the previous failed attempt treated modernization as a green-field development project — gathering requirements from users and building new. This missed the accumulated business logic embedded in code. Our approach: systematic extraction of business logic from the existing system. PL/SQL analysis: the Oracle database contained 180 PL/SQL stored procedures and 95 database triggers — together containing 42,000 lines of code. We analysed every procedure and trigger: documenting what it does (in plain language, Arabic and English), what inputs it requires, what outputs it produces, and what business rule it implements. The analysis: uncovering 287 distinct business rules — 37 more than the entity believed existed. The additional 37: rules added over the years through small changes that were never documented in requirements (e.g., a fee calculation exception for a specific activity category added in 2016 after a regulatory change — implemented in PL/SQL but never recorded in any requirements document). Forms analysis: 65 Oracle Forms screens containing: field validations (mandatory fields, format checks, cross-field validations), conditional display logic (fields appearing/disappearing based on other field values), and workflow routing logic (determining which officer reviews which application type). Extracting: 145 UI business rules not present in the database layer — rules implemented in the Forms client rather than the database. User knowledge capture: conducting structured sessions with the 6 Forms developers and key government officers — capturing knowledge that was not in the code. Examples: "when a business applies for this category in Zone 3, we also need to check with the municipality — this is not in the system, we do it manually" (a gap in the legacy system that should be addressed in the modern version), and "the fee calculation for Category 7 has a special rate during the first quarter — it was added as a temporary promotion in 2018 but we kept it" (undocumented business rule implemented as a "temporary" code change). Modern platform development (weeks 4-16): Arabic-first web application. Technology: Next.js frontend with full Arabic RTL implementation, Node.js backend with all 287 business rules implemented as testable, documented modules, and PostgreSQL database on Azure UAE North. Arabic-first design: every screen designed for Arabic users first — Arabic typography, RTL layout, Arabic form field labels, Arabic validation messages, and Arabic document generation. English: available as a toggle for English-preferring officers and international businesses — not a translated Arabic interface but a purpose-designed English version. Online citizen portal: businesses applying online — form completion, document upload, payment (integrated with Abu Dhabi payment gateway), and status tracking. Mobile responsive: the same web application working on tablets and phones — inspectors accessing the system in the field, officers checking applications from meetings. API layer: REST APIs exposing licensing data — for Tamm integration (citizens accessing licensing services through the unified government portal), inter-entity verification (other entities checking business licence status through API rather than phone calls), and mobile app (the entity's mobile app consuming the same APIs as the web application). Business rule validation (weeks 8-16): ensuring nothing is lost. The critical phase: verifying that the modern system produces identical results to the legacy system for every business rule. Automated testing: creating test cases for each of the 287 business rules — test data representing every licence type, fee scenario, eligibility condition, and approval pathway. Running the test data through both the legacy system (Oracle Forms/PL/SQL) and the modern system (Node.js) — comparing results. Initial comparison: 94.3% match (271 of 287 rules producing identical results). The 16 mismatches: 8 undocumented legacy bugs (the modern system was correct, the legacy system had bugs that had gone unnoticed — e.g., a rounding error in a fee calculation that consistently undercharged by AED 5), 5 ambiguous business rules (legacy implementation differed from documented requirements — resolved through officer workshops to determine the correct behaviour), and 3 genuine modernization issues (our implementation differed from legacy — corrected to match legacy behaviour). After correction: 100% match on all 287 business rules — verified through automated test suite. Data migration and transition (weeks 14-24): zero-loss transfer. Data migration: 15 years of licensing data — 40,000 active business records, 450,000 historical transaction records, and 120,000 documents (attached to applications over the years). Migration approach: full data migration with Arabic name standardisation (resolving 3,500 duplicate records where the same business was recorded with different Arabic name spellings), historical data preservation (all 15 years of transaction history accessible in the modern system — officers able to view the complete history of any business), and document migration (120,000 documents migrated from Oracle BLOB storage to Azure Blob Storage — each document re-linked to the corresponding business and transaction records). Parallel running: 6 weeks of parallel operation — every transaction processed in both the legacy and modern systems simultaneously. Officers using the modern system as primary, with legacy system available as reference. Automated comparison: nightly reconciliation confirming that both systems contained identical data. Parallel running result: zero discrepancies over the 6-week period — confirming the modern system was fully equivalent to legacy.
The modern platform launched at week 18 (officers) with full transition at week 24 (citizen portal and legacy decommission). Processing time: from 22 business days to 5 business days (average). For renewals with no changes: 1 business day (automated approval for compliant businesses). For new applications: 7 business days. The improvement: online submission eliminating paper handling (5 days saved), automated eligibility checking replacing manual verification (3 days saved), electronic workflow replacing physical file routing (4 days saved), and automated fee calculation replacing manual lookup (2 days saved). Online adoption: 72% of transactions submitted online within 6 months (from 0% — the legacy system had no online option). The remaining 28%: businesses preferring in-person service (primarily older business owners) and complex applications requiring consultation. Walk-in reduction: from 65,000 annual visits to 22,000 (66% reduction). The remaining visits: services requiring physical presence and in-person preference. Inter-entity verification: from 25,000 phone calls annually to API-based verification — other entities checking licence status programmatically in real-time. Zero manual verification calls after full Tamm integration. Arabic experience: the first purpose-built Arabic licensing interface — officers reporting: "Finally, a system that speaks our language" (Arabic-first design vs. the previous English Forms with Arabic characters). Arabic document generation: licences, certificates, and official letters produced in proper Arabic typography — replacing the misaligned Arabic output from Oracle Forms. Technology risk elimination: Oracle Forms 10g and JRE 6 decommissioned — the highest cybersecurity risk in the entity eliminated. Oracle 11g database migrated to PostgreSQL on Azure — eliminating AED 380,000/year in Oracle licensing. The 6 legacy Forms developers: 2 retired (planned), 2 retrained as modern web developers (Node.js/TypeScript — participating in the modernization project as domain experts), and 2 transitioned to system administration and support roles. Staff and citizen impact: officer productivity: 2.3x improvement — the modern web interface enabling faster processing with better information presentation. Citizen satisfaction: from 3.0/5 to 4.2/5 — driven by online access, faster processing, and Arabic digital experience. Financial impact: walk-in reduction (43,000 fewer visits × AED 45/visit processing cost): AED 1.94M/year. Processing speed (citizen economic value): AED 4.8M/year. Oracle licence elimination: AED 380,000/year. Staff productivity: AED 2.1M/year. Cybersecurity risk reduction: AED 1.5M/year (actuarial value of eliminated vulnerability). Inter-entity efficiency (API replacing phone verification): AED 0.6M/year. Total annual impact: AED 11.32M. Modernization cost: AED 3.6M. Annual operations: AED 420,000. First-year ROI: 214%.
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.
Abu Dhabi's legacy modernization market includes global consulting firms (Accenture, Deloitte, TCS — offering modernization as part of broader IT transformation with large teams), Oracle partners (offering Oracle Forms migration to Oracle APEX or Oracle Cloud — keeping the client in the Oracle ecosystem), low-code platform vendors (OutSystems, Mendix — offering rapid modernization through low-code platforms, but the previous failed attempt at this entity demonstrated the limitations of low-code for complex government logic), and regional IT companies (offering modernization with local teams — varying depth of legacy system analysis and modern architecture expertise). ZTABS differentiates through business logic archaeology (systematically extracting embedded business rules from legacy code — not just gathering requirements from users (who may not remember all the rules) but analysing the actual code that has accumulated knowledge over 10-15 years), Arabic-first modernization (modern web applications designed for Arabic users — not English systems with Arabic language packs but purpose-built Arabic digital experiences), zero-downtime transition methodology (parallel running, phased cutover, and verified rollback — ensuring the organisation never loses access to critical operations during transition), and Abu Dhabi government context (understanding government workflows, ADDA standards, Tamm integration requirements, and the specific challenges of modernizing Abu Dhabi government systems that have been accumulating business rules for 15+ years).
Legacy app modernization in Abu Dhabi ranges by system complexity. Legacy assessment (system analysis, modernization strategy, business case, 3-5 weeks): AED 100,000-250,000. Simple application modernization (standalone system, limited integration, 8-14 weeks): AED 300,000-700,000. Complex application modernization (core business system, multiple integrations, 250+ business rules, 16-24 weeks): AED 800,000-2,500,000. Enterprise platform modernization (multiple connected systems, data migration, 20-32 weeks): AED 1,500,000-5,000,000. Energy OT modernization (safety-critical, parallel running, staged migration, 24-40 weeks): AED 2,000,000-8,000,000. Annual post-modernization support: AED 150,000-400,000/year.
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 Abu Dhabi businesses
Business logic archaeology: we systematically extract rules from legacy code (PL/SQL, Forms triggers, application logic), document them, and verify the modern system produces identical results. Automated comparison testing confirms 100% functional equivalence before transition.
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 Abu Dhabi, United Arab EmiratesZTABS is a remote-first web development agency serving Abu Dhabi businesses — including full-stack development, progressive web apps, api development. We work with Energy Tech, FinTech, HealthTech companies in Abu Dhabi, United Arab Emirates 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 Abu Dhabi, United Arab EmiratesZTABS is a remote-first web design agency serving Abu Dhabi businesses — including ui/ux design, responsive design, custom interfaces. We work with Energy Tech, FinTech, HealthTech companies in Abu Dhabi, United Arab Emirates 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 Abu Dhabi, United Arab EmiratesZTABS is a remote-first AI development agency serving Abu Dhabi businesses — including llm integration & fine-tuning, ai agents & automation, rag & knowledge systems. We work with Energy Tech, FinTech, HealthTech companies in Abu Dhabi, United Arab Emirates 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 Abu Dhabi. Get a free consultation today.
