ZTABS modernizes legacy applications for Munich enterprises — migrating COBOL mainframes, SAP R/3 customisations, and legacy manufacturing systems to cloud-native with zero-downtime transitions and BaFin/BSI compliance.
Legacy application modernization in Munich addresses the technology debt of Germany's industrial heartland — a city where BMW's manufacturing execution systems were designed before the fall of the Berlin Wall, where Allianz processes insurance across 70 countries through mainframes from the 1980s, and where Mittelstand hidden champions run mission-critical production on systems that their vendors no longer support. Munich's legacy challenge reflects Germany's unique position: the country's engineering excellence built world-class products on technology that was state-of-the-art when deployed but has now become a constraint on the digital transformation that German industry needs to maintain global competitiveness. SAP R/3 legacy — Germany's defining legacy challenge. Germany is SAP's home market, and virtually every major German company implemented SAP R/3 in the 1990s-2000s. These implementations were heavily customised for German business practices: Handelsgesetzbuch (HGB) accounting standards, German payroll (one of the world's most complex — church tax, solidarity surcharge, Kurzarbeit calculations), and Mittelstand-specific processes. These customisations — often thousands of Z-programmes and customer exits — now block migration to SAP S/4HANA. SAP's 2027 end of mainstream maintenance for ECC 6.0 creates a hard deadline, but the customisation debt makes migration far more complex than a standard upgrade. BaFin regulatory pressure — BaFin supervises Munich's insurance and financial services companies with increasing attention to IT risk. BaFin's MaRisk (Mindestanforderungen an das Risikomanagement) and BAIT (Bankaufsichtliche Anforderungen an die IT) establish IT governance requirements that legacy systems struggle to meet: comprehensive IT asset management, regular vulnerability assessment and patching, and change management with adequate testing. BSI KRITIS requirements — Germany's Bundesamt fur Sicherheit in der Informationstechnik designates critical infrastructure operators (KRITIS) who must meet BSI security standards. Munich's energy, insurance, and telecommunications companies classified as KRITIS face legacy modernization pressure from BSI requirements that their ageing systems cannot satisfy. German Betriebsrat requirements — similar to French CSE requirements, German works councils (Betriebsrat) have co-determination rights (Mitbestimmung) on technology changes that affect working conditions. Legacy modernization programmes must include Betriebsrat consultation, particularly regarding: changes to employee roles and skills, monitoring and performance measurement implications, and data protection aspects of new systems.
Munich's legacy modernization demand spans four sectors. Automotive — Munich's OEMs and Tier-1 suppliers. BMW: operating legacy manufacturing execution systems (MES), product lifecycle management (PLM), and dealer management systems (DMS) across 31 production plants. BMW's MES for older production lines runs on platforms from the early 2000s — capable of producing world-class vehicles but constraining Industry 4.0 integration, digital twin implementation, and real-time quality analytics. BMW's SAP R/3 implementation (one of the largest in the automotive industry) is heavily customised for BMW's production planning, procurement, and financial processes — migration to S/4HANA is a multi-year programme affecting every BMW business function. Tier-1 suppliers: Continental, ZF, Knorr-Bremse — running legacy ERP (SAP R/3 with deep customisations), legacy PLM (Windchill, Teamcenter on older versions), and legacy quality management systems (SAP QM with customised inspection plans dating back decades). The automotive supply chain's legacy is interconnected: BMW's legacy EDI requirements force suppliers to maintain legacy interfaces, and supplier legacy systems constrain their ability to implement Industry 4.0 connectivity. Insurance — Munich's global insurance cluster. Allianz (EUR 152.7B revenue): operating legacy policy administration across 70+ countries. German domestic operations on the oldest platforms — COBOL-based life insurance administration dating to the 1980s, P&C systems from the 1990s. Allianz's modernization is complicated by: multi-country legacy (each acquired company bringing its own systems), Solvency II reporting dependencies (regulatory reporting built on top of legacy data structures), and scale (hundreds of millions of policies globally). Munich Re (EUR 67.4B revenue): legacy reinsurance administration — treaty management, claims, and accounting systems. Munich Re's legacy is less visible than primary insurers' (fewer customer-facing systems) but equally constraining for data analytics and regulatory reporting. ERGO, Versicherungskammer Bayern, HUK-Coburg — each with legacy policy administration, claims, and actuarial systems requiring modernization to support digital distribution and data-driven pricing. Siemens — Munich's industrial technology conglomerate. Siemens (EUR 77.8B revenue): legacy across every division — industrial automation (legacy SCADA and DCS), building technology (legacy building management systems), mobility (legacy railway signalling and control), and Siemens Healthineers (legacy medical device software). Siemens's internal IT also runs on legacy SAP R/3 with extensive customisations. Siemens's challenge is both internal legacy (their own IT systems) and external legacy (their customers' legacy Siemens installations that constrain product development). Mittelstand — hidden champion legacy. Munich-region Mittelstand companies (EUR 50M-2B revenue) typically implemented SAP R/3 or SAP Business One in the late 1990s-2000s, with varying degrees of customisation. Many now face: SAP ECC end of maintenance (2027) forcing S/4HANA migration or platform change, legacy MES from equipment vendors (proprietary systems tied to specific manufacturing equipment), legacy quality management (QM systems built for ISO 9001 compliance that have been continuously modified but never re-architected), and legacy customer/supplier portals (built in the 2000s, now unable to meet modern UX expectations or mobile requirements).
Our Munich legacy modernization methodology addresses German regulatory requirements, Betriebsrat co-determination, and the SAP R/3 migration challenge. Phase 1 — Legacy Assessment with German Regulatory Mapping (weeks 1-3): comprehensive inventory including SAP customisation assessment, BaFin/BSI classification, and Betriebsrat impact analysis. Phase 2 — German-Compliant Target Architecture (weeks 3-5): modern architecture meeting BSI standards, on German-sovereign infrastructure where required. Phase 3 — Strangler Fig Migration with Betriebsrat Alignment (weeks 5-20+): progressive replacement with parallel running, incorporating Betriebsrat consultation timelines. Phase 4 — Progressive Cutover (weeks 16-30+).
Automotive / Manufacturing / Legacy Modernization / Munich
A Munich-headquartered automotive Tier-1 supplier (EUR 3.8B revenue, manufacturing braking systems, steering components, and chassis electronics, 16,000 employees, operating 8 production plants across Germany, Czech Republic, China, and Mexico) needed to modernize their legacy technology estate to support electrification transition and Industry 4.0 implementation. The company's technology stack reflected 25 years of growth through acquisition and organic expansion. Legacy SAP R/3 (deployed 1999): SAP ECC 6.0 with 4,200 custom ABAP programmes (Z-programmes), 380 custom transactions, 240 user exits, and 85 BAdI implementations. The customisations covered: German production planning (PP) modifications for automotive JIT/JIS (just-in-time/just-in-sequence) delivery to BMW, Audi, and Mercedes assembly lines, quality management (QM) customisations implementing automotive IATF 16949 requirements with customer-specific quality gates, financial accounting customised for German HGB, IFRS parallel accounting, and transfer pricing across 4 countries, and human resources (HR) with German payroll (Lohnbuchhaltung) customisations including Kurzarbeit, church tax, and Berufsgenossenschaft contributions. SAP had announced end of mainstream maintenance for ECC 6.0 by 2027 — the company needed to either migrate to S/4HANA (addressing all 4,200 customisations) or replace SAP entirely. Legacy MES (deployed 2003-2008): three different MES platforms across 8 plants — the German plants running a customised Siemens SIMATIC IT installation, Czech plant on Wonderware (now AVEVA), and Chinese/Mexican plants on locally developed MES solutions. These MES systems could not: provide cross-plant production visibility (no unified view of production across 8 plants), support real-time quality analytics (quality data batch-processed nightly), integrate with OEM digital platforms (BMW's Catena-X supply chain data exchange requiring modern API connectivity that legacy MES lacked), or support electric vehicle component production (EV braking and steering systems requiring different manufacturing processes, tolerances, and testing protocols that legacy MES configurations could not accommodate). Core challenges: (1) SAP 2027 deadline — with 4,200 custom programmes, migration to S/4HANA was not a simple upgrade. Analysis showed: 1,800 Z-programmes required complete rewriting (using deprecated features, incompatible data types, or obsolete interfaces), 1,400 Z-programmes could be adapted (logic preserved, interfaces updated), 600 Z-programmes were replaceable by standard S/4HANA functionality (customisations that had been needed in R/3 but were now standard), and 400 Z-programmes were dead code (never executed in production — built for projects that were abandoned or superseded). The complexity of German payroll customisation alone represented 6 months of migration effort — Kurzarbeit calculations, Berufsgenossenschaft (BG) industry-specific contribution rates, and Arbeitnehmer-Sparzulage (employee savings bonuses) all requiring careful reimplementation. (2) OEM connectivity — BMW and other OEM customers were implementing Catena-X (the automotive industry data exchange standard). The company needed to: share quality data in real-time with OEM assembly plants (currently batch-reported 24 hours after production), provide supply chain visibility (current stock, production schedule, delivery forecast accessible through API), and support digital product passport (EU regulation requiring traceability data for each component — legacy systems could not provide component-level traceability across the full value chain). Without Catena-X connectivity, the company risked losing OEM nominations — BMW had indicated that Catena-X participation would become a supplier requirement. (3) EV transition — the company was transitioning 40 percent of production capacity from ICE (internal combustion engine) to EV components within 5 years. EV braking systems, electronic power steering, and battery disconnect units required different: manufacturing processes (clean room assembly for electronic components versus traditional machining), quality requirements (electronic testing protocols versus mechanical testing), and traceability requirements (complete component genealogy for safety-critical electronic systems — IATF 16949 plus ISO 26262 functional safety). Legacy MES could not support these new manufacturing paradigms without extensive modification. (4) Betriebsrat requirements — the company's German works council (Betriebsrat) required formal consultation on the modernization programme, particularly regarding: SAP HR module changes (affecting payroll processing and employee data handling), MES changes (affecting production worker interfaces and performance monitoring), Industry 4.0 data collection (concerns about employee monitoring through increased sensor data), and potential skill changes (production workers needing training for new MES interfaces). The Betriebsrat had negotiated a Betriebsvereinbarung (works agreement) on technology changes, requiring 3-month consultation periods for significant system replacements.
We delivered a comprehensive SAP and MES modernization over 44 weeks — migrating SAP R/3 to S/4HANA, unifying MES across 8 plants, and enabling Catena-X connectivity. (1) SAP S/4HANA migration with custom code remediation. Custom code analysis: all 4,200 Z-programmes analysed using SAP's Custom Code Migration Worklist and our proprietary analysis tooling. Classification: 1,800 rewrite, 1,400 adapt, 600 replace with standard, 400 decommission. Rewrite priority: German payroll (Lohnbuchhaltung) customisations migrated first — the most complex and highest-risk area. Each payroll calculation validated against the Lohnsteuer-Handbuch (wage tax handbook) and BG contribution tables. Production planning customisations reimplemented for S/4HANA's embedded PP/DS (Production Planning and Detailed Scheduling) — automotive JIT/JIS delivery sequences preserved and enhanced. Quality management migrated to S/4HANA embedded QM with IATF 16949 compliance maintained — customer-specific quality gates reconfigured rather than custom-coded. Financial accounting: HGB/IFRS parallel accounting leveraging S/4HANA's universal journal — replacing custom parallel ledger implementations that were the source of quarter-end closing delays. Custom code reduction: 4,200 Z-programmes reduced to 1,400 in S/4HANA — a 67 percent reduction in custom code. Standard S/4HANA functionality replacing custom solutions wherever possible, reducing future upgrade complexity. (2) Unified MES: one platform across 8 plants. Modern MES: replacing 3 legacy MES platforms with a single cloud-native MES built on: containerised microservices (Kubernetes on Azure Germany — meeting German data sovereignty requirements), real-time production data streaming (Apache Kafka processing sensor data from all 8 plants), unified quality management (real-time SPC — Statistical Process Control — replacing nightly batch analysis), and cross-plant production visibility (a single dashboard showing production status, quality metrics, and OEE across all 8 plants for the first time). EV manufacturing support: the new MES designed for both ICE and EV component production — clean room manufacturing protocols, electronic testing integration, and ISO 26262 functional safety traceability built into the platform architecture rather than retrofitted onto legacy. Plant-specific migration: each plant migrated individually over 6-week cycles — German plants first (highest volume, highest complexity), then Czech, then Chinese and Mexican. (3) Catena-X integration: automotive supply chain connectivity. API-based data exchange: implementing Catena-X connectors enabling: real-time quality data sharing with BMW, Audi, and Mercedes assembly plants (quality measurements transmitted within minutes of production versus 24-hour batch reporting), supply chain visibility (current inventory, production schedule, and delivery forecast accessible through standardised Catena-X APIs), digital product passport (component-level traceability from raw material to finished part — meeting upcoming EU regulation requirements), and demand-capacity coordination (OEM demand signals triggering automatic production scheduling adjustments). The company becoming one of the first Tier-1 suppliers to achieve full Catena-X operational integration — creating competitive advantage in OEM nomination discussions. (4) Betriebsrat-aligned implementation. Works council engagement: formal Betriebsrat consultation initiated at programme start, including: detailed impact assessment for each employee group, training programme for production workers (new MES interfaces) and office workers (S/4HANA), data protection assessment (Datenschutzfolgenabschaetzung) for new sensor data collection, and explicit commitment that Industry 4.0 sensor data would not be used for individual employee performance monitoring. The Betriebsvereinbarung was amended to include specific provisions for the modernization programme — Betriebsrat approval secured through transparent engagement and genuine commitment to employee protection. Training: 1,200 employees trained on new systems — S/4HANA training for 400 office workers, MES training for 800 production workers. Training conducted during paid working hours per Betriebsrat agreement.
Results over 12 months post-modernization. SAP S/4HANA: 4,200 custom programmes reduced to 1,400 (67 percent custom code reduction). Quarter-end financial close: from 12 days to 5 days (58 percent reduction through universal journal and eliminated reconciliation between parallel ledgers). German payroll: processing time from 5 days to 1 day (all customisations validated against Lohnsteuer-Handbuch). Production planning: JIT/JIS delivery compliance maintained at 99.7 percent through migration (no degradation). S/4HANA positioned the company for future upgrades without the custom code burden that had made R/3 upgrades impossible. Manufacturing (MES): cross-plant visibility achieved for the first time — production, quality, and OEE visible across all 8 plants on a single dashboard. Real-time quality: SPC replacing nightly batch analysis — quality deviations detected and addressed during production shift rather than next-day. OEE improvement: 4.2 percent average across plants (from 78.4 percent to 82.6 percent — representing EUR 16M in additional production capacity at current margins). EV production: new MES supporting clean room assembly, electronic testing, and ISO 26262 traceability for EV component manufacturing lines launched successfully. Catena-X: first Tier-1 supplier in company's peer group to achieve full Catena-X operational integration. Quality data transmission: from 24-hour batch to real-time (BMW receiving quality measurements within minutes of production). Supply chain visibility: OEMs accessing real-time inventory and production schedule. Competitive impact: Catena-X readiness cited as a factor in winning 2 new BMW nominations (estimated EUR 180M lifecycle revenue). Cost: legacy elimination: SAP R/3 licence and maintenance EUR 2.8M annually, legacy MES maintenance EUR 1.4M annually — EUR 4.2M total eliminated. Modern platform: S/4HANA cloud EUR 1.8M annually, MES platform EUR 600K annually — EUR 2.4M total. Annual infrastructure saving: EUR 1.8M. OEE improvement value: EUR 16M additional production capacity annually. Total modernization investment: EUR 6.4M over 44 weeks. Annual value (infrastructure saving + OEE improvement): EUR 17.8M. Payback: 5 months (driven primarily by OEE improvement). 5-year TCO: modern platform saving EUR 9M versus continued legacy operation, before OEE value.
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.
Munich's legacy modernization market includes SAP migration specialists (SNP, Datavard — focused on SAP but lacking MES and manufacturing depth), German systems integrators (msg, MHP — automotive knowledge but varying modernization capability), global integrators' Munich offices (Accenture, Deloitte — broad but EUR 5M+ minimums), and manufacturing technology vendors (Siemens, Rockwell — MES replacement but not SAP migration). ZTABS delivers Munich legacy modernization combining SAP S/4HANA migration expertise with manufacturing MES modernization and Catena-X integration.
Legacy modernization in Munich ranges from EUR 400K-1.2M for focused modernizations (SAP custom code remediation or single-plant MES) to EUR 3M-10M for comprehensive SAP + MES modernization programmes. SAP S/4HANA migration: EUR 1.5M-6M depending on custom code volume and complexity. MES unification: EUR 1M-4M depending on plant count and legacy variety. All engagements include Betriebsrat consultation support.
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 Munich businesses
Automated analysis classifying each programme: rewrite (1,800), adapt (1,400), replace with standard S/4HANA (600), or decommission (400). Our client reduced custom code 67 percent — from 4,200 to 1,400 programmes — dramatically reducing future upgrade complexity while preserving critical German payroll and automotive production logic.
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 Munich, GermanyZTABS is a remote-first web development agency serving Munich businesses — including full-stack development, progressive web apps, api development. We work with Automotive Tech, Enterprise Software, Industrial IoT companies in Munich, 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 Munich, GermanyZTABS is a remote-first web design agency serving Munich businesses — including ui/ux design, responsive design, custom interfaces. We work with Automotive Tech, Enterprise Software, Industrial IoT companies in Munich, 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 Munich, GermanyZTABS is a remote-first AI development agency serving Munich businesses — including llm integration & fine-tuning, ai agents & automation, rag & knowledge systems. We work with Automotive Tech, Enterprise Software, Industrial IoT companies in Munich, 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 Munich. Get a free consultation today.
