ZTABS modernizes legacy applications for Berlin enterprises — Java monolith decomposition into cloud-native microservices, SAP ECC to S/4HANA transition, COBOL banking system migration, and Betriebsrat-compliant modernization programs that preserve German works council agreements and employee data protections.
Germany runs on legacy software. The country's industrial strength — automotive, manufacturing, financial services, and public administration — was built on enterprise systems deployed in the 1990s and 2000s. Berlin businesses inherit this legacy: banks running COBOL on IBM mainframes, Mittelstand manufacturers operating SAP ECC systems approaching end of support, insurance companies processing claims through Java 6 monoliths, and government agencies delivering services through applications built on: technologies that no longer receive security updates. The urgency for modernization in Germany comes from multiple pressures: SAP ECC end of support (SAP's ERP Central Component reaches end of maintenance in 2027 — thousands of German businesses must transition to S/4HANA or alternative platforms; for companies that have customized SAP ECC extensively over 15-20 years: this transition is a major technology program), security compliance (BSI (Bundesamt für Sicherheit in der Informationstechnik) IT-Grundschutz requirements increasingly difficult to meet with: legacy systems running unsupported software; DSGVO requirements for: data protection by design — a concept fundamentally incompatible with: systems designed before data protection was a design principle), talent shortage (Germany faces 149,000 unfilled IT positions as of 2025. Finding developers for: COBOL, RPG, ABAP, or: legacy Java frameworks is: increasingly difficult and expensive. Junior developers: prefer modern technology stacks — recruiting for legacy maintenance: requires significant salary premiums without: attracting the best talent), digital transformation demands (Industry 4.0, IoT, AI, and: cloud-native architecture all require: modern systems that can: integrate with sensors, process real-time data streams, and: expose APIs for partner and customer connectivity — capabilities that legacy monoliths and mainframes cannot provide without: fundamental re-architecture), and competitive pressure (German companies competing against: digital-native competitors who build on: modern architecture from day one; the legacy technology debt: creating increasingly visible competitive disadvantages in: time-to-market, customer experience, and: operational agility). Germany's modernization context has unique characteristics: Betriebsrat considerations (German works councils have co-determination rights over: systems that monitor employee performance, changes to working conditions, and: technology implementations affecting employees; legacy modernization must: formally engage the Betriebsrat, address: data protection concerns, and: sometimes negotiate: Betriebsvereinbarungen — works council agreements — covering: how the modernized system handles employee data), thoroughness over speed (German enterprise culture values: careful planning, comprehensive documentation, and: risk mitigation over: rapid iteration; modernization programs must provide: detailed Pflichtenheft (requirements specification), thorough testing documentation, and: formal acceptance criteria), vendor relationships (German enterprises often have: deep, long-term vendor relationships — SAP, IBM, T-Systems, Siemens IT — that influence technology decisions; modernization must work within: these existing vendor ecosystems or: clearly demonstrate the value of change), and regulatory complexity (German industry regulations — BaFin for financial services, BfArM for medical devices, Bundesnetzagentur for energy — create: compliance requirements that legacy systems have evolved to meet over decades; modernization must: preserve regulatory compliance without: requiring re-certification).
Berlin legacy modernization demand spans financial services, public sector, technology companies, and manufacturing. Financial services: Berlin financial services legacy modernization needs: core banking (Berlin-based banks and fintech companies inheriting: core banking systems running on IBM z/OS mainframes with: COBOL programs processing: transactions, customer management, and: regulatory reporting; the systems reliable but: incapable of supporting: real-time APIs for open banking (PSD2), instant payments (SEPA Instant), and: mobile-first customer experiences), insurance claims processing (German insurers processing: claims through: Java monolith applications built in the early 2000s — running on: J2EE application servers with: complex EJB architectures; the systems: difficult to modify, slow to deploy updates (monthly release cycles), and: unable to integrate with: AI-based claims assessment, digital customer channels, or: IoT-connected insurance products), payment processing (legacy payment systems handling: SEPA transfers, direct debits, and: card processing — built before: instant payments, open banking, and: cryptocurrency became relevant; modernization enabling: real-time payment processing, PSD2 compliance, and: integration with modern payment methods), and BaFin regulatory reporting (regulatory reports generated through: manual data extraction from legacy systems, Excel-based compilation, and: manual submission; BaFin increasingly requiring: automated, real-time regulatory reporting that: legacy systems cannot provide without: significant data integration work). Public sector: Berlin government legacy modernization needs: citizen services (Berlin's Bürgerämter and Landesämter operating: applications built on: Oracle Forms, Lotus Notes, and: custom Visual Basic 6 applications; the Onlinezugangsgesetz (OZG) requiring: digital citizen services accessible online — the legacy systems: unable to deliver web-based or mobile services), document management (government document workflows running on: legacy ECM systems — FileNet, OpenText, or: custom document management; modernization to: cloud-based document management with: electronic signatures, workflow automation, and: archival compliance per GoBD regulations), and interoperability (German government entities exchanging data through: file-based interfaces and: custom point-to-point connections built over decades; modernization creating: standardized API-based data exchange aligned with: FIT-Connect and other national interoperability standards). Technology companies: Berlin tech companies with legacy challenges: startup-to-scale-up transition (Berlin startups that grew rapidly — their MVP codebases becoming: production systems handling: millions of users on: architectures never designed for: that scale; the "startup monolith" problem — a single Rails, Django, or: Express application that: served the first 10,000 users perfectly but: creates bottlenecks, deployment risks, and: developer productivity issues at: 1 million+ users), acquired technology (Berlin companies acquiring: other companies inheriting: their technology stacks; a Berlin fintech acquiring: a traditional financial services company inherits: their mainframe systems, compliance requirements, and: integration dependencies), and technical debt (Berlin companies accumulating: 5-10 years of technical debt — outdated dependencies, deprecated frameworks, missing tests, and: architecture decisions that: made sense initially but: now constrain the business). Manufacturing: Berlin-area manufacturing legacy modernization needs: MES modernization (Manufacturing Execution Systems running on: legacy platforms — Wonderware, SCADA systems from the 1990s, or: custom MES built on: outdated middleware; Industry 4.0 requiring: real-time production data, IoT sensor integration, and: AI-driven quality control that: legacy MES cannot support), ERP transition (SAP ECC to S/4HANA — the defining modernization challenge for German manufacturing; custom ABAP developments accumulated over 15-20 years must be: evaluated, migrated, or: replaced; the transition requiring: months of planning, testing, and: careful execution to: avoid production disruption), and PLM integration (Product Lifecycle Management systems — Siemens Teamcenter, PTC Windchill — running legacy versions requiring: upgrade or replacement; modern PLM needing: cloud deployment, AI-assisted design, and: digital twin capabilities).
Our Berlin legacy modernization follows a structured German engineering approach: thorough assessment, detailed planning, disciplined execution, and: comprehensive documentation. Assessment (Bestandsaufnahme): (1) Comprehensive analysis of the legacy landscape: application portfolio analysis (cataloging: every legacy application, its technology stack, business criticality, maintenance cost, and: risk level; the portfolio analysis producing: a prioritized modernization roadmap based on: business value and technical risk), code archaeology (for applications without: adequate documentation — automated code analysis revealing: actual system behavior, data flows, and: business rules; legacy systems in German enterprises often have: documentation written during original development that: no longer reflects: 20 years of modifications), integration topology (mapping: every data flow between: legacy systems, databases, file systems, and: external interfaces; German enterprise integration landscapes are: characteristically complex — 15-20 year old point-to-point connections between: dozens of systems creating: a web of dependencies that: must be understood before: any system is modified), and Betriebsrat assessment (for systems handling employee data: early engagement with the Betriebsrat to understand: existing Betriebsvereinbarungen, co-determination requirements, and: data protection commitments that: the modernized system must maintain — starting this conversation early prevents: delays during implementation). Strategy (Modernisierungskonzept): (1) Detailed modernization strategy documented as a formal Pflichtenheft: strangler fig pattern (gradually replacing: legacy system components with: modern equivalents; the legacy system: continues to operate while: individual functions are extracted, reimplemented, and: redirected to the modern system; particularly effective for: large monoliths where: a full rewrite is: too risky and too expensive), API wrapping (exposing: legacy system functionality through: modern REST or GraphQL APIs without: modifying the legacy code; the API layer: translating between: modern API contracts and: legacy communication protocols; providing: immediate integration capability while: planning longer-term modernization), microservices decomposition (breaking: monolithic applications into: independent microservices — each: owning its domain data, independently deployable, and: technology-independent; the decomposition following: domain-driven design principles to ensure: service boundaries align with: business domain boundaries, not arbitrary technical divisions), and data platform modernization (separating: data concerns from: application logic; legacy systems typically: combine application logic, data storage, and: reporting in a single monolith; modern architecture: extracting data into: a data platform enabling: analytics, AI, and: cross-system reporting without: querying production databases). Execution (Umsetzung): (1) Disciplined implementation with German engineering rigor: comprehensive test strategy (test coverage exceeding: 90% for modernized components — unit tests, integration tests, contract tests, and: end-to-end tests; for financial systems: mathematical verification that: calculations produce identical results in: legacy and modern implementations), parallel operation (Parallelbetrieb — legacy and modern systems processing: identical workloads with: automated comparison of results; the duration of parallel operation: proportional to business criticality — 3 months for internal systems, 6-12 months for: financial systems and: government systems processing citizen data), documentation (comprehensive documentation meeting German enterprise standards: architecture documentation (arc42 or similar framework), operations manual, deployment procedures, rollback plans, and: training materials — delivered in German), and knowledge transfer (structured handover to the client's IT team: workshops, pair programming, and: supervised independent operation before: the modernization team withdraws; the client's team: fully capable of operating and evolving: the modernized system independently).
Fintech / Financial Services
A Berlin fintech company (BaFin-licensed, EUR 45M annual revenue, 180 employees, 280,000 active users) needed to modernize its core platform. The problems: (1) Monolith limitations: the core platform was a Ruby on Rails monolith — originally built as an MVP in 2016 and continuously extended for 8 years. The codebase: 420,000 lines of Ruby, 85 database tables with: complex relationships, and: 180 background job types processing: financial transactions, compliance checks, and: notification delivery. Deployment: the entire monolith deployed as: a single unit — any change, even a UI text correction, required: deploying the entire application. Deploy frequency: reduced from daily (in the startup phase) to: weekly (due to: deployment risk). A failed deployment in the previous year: caused 4 hours of downtime affecting: all users, all services simultaneously. (2) Performance bottleneck: the monolith ran on: a single PostgreSQL database handling: user requests, transaction processing, reporting queries, and: compliance batch jobs simultaneously. During month-end processing: compliance reports locked database tables causing: user-facing response times to increase from: 200ms to 3-5 seconds. The company had: vertically scaled the database server 4 times in 2 years — approaching: the practical limit of vertical scaling. (3) Team productivity: 35 developers working on: the same codebase. Merge conflicts: averaging 12 per day. A change to the payment processing module: could unexpectedly break: the user notification system because: of tightly coupled code. Test suite: 45 minutes to run — developers skipping: full test runs before merging, leading to: production bugs discovered post-deployment. Developer onboarding: new engineers required: 3 months to understand the codebase sufficiently to make: independent contributions. (4) BaFin compliance: BaFin regulatory requirements demanded: clear separation of concerns — payment processing, customer data management, and: compliance functions should be: independently auditable, independently deployable, and: subject to: different change management procedures. The monolith: made this separation impossible — every deployment included: changes across all functional areas, complicating: regulatory audit trails.
We executed a 10-month strangler fig decomposition: (1) Domain analysis (month 1): domain-driven design workshop with: engineering leads, product managers, and: compliance officers. Identified: 8 bounded contexts: user management (registration, authentication, KYC), account management (account creation, balance tracking, statements), payment processing (incoming/outgoing payments, SEPA, instant payments), card services (virtual and physical cards, authorization, settlement), compliance (AML screening, transaction monitoring, regulatory reporting), notification (email, push, SMS, in-app), analytics (user behavior, business metrics, financial reporting), and integration (banking partner APIs, payment network connections). (2) Extraction priority: payment processing extracted first (highest BaFin scrutiny + highest performance demands) followed by: compliance (regulatory independence requirement), then: remaining services in order of business impact. (3) Payment service (months 2-4): the first service extracted from the monolith: domain extraction (payment processing code identified and: extracted from the monolith — 45,000 lines of Ruby refactored into: a new Elixir service; Elixir chosen for: its concurrency model ideal for: high-throughput payment processing; the new service: handling 5,000 transactions per second vs. the monolith's 800), database separation (payment data migrated from: the shared PostgreSQL database to: a dedicated payment database; the migration: executed with zero downtime using: CDC (Change Data Capture) replication during the transition period), API contract (the payment service exposing: a versioned REST API consumed by: the remaining monolith and: other future services; the API contract: formally documented and: tested through contract tests ensuring: consumer compatibility), and SEPA integration (SEPA payment processing moved from: batch files generated by the monolith to: real-time processing in the payment service — instant SEPA credit transfers supported for the first time). (4) Compliance service (months 4-6): AML and transaction monitoring (AML screening and: transaction monitoring extracted into: an independent service with: its own data store; the compliance team able to: modify screening rules without: monolith deployment; regulatory audit: simplified because: compliance changes tracked independently from: product feature changes), regulatory reporting (BaFin reports generated from: the compliance service's own data — not querying the production database; month-end reporting: no longer causing: performance degradation for users), and audit trail (every compliance decision: logged with: full context, timestamp, and: decision rationale; the audit trail: independently queryable for: BaFin examinations without: accessing production systems). (5) Remaining services (months 6-10): user management, account management, card services, notification, and analytics: each extracted following the same pattern — domain extraction, database separation, API contract, and: integration with existing services. The monolith: gradually shrinking as: functionality moved to services. By month 10: the monolith contained only: the web frontend and: API gateway routing to: the decomposed services. (6) Infrastructure: Kubernetes deployment on AWS Frankfurt (eu-central-1) — each service: independently deployable, auto-scaling, and: monitored. CI/CD pipeline: service-specific pipelines — a change to the payment service: deployed without: touching any other service. Monitoring: distributed tracing with Jaeger, centralized logging with: the ELK stack, and: service-specific dashboards. (7) Betriebsrat coordination: the works council was engaged during: the assessment phase. User management and: analytics services handling: employee data discussed with: the Betriebsrat. A Betriebsvereinbarung negotiated covering: employee data handling in the modernized system — specifying: what employee data is stored where, who has access, and: what automated decisions are made. The Betriebsvereinbarung: completed before the user management service was extracted — avoiding: implementation delays.
Deployment frequency: from weekly (entire monolith) to multiple daily deploys per service. The payment service: deployed 15 times in its first month — each deployment: affecting only payment processing, not the entire platform. Deployment failures: zero-downtime deployments through: rolling updates and: health check-based routing — no repeat of the 4-hour outage. Performance: payment processing throughput: 800 TPS (monolith) → 5,000 TPS (Elixir payment service). User-facing response time during month-end: 3-5 seconds (shared database contention) → 200ms (dedicated databases, no contention). The month-end compliance reporting: running against its own database without: any impact on user-facing services. Developer productivity: merge conflicts: reduced from 12/day to 2/day (services with smaller, focused codebases). Test suite: service-specific tests running in: 3-8 minutes (vs. 45 minutes for the monolith). Developer onboarding: new engineers productive in a single service within: 2-3 weeks (vs. 3 months for the monolith). The 35-person team: organized into: service-owning teams of 4-5 developers — each team: fully responsible for their service's development, deployment, and: operations. BaFin compliance: clean separation of compliance functions achieved. BaFin audit trail: independently accessible. Regulatory reporting: independently deployable and: independently modifiable. The BaFin examiner's feedback during the annual review: "significantly improved transparency and auditability of compliance functions." Cost impact: AWS infrastructure: EUR 18,000/month (vs. EUR 12,000/month for the monolith — increased by: the overhead of microservices infrastructure). However: developer productivity gains valued at: approximately EUR 400,000/year (faster development cycles, fewer production incidents, reduced onboarding time). The net annual benefit: significantly positive despite: increased infrastructure costs. Development cost: EUR 480,000 (10-month program). Annual value: EUR 400,000+ in developer productivity + immeasurable value from: deployment reliability, BaFin compliance improvement, and: platform scalability for business growth.
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.
Berlin legacy modernization options include: global SIs (Accenture, Capgemini, IBM — EUR 500,000-5,000,000, enterprise-grade but expensive and often lengthy), German SIs (T-Systems, Atos — EUR 300,000-2,000,000, strong German market knowledge), Berlin tech agencies (multiple agencies offering modernization — EUR 100,000-500,000, modern technology expertise but varying legacy experience), and freelance architects (EUR 50,000-200,000 for architecture and guidance, execution by client team). ZTABS delivers Berlin-specific legacy modernization with Betriebsrat-aware implementation, BaFin compliance expertise, and practical strangler fig execution at mid-market pricing.
Legacy app modernization in Berlin ranges from EUR 80,000 for focused module modernization to EUR 2,000,000+ for enterprise-wide legacy transformation. Fintech monolith decomposition (as in the case study): EUR 480,000. Java monolith to microservices: EUR 150,000-600,000. SAP ECC to S/4HANA (assessment + migration planning): EUR 80,000-200,000. Oracle Forms to web application: EUR 100,000-400,000. Legacy assessment and modernization roadmap: EUR 20,000-50,000.
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 Berlin businesses
Strangler fig — almost always. Full rewrites of large legacy systems fail at a rate exceeding 60% (industry data). The strangler fig pattern: extracts functionality incrementally, delivers value at each step, and allows course correction. Each extracted service is validated before the next extraction begins. The legacy system continues operating throughout — no big-bang cutover risk. Full rewrites are only appropriate for small, well-understood systems where the legacy codebase is genuinely unmaintainable.
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 Berlin, GermanyZTABS is a remote-first web development agency serving Berlin businesses — including full-stack development, progressive web apps, api development. We work with FinTech, E-commerce, Mobility companies in Berlin, Germany 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 Berlin, GermanyZTABS is a remote-first web design agency serving Berlin businesses — including ui/ux design, responsive design, custom interfaces. We work with FinTech, E-commerce, Mobility companies in Berlin, Germany 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 Berlin, GermanyZTABS is a remote-first AI development agency serving Berlin businesses — including llm integration & fine-tuning, ai agents & automation, rag & knowledge systems. We work with FinTech, E-commerce, Mobility companies in Berlin, Germany 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 Berlin. Get a free consultation today.
