Legacy App Modernization in Abu Dhabi for Government, Healthcare and Finance

ZTABS modernizes legacy applications for Abu Dhabi enterprises in government, healthcare, financial services and energy. Abu Dhabi government entities operate Oracle Forms and legacy database systems managing licensing, permits and citizen services through TAMM platform. Healthcare providers operate clinical and administrative systems needing Malaffi integration. ADGM financial services firms run platforms requiring modernization. ZTABS is remote-first by design from our Houston, Texas office.

Abu Dhabi's legacy modernization demand spans government Oracle Forms migration through DGE and TAMM digital government platform, healthcare system upgrades for ADHICS compliance and Malaffi clinical health information exchange integration, and ADGM financial platform modernization for regulatory compliance and digital services.

Legacy app modernization in Abu Dhabi at a glance

Need	What we build	Key requirement
Government	Oracle Forms migration	TAMM, DGE, Onwani
Healthcare	System upgrades	ADHICS, Malaffi, DoH
ADGM finance	Platform modernization	ADGM DPR, FSRA
Energy	Operations system upgrades	ADNOC ecosystem
Enterprise	Legacy system migration	PDPL, data residency

Government Oracle Forms modernization

Abu Dhabi government entities operate Oracle Forms applications managing licensing, permits, inspections, payments and citizen interactions through the TAMM unified government services platform.

DGE and TAMM. The Department of Government Enablement (DGE) consolidates Abu Dhabi digital government functions and oversees the TAMM unified government services platform. TAMM is Abu Dhabi's platform, not Dubai. Government system modernization aligns with DGE digital transformation objectives and TAMM service delivery standards.

Licensing systems. Business licensing, professional licensing and activity permits processed through Oracle Forms with multi-step approval workflows. Legacy forms replaced with modern digital government services accessible through UAE Pass and TAMM portal.

Onwani addressing. Abu Dhabi uses Onwani addressing system. Not Dubai Makani. Government systems modernized with appropriate Abu Dhabi geo-location and addressing integration.

MoF e-invoicing ASP. Ministry of Finance Accredited e-Invoicing Service Provider framework. Ministerial Decision 168 of 2026 effective October 1 replaces previous decisions. ASP accreditation applies to e-invoicing service providers, not all ERP or government financial system developers. Covered businesses integrate with an accredited ASP for e-invoice submission.

Healthcare system modernization

Abu Dhabi healthcare providers operate clinical and administrative systems requiring modernization for ADHICS compliance and Malaffi clinical health information exchange integration.

ADHICS compliance. DoH Abu Dhabi Healthcare Information and Cyber Security standard applies to actual health facility, payer, tech service entity and health data scope. Not all technology is automatically health information system scope. Healthcare system modernization meets ADHICS requirements for applicable entities and data.

Malaffi integration. Abu Dhabi clinical health information exchange for sharing patient records, lab results, radiology reports and medication history among authorised care teams for current clinical purposes. Not a payer claims adjudication channel. Healthcare system modernization integrates with Malaffi per approved provider access specifications.

Clinical system upgrades. Legacy clinical systems modernized for electronic health records, patient portal access and clinical decision support. ADHICS security requirements embedded in architecture from the beginning.

Payer system modernization. Health insurance payer systems processing claims, authorisations and provider payments. Legacy claims adjudication and payment systems modernized for digital submission and real-time processing through applicable payer channels.

ADGM financial platform modernization

Abu Dhabi Global Market financial services firms operate platforms requiring modernization for FSRA regulatory compliance, client reporting and digital service delivery.

ADGM DPR. Data Protection Regulations apply based on context of establishment regardless of outside processing. Different from federal UAE PDPL. Different from DIFC Data Protection Law. Three distinct data protection frameworks for Abu Dhabi, Dubai free zone and federal onshore.

SFO. Single Family Office operating within ADGM has specific regulatory framework. Not all family office activities are SFO scope.

Trading and portfolio platforms. Legacy trading, portfolio management and client reporting systems modernized for current FSRA requirements and digital client experience.

Energy sector modernization

Abu Dhabi energy companies operate production, operations and maintenance systems on legacy platforms.

Operations systems. Production monitoring, maintenance scheduling and safety management on legacy platforms. Modernization enabling IoT integration and real-time operational visibility. Energy and industrial IoT control writes require explicit engineering-approved envelopes, independent safety interlocks, validation and change authority; not inferred as safe defaults.

Supply chain. Procurement, inventory and logistics systems modernized for digital supply chain management and vendor portal access.

Abu Dhabi and UAE regulation

Federal UAE PDPL. Article 2 excludes government data and entities from PDPL scope. The special-law exclusion concerns data whose protection and processing are regulated by specific health or banking legislation, not every record belonging to an entire health or banking organisation. Free zones with their own data protection laws have their own frameworks outside federal PDPL. Actual PDPL applicability depends on entity, data type and processing nexus.

ADGM DPR. Context of establishment regardless of outside processing. Different from DIFC and federal PDPL. Distinct regulator and requirements.

Azure UAE Central. Abu Dhabi with restricted availability for specific workloads and products. UAE North is Dubai. Different regions for data residency. Cloud infrastructure based on actual workload requirements and data residency.

Core42. Merger of Injazat, G42 Cloud and Inception. Actual current product and service offerings. Abu Dhabi based sovereign cloud provider.

Onwani. Abu Dhabi addressing system. Not Dubai Makani. Correct addressing system per jurisdiction.

UAE Pass and TAMM. ICP actual onboarding, product, user and role permissions. Not all government services automatically integrated. TAMM is Abu Dhabi only.

WhatsApp. Customer service window is 24 hours from the last user message. Outside this window, only pre-approved message templates to opted-in recipients.

Cloud terms. Actual cloud training, log, backup, SDK and support terms verified per provider.

Strangler fig for government systems

Seam selection. Government seams: licensing, permits, inspections, payments, document management, TAMM integration. Each function extracted independently.

Single authoritative write. One system authoritative for each licence and period during coexistence. Government dual-write dangerous for regulatory status tracking. 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 licence status changes and fee payments.

Data migration methodology

Government data. Licence records, permit histories, inspection records, payment transactions and citizen data migrated with regulatory verification. Arabic and English bilingual content preserved. TAMM integration data verified.

Healthcare data. Patient records, clinical data and Malaffi clinical exchange data migrated with ADHICS security controls. DoH health data scope requirements maintained. Insurance claims data migrated separately with applicable payer system controls.

Financial data. ADGM financial services data migrated with FSRA regulatory compliance. Client records, transaction history and regulatory reporting data preserved.

Data type mapping. Types, nulls, time zones, currency, rounding, identifiers, encoding, history and crosswalks reconciled. Government-specific: licence types with regulatory classification, Hijri and Gregorian dates, Emirates ID numbers, Onwani addresses. Healthcare-specific: patient identifiers, Malaffi clinical exchange records, ADHICS security classifications. ADGM-specific: client identifiers, FSRA reporting fields, SFO entity types. Fee schedules where VAT at 5 percent applies to commercial transactions; sovereign government services may be outside VAT scope.

Cutover rehearsal. Observable acceptance with measurable RTO, RPO and latency targets. Government cutover timed for licensing cycle boundaries. Healthcare cutover timed for Malaffi integration windows. ADGM cutover timed for FSRA reporting periods.

Inventory and discovery

Abu Dhabi enterprise modernization begins with inventory of applications, users, scheduled jobs, database procedures, reports, file and API dependencies, vendor contracts, supported versus end-of-life versions. Discovery documents known dependencies; undiscovered dependencies may surface during parallel operation.

Business rules discovered with users through representative transaction analysis. Government rules validated against DGE and TAMM requirements. Healthcare rules validated against ADHICS and DoH requirements. ADGM rules validated against FSRA requirements.

Integration and dependency management

Government integrations. DGE and TAMM platform, UAE Pass identity, Onwani addressing, MoF e-invoicing ASP and inter-entity connections. Each integration documented and migration coordinated.

Healthcare integrations. Malaffi clinical health information exchange, DoH regulatory reporting, insurer connections and provider network.

ADGM integrations. FSRA regulatory reporting, international financial data providers and correspondent connections.

Authentication versus authorisation. Authentication identity distinct from entity-level, role-level and transaction-level authorisation. Government systems require audit trail for all authorisation changes.

Modernization approach selection

Abu Dhabi enterprises need clear criteria for choosing between approaches.

Targeted remediation. Adding specific capabilities to otherwise functional systems. Example: adding API layer for TAMM integration while keeping Oracle Forms for back-office processing.

Re-platforming. Moving to modern infrastructure while preserving logic. Example: migrating Oracle Forms licensing to cloud while preserving approval workflow rules and TAMM integration.

Re-architecture. Decomposing monolith into services. Example: extracting licensing, permits, payments and Malaffi integration as independent services.

Full rebuild. Ground-up development as part of Abu Dhabi digital government transformation.

Regression and testing

Representative business-critical paths: licensing lifecycle through TAMM, healthcare clinical exchange through Malaffi, ADGM financial reporting. 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 target, rehearsed staged cutover

Vendor comparison

Ranges are 2026 US-buyer guide-based estimates for 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
ZTABS	$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 benchmarks from the published cost guide. Parallel-running infrastructure, senior knowledge transfer and where applicable compliance revalidation can add a combined scope-dependent $100K to $500K+ planning allowance. The guide's examples are SOX, HIPAA and FDA; actual applicable regime depends on the engagement.

Proposal evaluation criteria

Evaluate any vendor proposal against these six criteria regardless of price tier.

Criterion	What to verify
Strategy, deliverables and acceptance	Defined modernization phases with measurable acceptance criteria at each stage
Data source-of-truth and reconciliation	Which system is authoritative per object and period, agreed reconciliation tolerances and exception register
Rehearsal, cutover and rollback	Rehearsed cutover with RTO and RPO targets, documented rollback feasibility after schema and data changes
Security, privacy, compliance and approval scope	Applicable regulations identified with actual approval authority and scope
Full recurring costs	Licensing, parallel-run infrastructure, support, monitoring and decommission costs beyond initial build
Human roles and responsibilities	Provider and customer trainer-validator-support split, agreed working languages, translated materials review and on-site responsibilities where needed

How delivery works

ZTABS is remote-first by design from our Houston, Texas office. Overlap with Abu Dhabi business hours for coordination and review.

When ZTABS is not the right fit

• The system still works and nobody is asking for changes. Wait for a real forcing function.
• Oracle ERP implementation. Licensed vendor selection and implementation scope.
• On-site embedded team. ZTABS is remote-first by design. On-site staffing, training and support retainers for this engagement are separately agreed.
• ADGM FSRA or DoH regulatory advisory. This engagement builds platforms, not regulatory advice. Regulatory advisory is separately engaged.

White-label AI products

ZTABS builds custom white-label AI products for clients to brand and resell. Abu Dhabi 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. Government records retained per Abu Dhabi and federal requirements. Healthcare records retained per ADHICS and DoH requirements. ADGM records retained per ADGM DPR and FSRA requirements.

Cutover rehearsal detail

Observable acceptance with measurable RTO, RPO and latency targets. Government cutover timed for licensing cycle boundaries. Healthcare cutover timed for Malaffi integration windows. ADGM cutover timed for FSRA reporting periods.

Rollback feasibility assessed after schema, data and contract changes. Licence status changes, healthcare record updates, Malaffi exchange records and ADGM financial transactions may not be automatically reversible. Compensations can require legal, regulatory, clinical or accounting review.

Data type mapping for Abu Dhabi industries

Abu Dhabi industry data has unique types requiring careful migration planning. Government: licence types with DGE classification, Hijri and Gregorian dates with conversion rules, Emirates ID numbers, Onwani addresses distinct from Dubai Makani codes, fee schedules where VAT at 5 percent applies to commercial transactions. Healthcare: patient identifiers with Malaffi clinical exchange format, ADHICS security classifications, DoH provider identifiers, clinical coding schemes. ADGM: client identifiers with FSRA format, SFO entity classifications, regulatory reporting fields, international financial instrument identifiers.

Risks and mitigations

Business rule gaps. Oracle Forms PL/SQL archaeology combined with parallel operation catches undiscovered rules within agreed discovery coverage. Government domain experts validate extracted licensing and permit rules with sign-off; undiscovered rules remain a managed residual risk.

ADHICS compliance. Healthcare system modernization validated against ADHICS requirements before deployment.

Data residency. Abu Dhabi data residency for covered data, contracts and applicable entity obligations scoped at engagement start. Full-stack residency including storage, backups, logs, support access and subprocessor jurisdictions verified per provider before commitment. Azure UAE Central has restricted product availability; actual workload and region suitability checked and agreed before selection.

Handover

Modernization handover includes runbooks, data lineage, licensing, support contacts and accountable owners. Government handover includes DGE compliance documentation, TAMM integration specifications and Onwani addressing documentation. Healthcare handover includes ADHICS compliance evidence and Malaffi clinical exchange integration specifications.