ZTABS modernizes legacy applications for Singapore enterprises — migrating mainframe systems, COBOL codebases, and monolithic applications to cloud-native architectures. MAS TRM-compliant migration strategies for financial services, government digital transformation, and enterprise systems built for Singapore's future.
Singapore runs on legacy systems that work — until they don't. The Monetary Authority of Singapore's core systems, DBS Bank's original transaction processing, SingTel's billing platforms, and government systems built during Singapore's rapid digitization in the 1990s and 2000s: all running on technology stacks that are increasingly difficult to maintain, impossible to recruit for, and incompatible with Singapore's Smart Nation ambitions. The typical Singapore enterprise legacy stack: COBOL on IBM mainframes (banking), Java 6/7 monoliths on WebSphere (insurance, telecommunications), Oracle Forms applications (government), and .NET Framework 4.x systems (corporate IT). These systems process millions of transactions daily and are deeply embedded in business operations — you cannot simply rewrite them. Modernization in Singapore carries specific constraints: MAS TRM (Technology Risk Management) guidelines govern how financial institutions change technology systems, PDPA (Personal Data Protection Act) requires that data migration preserves privacy controls, and GovTech Singapore's SGTS (Singapore Government Tech Stack) standards apply to government system modernization. The engineering challenge is surgical: decompose monoliths into microservices, migrate data without downtime, and maintain regulatory compliance throughout — all while the business continues operating.
Singapore's legacy modernization demand is concentrated in three sectors. Financial services: Singapore's 150+ licensed banks and financial institutions collectively run billions of dollars in transactions through legacy systems. DBS (Southeast Asia's largest bank by assets) completed a massive multi-year mainframe-to-cloud migration — but most Singapore banks are still early in the journey. OCBC's core banking system handles 30 million transactions monthly on infrastructure that requires specialized COBOL programmers (average age of COBOL developers in Singapore: 55+). UOB's regional banking platform spans Singapore, Malaysia, Thailand, and Indonesia — modernization must coordinate across four regulatory jurisdictions simultaneously. Insurance companies (Great Eastern, NTUC Income, AIA Singapore) run actuarial engines and policy administration on AS/400 systems that new graduates cannot maintain. MAS TRM guidelines require that technology changes to critical systems follow formal change management procedures — "move fast and break things" is not an option in Singapore financial services. Government: Singapore's Smart Nation initiative drives modernization across government agencies. GovTech Singapore has standardized on SGTS (Singapore Government Tech Stack) — a cloud-native platform using Kubernetes, microservices, and API-first architecture. Government agencies migrating from legacy Oracle/IBM systems to SGTS need to maintain service continuity for citizens using platforms like SingPass, MyInfo, and LifeSG. The challenge: government legacy systems often have 15-20 years of business logic encoded in stored procedures, batch jobs, and configuration that nobody fully documents. Telecommunications: SingTel and StarHub run billing, CRM, and network management systems on legacy stacks that struggle with the demands of 5G, IoT, and converged services. A single billing run at SingTel processes millions of records — the monolithic architecture cannot scale to handle the transaction volumes that 5G and IoT will generate. Modernization must happen without disrupting billing accuracy for millions of subscribers.
Our Singapore modernization projects follow the Strangler Fig pattern — we do not attempt big-bang rewrites. Instead, we incrementally route traffic from the legacy system to new microservices, one capability at a time, until the legacy system has no remaining responsibilities and can be decommissioned. Phase 1 — Discovery and domain decomposition (3-4 weeks): we reverse-engineer the legacy system's domain boundaries using a combination of codebase analysis (static analysis of COBOL copybooks, Java class hierarchies, or .NET assemblies), database schema mapping (understanding which tables serve which business capabilities), and — critically — interviews with the business users who actually understand what the system does (the documentation is always incomplete or wrong). We produce a domain map that identifies bounded contexts: the natural boundaries where the monolith can be decomposed into independent services. Phase 2 — Data strategy (2-3 weeks): the hardest part of modernization is data. Legacy systems typically share a single database — the database is the integration layer. Decomposing the monolith means decomposing the database, which means deciding which service owns which data, how services communicate (event-driven architecture using Kafka or Amazon EventBridge), and how to maintain data consistency without the crutch of a shared RDBMS. For MAS-regulated entities, we map data lineage to ensure that PDPA obligations (data retention, access controls, consent management) survive the migration. Phase 3 — Incremental migration (8-16 weeks per bounded context): we build the new microservice, deploy it alongside the legacy system, and use a routing layer (typically an API gateway or reverse proxy) to direct specific requests to the new service. The legacy system continues handling everything else. Database migration uses the Change Data Capture (CDC) pattern: changes in the legacy database are streamed to the new service's database in real-time, maintaining consistency during the parallel-running period. When the new service has proven itself under production load, we flip the routing — and that capability is modernized. No big bang. No weekend cutovers. No prayer-based deployment. Phase 4 — Decommission (ongoing): as bounded contexts migrate, the legacy system shrinks. When the last capability is migrated, the legacy system is decommissioned — usually with a celebration and a formal notification to MAS (for financial institutions) that the technology risk associated with the legacy system has been retired.
Insurance / Financial Services
A Singapore life insurance company (SGD 8B in assets under management, 1.2 million policyholders, MAS-regulated) ran its core policy administration on an AS/400 system written in RPG/400 — a language that fewer than 200 developers in Singapore can maintain. The system processed: new policy issuance, premium collection, claims management, agent commission calculation, actuarial data feeds, and regulatory reporting to MAS. The problems: (1) Talent: the last RPG/400 developer on staff was retiring in 18 months. Replacement candidates: effectively zero in Singapore. Contractors from India: SGD 250/hr with 3-month minimum engagements — and they needed 2 months to understand the codebase. (2) Performance: end-of-month policy renewal batch processing (500,000+ policies): taking 14 hours. The batch window: originally designed for 200,000 policies. As the book of business grew, the batch window expanded — now starting at 6pm and finishing at 8am, with no room for reruns if errors occurred. (3) Integration: the AS/400 system communicated through flat file exchanges (FTP uploads/downloads) with 12 downstream systems — agent portal, customer portal, claims management, reinsurance, accounting, MAS regulatory reporting. Adding new integration partners required custom file format specifications and batch scheduling — each new integration taking 6-8 weeks. (4) MAS compliance: MAS TRM guidelines required a formal technology risk assessment for the AS/400 platform — the assessment had flagged the single-developer dependency as a "high" risk. MAS expected a remediation plan.
We implemented the Strangler Fig migration over 20 months (ongoing — 3 of 6 bounded contexts completed): (1) Domain decomposition: 6-week discovery identified 6 bounded contexts — Policy Administration, Premium Billing, Claims, Commission, Actuarial, and Regulatory Reporting. Each context mapped to specific AS/400 programs, database files (DB2/400 physical and logical files), and batch jobs. (2) Event backbone: Apache Kafka cluster on AWS ap-southeast-1 — replacing the flat file integration pattern. Each legacy batch job now publishes events to Kafka topics; downstream systems consume events in real-time instead of waiting for nightly file drops. The Kafka infrastructure: serving as both the integration layer for the new microservices and the bridge to legacy systems still running on AS/400. (3) First migration — Premium Billing: the most self-contained bounded context. New service: Go microservices on EKS (Elastic Kubernetes Service) with PostgreSQL. CDC (Change Data Capture) from DB2/400 to PostgreSQL using Debezium — maintaining real-time data consistency during the parallel-running period. The new billing service: processing premium calculations in real-time (vs. nightly batch), generating payment requests via direct debit (GIRO) and credit card APIs, and publishing billing events to Kafka. The AS/400 billing programs: gradually decommissioned as the new service proved itself over 3 months of parallel running. (4) Second migration — Claims Management: new service on EKS with a workflow engine (Temporal) orchestrating the claims lifecycle — submission, assessment, approval routing, payment, and reinsurance notification. The claims service consuming events from the billing service (premium status affecting claims eligibility) via Kafka. (5) Third migration — Commission: agent commission calculations migrated from 4,000 lines of RPG/400 to a Go service with a rules engine — commission structures encoded as configurable business rules rather than hardcoded logic. Commission calculations: from nightly batch to real-time — agents seeing their commission immediately after a policy is issued.
Premium Billing migration: monthly batch processing from 14 hours to real-time (continuous processing). Zero billing errors in the first 6 months of the new system (vs. 12-15 errors per month requiring manual correction in the AS/400 system). Integration: 12 downstream systems migrated from flat file FTP to Kafka event streams — new integrations now taking 1-2 weeks instead of 6-8 weeks. Real-time data flow: downstream systems receiving updates in seconds instead of waiting for nightly batch files. Claims processing: average claim assessment time from 5 business days to 1.5 business days. The workflow engine: automatically routing claims to the appropriate assessor based on claim type, amount, and policy conditions. Commission: agents receiving real-time commission visibility — agent satisfaction scores increasing from 3.4/5 to 4.5/5. Agent recruitment: the company citing the modern commission platform as a competitive advantage in agent recruitment. MAS: technology risk assessment updated to reflect the migration progress — the "high" risk rating for RPG/400 dependency downgraded to "medium" (will reach "low" when all 6 contexts are migrated). The retiring RPG/400 developer: now working part-time as a consultant for the remaining 3 bounded contexts rather than being the single point of failure. Development cost (3 contexts completed): SGD 680,000 over 14 months. Remaining 3 contexts (estimated): SGD 450,000 over 10 months. Total modernization: approximately SGD 1.13M — compared to vendor quotes of SGD 4-6M for a commercial policy administration platform (Guidewire, Duck Creek). Annual savings: SGD 180,000 in AS/400 maintenance and licensing costs (realized incrementally as contexts migrate off AS/400).
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.
Singapore's legacy modernization market includes the global consultancies (Accenture, TCS, Infosys — all with large Singapore practices), local systems integrators (NCS, part of SingTel, is the dominant government IT partner), and specialist modernization firms. Accenture and TCS handle large-scale mainframe migrations but at SGD 350-500/hr with minimum engagement sizes of SGD 2M+. NCS dominates government modernization contracts but is less active in private sector insurance and banking. For COBOL/RPG/400 specifically, the talent pool is shrinking globally — making experienced modernization teams increasingly valuable. Offshore teams from India handle code-level translation (COBOL to Java) but often lack the domain understanding to decompose systems correctly — they translate syntax without understanding business logic. ZTABS provides the architectural expertise for incremental modernization at rates below the Singapore premium, with deep understanding of MAS TRM requirements.
Senior modernization architects in Singapore command SGD 200-SGD 300/hr ($150-$225 USD). MAS-regulated legacy modernization carries a 15-25% premium for compliance documentation and change management. ZTABS delivers at competitive rates — our remote-first model avoids Singapore CBD office costs (among Asia's highest commercial rents) while maintaining SGT business hours alignment for daily collaboration with Singapore development teams.
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 Singapore businesses
Named after the strangler fig tree that grows around a host tree and gradually replaces it, the Strangler Fig pattern incrementally replaces a legacy system by routing specific capabilities to new microservices one at a time. The legacy system continues handling everything else. Over time, the legacy system has fewer responsibilities until it can be decommissioned entirely. This avoids the risk of big-bang rewrites — which fail 70%+ of the time according to industry studies.
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 Singapore, SingaporeZTABS is a remote-first web development agency serving Singapore businesses — including full-stack development, progressive web apps, api development. We work with FinTech, Logistics, HealthTech companies in Singapore, Singapore 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 Singapore, SingaporeZTABS is a remote-first web design agency serving Singapore businesses — including ui/ux design, responsive design, custom interfaces. We work with FinTech, Logistics, HealthTech companies in Singapore, Singapore 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 Singapore, SingaporeZTABS is a remote-first AI development agency serving Singapore businesses — including llm integration & fine-tuning, ai agents & automation, rag & knowledge systems. We work with FinTech, Logistics, HealthTech companies in Singapore, Singapore 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 Singapore. Get a free consultation today.
