ZTABS modernises legacy applications for Zurich enterprises — banking platform upgrades, pharmaceutical system migrations, and enterprise application transformation for Swiss private banks, pharma companies, and multinational headquarters with zero data loss and Swiss compliance.
Legacy application modernisation in Zurich addresses the technology debt accumulated by Swiss enterprises that have invested heavily in systems over decades — private banks running 15-year-old Avaloq installations with thousands of custom extensions, pharmaceutical companies operating validated manufacturing systems that cannot be easily replaced without Swissmedic re-validation, and corporate headquarters maintaining SAP ECC installations that must migrate to S/4HANA before end-of-support in 2027. The modernisation challenge in Zurich is shaped by industry-specific constraints. Swiss banking: private banks have deep customisation built on their core banking platforms (Avaloq, Temenos). A typical Zurich private bank's Avaloq installation includes: 200-500 custom reports, 50-100 custom workflows, dozens of custom interfaces to custodians, market data providers, and regulatory systems, and years of configuration reflecting the bank's specific product offerings, fee structures, and operational processes. This customisation represents millions of francs in investment and encodes institutional knowledge that cannot be recreated quickly. Modernisation must preserve this investment while moving to current technology — a complete replacement would take years, cost tens of millions, and risk operational disruption that a FINMA-regulated institution cannot accept. Swiss pharmaceuticals: pharmaceutical manufacturing and quality systems are validated under GxP requirements (Good Manufacturing Practice, Good Laboratory Practice). A manufacturing execution system (MES) or laboratory information management system (LIMS) has been through formal validation — documented testing proving that the system performs as intended. Modernising or replacing these systems requires re-validation — a process that can take 6-12 months and involves substantial documentation. This validation overhead makes pharmaceutical legacy modernisation slower and more expensive than in unregulated industries, creating a tendency to defer modernisation until the system becomes unmaintainable. SAP S/4HANA migration: Zurich's large enterprises face the SAP ECC to S/4HANA migration — arguably the largest enterprise technology modernisation programme in Swiss corporate history. SAP's end of mainstream maintenance for ECC (2027, with extended maintenance available at premium cost until 2030) creates a hard deadline. The migration is complex: S/4HANA requires a different database (SAP HANA), has a different data model (simplified tables, new business processes), and deprecates some ECC functionality. Custom ABAP code must be analysed and adapted. The Swiss-specific requirements (Swiss localisation, cantonal tax, Swiss payroll) must be verified on S/4HANA. Modernisation approach options range from minimal intervention to complete replacement. Re-platform: moving the existing application to modern infrastructure (cloud hosting, containerisation) without changing the application code — the fastest, lowest-risk approach but one that does not address application-level technical debt. Re-factor: restructuring the application code to improve maintainability, performance, and extensibility — typically involving breaking monolithic applications into services, updating frameworks and libraries, and improving the codebase without changing business logic. Re-architect: fundamentally redesigning the application architecture — moving from monolithic to microservices, from synchronous to event-driven, from server-rendered to API-first — while preserving business logic and data. This provides the most long-term benefit but carries the highest risk and cost. Replace: retiring the legacy application and implementing a new system — sometimes the right choice when the legacy application is beyond economic modernisation, but carrying the risk of data migration, business process disruption, and institutional knowledge loss.
Zurich's legacy modernisation demand concentrates across four sectors with urgent modernisation timelines. Banking platform modernisation represents the highest-stakes engagement. Zurich private banks face: Avaloq version currency (banks running Avaloq versions 3-5+ years behind current face increasing compatibility issues with integrations, missing security patches, and inability to use new Avaloq features; upgrading requires testing thousands of custom extensions against the new version), core banking migration (some banks on legacy core platforms (Olympic, Finnova, or very old Temenos installations) face end-of-vendor-support — requiring migration to current platforms (Avaloq, Temenos Transact, or new entrants like Thought Machine, Mambu)), client-facing digital channels (internet banking and mobile banking built on legacy middleware (Java applets, Flash-era web technology, or early mobile frameworks) — requiring complete rebuild to meet current client expectations and security standards), and regulatory reporting systems (systems built to meet regulatory requirements from 5-10 years ago that have been patched for each new requirement — resulting in fragile, poorly documented reporting infrastructure that creates compliance risk). Pharmaceutical system modernisation constitutes the second pillar. Zurich pharma companies face: MES/LIMS modernisation (manufacturing execution systems and laboratory information management systems running on deprecated operating systems (Windows Server 2008/2012), deprecated databases (Oracle 11g, SQL Server 2012), or custom-built applications that the original developers have left — systems that must be modernised while maintaining GxP validation status), clinical trial system migration (electronic data capture (EDC), trial management (CTMS), and safety reporting systems that have accumulated years of clinical data — migration to current platforms (Medidata Rave, Oracle Arium, Veeva Vault CDMS) while preserving data integrity and audit trails), and regulatory submission systems (eCTD publishing, document management, and submission tracking systems that need modernisation to handle current regulatory requirements across Swissmedic, EMA, and FDA). SAP S/4HANA migration forms the third category. Zurich enterprises face: migration assessment (understanding the scope of their ECC installation — custom code, custom objects, data volumes, integrations — and the impact of S/4HANA changes on their specific configuration), migration planning (brownfield (in-place conversion), greenfield (new implementation), or selective data transition — each approach with different risk, cost, and timeline profiles), Swiss localisation verification (ensuring that Swiss-specific functionality — VAT, payroll, customs, cantonal tax — works correctly on S/4HANA), and custom code remediation (analysing and adapting custom ABAP code for S/4HANA compatibility — syntax changes, deprecated functions, and new programming models (RAP, CDS views, Fiori)). Corporate legacy application modernisation adds the fourth dimension: intranet and collaboration platforms (migrating from legacy intranets (SharePoint 2013, Lotus Notes) to modern platforms), workflow and document management (legacy BPM and DMS systems that have accumulated years of institutional process knowledge), and departmental applications (custom applications built over years for specific business functions — often in VBA, Access, or classic ASP — that need modernisation or replacement).
Our Zurich legacy modernisation methodology minimises risk while delivering measurable improvement. Assessment quantifies the modernisation challenge. Application assessment: we evaluate the legacy application across six dimensions: business value (how critical is this application to business operations? What revenue or compliance function depends on it?), technical health (technology currency, code quality, security posture, performance characteristics, and maintainability), data value (what data does the application hold, how valuable is it, and how complex would migration be?), integration complexity (how many systems depend on this application, and how deeply are they coupled?), team knowledge (who understands this application, and what is the knowledge concentration risk?), and modernisation options (what approaches are technically feasible and economically justified?). Risk assessment: for each modernisation option, we evaluate: data risk (the risk of data loss or corruption during migration — the most critical risk for any modernisation), operational risk (the risk of business disruption during the transition — particularly important for 24/7 banking systems and GxP-validated pharmaceutical systems), compliance risk (the risk that modernisation affects regulatory compliance — FINMA audit trail requirements, GxP validation status, regulatory reporting capability), and vendor risk (the risk of dependency on new technology vendors — licence terms, vendor viability, lock-in potential). Strangler fig pattern for incremental modernisation. For complex legacy applications where replacement is too risky and re-platforming is insufficient, we use the strangler fig pattern — gradually replacing legacy functionality with modern components while the legacy system continues to operate. New functionality is built in the modern stack (new features implemented in the modern application rather than extending the legacy system). Legacy functionality is incrementally migrated (existing features rebuilt in the modern stack, one at a time, with the legacy system as fallback). Integration layer routes between legacy and modern (an API gateway or integration layer directs each request to either the legacy system or the modern component — traffic shifts from legacy to modern as components are migrated). Legacy system is retired when all functionality has been migrated (the legacy system is decommissioned only when the modern system has proven itself in production for every function). This approach: eliminates big-bang risk (the organisation is never dependent on a single go-live event — each component migration is a small, reversible step), maintains operational continuity (the legacy system continues to operate throughout — if a modern component has issues, traffic reverts to the legacy system), and delivers value incrementally (the organisation benefits from each migrated component immediately, rather than waiting 18-24 months for a complete replacement). Data migration is treated as the highest-risk activity. Data migration strategy: we plan data migration as a distinct workstream — not an afterthought. Methods: data profiling (understanding data quality, completeness, and consistency in the legacy system before migration — identifying issues that must be addressed), data mapping (defining the transformation from legacy data model to target data model — field mapping, data type conversion, lookup table migration, and business rule application), migration scripting (automated, repeatable migration scripts — not manual data manipulation — enabling multiple test migrations before the production cutover), validation (automated validation of migrated data — row counts, checksums, referential integrity checks, business rule validation — ensuring the migrated data is complete and correct), and fallback (the ability to revert to the legacy system if production migration reveals issues — maintaining the legacy system in read-only mode for a defined period after cutover).
Private Banking / Digital Client Channels
A Zurich private bank (CHF 16 billion AUM, 2,200 clients) operated an internet banking platform built in 2012 on a Java/JSP stack with jQuery frontend. The platform provided: portfolio viewing (positions, transactions, performance), document access (portfolio reports, tax statements, contract notes), secure messaging with the relationship manager, and basic payment initiation (domestic and international transfers). The platform was functionally adequate but technologically obsolete: security vulnerabilities (the Java framework version had known CVEs that required mitigation through WAF rules rather than patching — the codebase was too fragile for framework upgrades), performance issues (page load times of 4-8 seconds — acceptable in 2012, frustrating in 2024 when clients compared the experience to their retail banking apps), mobile incompatibility (the JSP-rendered interface was not responsive — clients on tablets and phones received a desktop experience that was difficult to navigate), no API layer (the internet banking connected directly to Avaloq through custom database procedures — making it impossible to build a mobile app, connect a client portal, or integrate third-party services without duplicating the database integration), and developer dependency (the original development team had left the bank — only 2 current developers partially understood the codebase, and they spent 80% of their time on maintenance rather than feature development). FINMA's most recent supervisory review noted the platform's technology currency as a concern — not a formal requirement to modernise but a clear signal that the bank should address the issue. The Head of Digital wanted: a modern, mobile-responsive platform, API-first architecture enabling future mobile app development, current security standards, and the ability to add new features (AI-powered portfolio insights, document AI, video banking) without the constraints of the legacy codebase.
We modernised the internet banking using the strangler fig approach over 16 weeks — replacing the legacy platform incrementally rather than as a big-bang migration. Architecture design (weeks 1-3): the target architecture: Next.js frontend (server-side rendered for performance, React components for interactive portfolio views, TypeScript for code quality), API layer (Node.js/TypeScript BFF — Backend for Frontend — providing a clean API that the frontend consumed; the BFF connected to Avaloq through Avaloq's API framework, replacing the legacy database procedures), and authentication (migrated from the legacy session-based auth to Auth0 with MFA — maintaining the bank's existing strong authentication but on a modern, maintainable platform). The strangler pattern: we deployed the new frontend alongside the legacy system behind an Nginx reverse proxy. Initially, 100% of traffic went to the legacy system. As we rebuilt each functional area in the new stack, the proxy routed those specific URLs to the new system while the remaining URLs continued to serve from the legacy system. Phase 1 (weeks 2-6) — portfolio and documents: rebuilt the core read-only functions first — portfolio positions, transaction history, performance, and document access. These functions were highest-value (used daily by clients), lowest-risk (read-only — no transactions), and provided immediate visual impact (clients saw the modern, fast, responsive interface immediately). The new portfolio view: loaded in 1.2 seconds (from 6+ seconds), was fully responsive (optimised for desktop, tablet, and phone), included interactive charts (portfolio allocation, performance over time, currency exposure), and supported German, French, Italian, and English (the legacy system supported only German and English). Phase 2 (weeks 4-10) — messaging and communication: rebuilt secure messaging with modern capabilities: threaded conversations (the legacy system had flat email-like messaging — the new system provided WhatsApp-style threaded conversations with the RM), document sharing (clients could share documents with their RM directly in the conversation — the legacy system required separate email), read receipts and typing indicators (the modern messaging experience clients expected), and notification (push notifications for new messages — the legacy system required the client to log in and check). Phase 3 (weeks 6-14) — payments and transactions: the highest-risk migration — payment initiation involved writing to Avaloq (creating payment instructions) rather than just reading data. Domestic payments (CHF transfers between Swiss banks — SIC/SIX Interbank Clearing integration via Avaloq), international payments (SWIFT transfers — correspondent banking routing, sanctions screening integration), and standing orders and scheduled payments. Each payment type was migrated individually: domestic payments first (highest volume, best understood), then international payments (more complex, lower volume), then scheduled payments. For each type: the new system was deployed in parallel — the client could initiate payments through both the new and legacy systems during the transition. After 2 weeks of parallel operation with zero discrepancies, the legacy payment route was disabled. Phase 4 (weeks 12-16) — legacy decommission and new capabilities: once all functionality was running on the new stack: the legacy system was placed in read-only mode (accessible for 60 days as a fallback — if any issue emerged, traffic could be reverted), then decommissioned entirely. New capabilities deployed immediately after legacy decommission: AI portfolio insights (a GPT-4o-powered feature — accessible via Azure Switzerland North — that answered client questions about their portfolio: "How has my tech allocation performed versus the benchmark?" "What are my largest currency exposures?" "When do my fixed income positions mature?" — answered from real-time Avaloq data), document AI (clients could photograph documents (tax forms, contracts) and share them with their RM with AI-extracted key data — simplifying document-intensive processes like tax reporting and account updates), and mobile-optimised experience (while not a native mobile app, the responsive design provided a mobile-grade experience — with biometric login via the mobile browser, optimised touch interactions, and mobile-appropriate layouts).
The modernised internet banking deployed incrementally over 16 weeks with zero downtime and zero data issues. Performance: page load time: 1.2 seconds average (from 5.8 seconds — 79% improvement). Lighthouse performance score: 92 (the legacy system scored 28). Mobile experience: fully responsive — mobile usage increased from 12% (clients attempting to use the non-responsive legacy system on phones) to 48% of sessions. Client satisfaction: internet banking satisfaction: 4.5/5 (from 3.1/5 — survey conducted 3 months post-completion). The most cited improvements: speed ("It actually loads now"), mobile access ("I can check my portfolio on my phone"), and the portfolio charts ("I can finally see my allocation and performance visually"). AI portfolio insights: 38% of clients used the AI insights feature within the first 3 months. Average 2.3 queries per client per week. The most common queries: performance attribution, upcoming maturities, and currency exposure. Relationship managers reported that clients came to meetings better informed — the meeting time was spent on advice rather than information delivery. Security: the modernised platform addressed all security concerns noted in FINMA's supervisory review. Current framework versions, modern authentication (Auth0 with MFA), encrypted API communication, and regular security scanning. The bank's next FINMA review noted the improvement positively. Developer productivity: the new codebase (TypeScript, Next.js, well-documented API layer) was maintainable by the bank's development team. Feature development velocity increased approximately 3x — the team could build new features in the modern stack in days rather than weeks of navigating the legacy codebase. The 2 developers who had been spending 80% of time on legacy maintenance now spent 80% on feature development. Operational cost: the legacy Java application servers (3 physical servers in the bank's data centre) were replaced by Vercel hosting (Next.js frontend) and a small ECS cluster (API layer) — reducing infrastructure cost from CHF 8,000/month to CHF 2,200/month. Financial impact: client experience improvement: estimated CHF 1.4 million in client retention (clients who had considered moving to banks with better digital experience), infrastructure cost reduction: CHF 69,600 annually, developer productivity: estimated CHF 180,000 annually (developer capacity redirected from maintenance to features), and AI insights engagement: contributing to deeper client relationships and higher engagement — difficult to quantify but valued by the bank's leadership as a competitive differentiator. Implementation cost: CHF 380,000. First-year ROI: 4.3x on quantifiable benefits, with significant unquantified strategic value. Ongoing cost: CHF 4,500/month (hosting, Auth0, Azure for AI features).
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.
Zurich's legacy modernisation landscape includes banking technology consultancies, global systems integrators, and platform vendors. Banking technology consultancies (Synpulse, zeb, Capco) advise on banking system modernisation but typically recommend platform replacements (which carry higher risk and cost) rather than incremental modernisation approaches. Global systems integrators (Accenture, TCS, Infosys) execute large-scale modernisation programmes but at enterprise scale and cost — their minimum engagement size often exceeds what mid-sized Swiss private banks require. Platform vendors (Avaloq, Temenos) offer upgrade paths within their own platforms but these paths address only the core banking component — not the custom applications, client channels, and integrations that represent the majority of the modernisation challenge. Offshore modernisation teams lack the Swiss banking domain knowledge, FINMA regulatory understanding, and Swiss data sovereignty awareness required for banking system modernisation. ZTABS operates at CHF 200-300/hr with incremental modernisation expertise (strangler fig pattern — lower risk than big-bang replacement), Swiss private banking domain knowledge, FINMA-aligned architecture, and modern technology stack (Next.js, TypeScript, API-first) combined with legacy system integration capability.
Legacy modernisation in Zurich ranges by system complexity and modernisation approach. Internet banking modernisation (strangler fig, 12-18 weeks): CHF 250,000-500,000. Core banking upgrade support (Avaloq/Temenos version upgrade, 10-16 weeks): CHF 200,000-450,000. SAP S/4HANA migration assessment and planning (4-8 weeks): CHF 80,000-180,000. Pharmaceutical system modernisation (GxP-validated, 16-24 weeks): CHF 350,000-700,000. API layer development (legacy system API enablement, 8-12 weeks): CHF 150,000-300,000. Data migration (per legacy system): CHF 30,000-80,000. Custom code analysis and remediation (per 100K lines): CHF 25,000-50,000. Ongoing modernisation support: CHF 5,000-15,000 per month.
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 Zurich businesses
Instead of replacing the legacy system all at once (big-bang — high risk), we build the new system alongside the legacy system and migrate functionality incrementally. Each component is rebuilt, tested, and deployed independently. The legacy system is only decommissioned when all functionality runs on the new platform.
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 Zurich, SwitzerlandZTABS is a remote-first web development agency serving Zurich businesses — including full-stack development, progressive web apps, api development. We work with FinTech & Banking, Crypto & Blockchain, Pharma & MedTech companies in Zurich, Switzerland 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 Zurich, SwitzerlandZTABS is a remote-first web design agency serving Zurich businesses — including ui/ux design, responsive design, custom interfaces. We work with FinTech & Banking, Crypto & Blockchain, Pharma & MedTech companies in Zurich, Switzerland 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 Zurich, SwitzerlandZTABS is a remote-first AI development agency serving Zurich businesses — including llm integration & fine-tuning, ai agents & automation, rag & knowledge systems. We work with FinTech & Banking, Crypto & Blockchain, Pharma & MedTech companies in Zurich, Switzerland 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 Zurich. Get a free consultation today.
