Legacy App Modernization in Berlin for Banking, Insurance and Manufacturing

ZTABS modernizes legacy applications for Berlin enterprises in banking, insurance, manufacturing and Mittelstand technology. Berlin banks operate COBOL mainframe core banking systems. Insurance companies process claims through Java monoliths. Manufacturing companies run SAP R/3 with thousands of custom ABAP programmes approaching S/4HANA migration deadline. ZTABS is remote-first by design from our Houston, Texas office.

Berlin's legacy modernization demand spans COBOL banking mainframe migration for BaFin-regulated institutions, SAP ECC to S/4HANA transition for manufacturing and Mittelstand companies, Java monolith decomposition for insurance and fintech platforms, and Oracle Forms government system replacement.

Legacy app modernization in Berlin at a glance

Need	What we build	Key requirement
Banking	COBOL mainframe migration	BaFin, DORA, SEPA
Insurance	Java monolith decomposition	Solvency II, actuarial
Manufacturing	SAP R/3 to S/4HANA	JIT/JIS, IATF 16949
Mittelstand	ERP modernization	German payroll, HGB
Fintech	Platform decomposition	BaFin, PSD2

Banking COBOL modernization

Berlin banks operate COBOL mainframe core banking systems processing transactions, customer management and regulatory reporting. These systems support retail banking, corporate banking and securities services. Assessment determines actual API wrapper, upgrade and integration options for PSD2 open banking, SEPA Instant payments and mobile banking.

Core banking migration. Account management, transaction processing, general ledger and customer information migrating from COBOL mainframes. BaFin regulatory reporting addressed at each migration phase. SEPA payment processing preserved and enhanced for instant payment capability.

Open banking enablement. PSD2 requirements for API-accessible account information and payment initiation services assessed per actual system scope. Legacy batch-oriented payment processing modernized for real-time capabilities where agreed.

Regulatory reporting. BaFin reporting including MaRisk and applicable DORA requirements addressed in modernized data stores. Manual regulatory report compilation replaced with automated generation where agreed.

SAP R/3 to S/4HANA transition

German enterprises face SAP ECC maintenance changes that depend on actual product, module, version and contract. Installations with thousands of custom ABAP programmes accumulated over 15 to 20 years require systematic analysis before migration.

Custom code analysis. Each Z-programme classified as rewrite, adapt, replace with standard S/4HANA functionality or decommission. Dead code identified and removed. Standard S/4HANA functionality replacing custom solutions where possible.

German payroll. German payroll is among the most complex globally. Kurzarbeit calculations, church tax, solidarity surcharge, Berufsgenossenschaft contributions and Arbeitnehmer-Sparzulage require careful reimplementation. Each calculation validated against current Lohnsteuer-Handbuch and BG contribution tables.

Production planning. Automotive JIT/JIS delivery sequences preserved for OEM supply chain compliance. Production planning customisations reimplemented for S/4HANA embedded PP/DS.

Financial accounting. HGB and IFRS parallel accounting leveraging S/4HANA universal journal. Transfer pricing across multiple countries addressed per actual module and version.

Insurance modernization

Berlin insurers operate Java monolith applications for policy administration, claims processing and actuarial systems. Monthly release cycles and complex EJB architectures constrain digital distribution and AI-based claims assessment.

Policy administration. Life, P&C and health insurance policy lifecycle modernized. Actuarial calculations preserved with mathematical verification. Solvency II reporting dependencies addressed at each migration phase.

Claims processing. Claims workflow from FNOL through investigation, assessment and settlement. Digital customer channels and automated claims assessment enabled.

Manufacturing and Mittelstand

Berlin-area manufacturers operate legacy MES, PLM and ERP systems constraining Industry 4.0 integration.

MES modernization. Manufacturing execution systems on legacy platforms modernized for real-time production data, IoT sensor integration and quality analytics. IEC 62443 cybersecurity is distinct from ISO 26262 safety and IATF 16949 or ISO 21434 product and programme scope. No modernization guarantees certification.

SAP S/4HANA, DATEV, proALPHA. Actual product version, vendor licence and tenant action permissions verified. Not all legacy installations automatically unsupported or custom microservices compulsory. Configuration, upgrade and licensed partner help where appropriate.

Catena-X. Catena-X association membership is distinct from operational data-space access. Automotive supply chain data exchange enabled through modern API architecture where applicable.

German regulation

GDPR and BDSG. GDPR directly applicable in Germany with BDSG supplementary provisions. Personal data modernized with appropriate protections throughout migration.

TDDDG and UWG. TDDDG covers terminal-device storage and access, distinct from UWG electronic marketing. UWG 7(3) applies to actual sale of own similar products or services, no objection, with opt-out at collection and each message. Not a universal double-opt-in statute.

Works council. Section 87(1)(6) co-determination for technical devices capable of monitoring employee behaviour or performance, with agreement or conciliation. Section 90 timely planning information and consultation. Section 111 applies to companies normally with more than 20 eligible employees for proposed operational changes that may cause substantial disadvantages; within Section 111, companies with more than 300 employees have adviser entitlement. Not every technology change or employee data use automatically requires the same approval. Early engagement during assessment reduces delay risk.

HGB and AO retention. Baseline 10 years for books, 8 years for vouchers, 6 years for business correspondence. KWG institutions including branches, VAG-supervised entities and securities institutions keep vouchers for 10 years. Calendar-year-end document-event clocks under Section 257(5). Holds and other applicable AO provisions preserved. Not all logs have the same retention period.

GoBD. Z1 direct read and analysis, Z2 indirect analysis, Z3 machine-evaluable data provision. These are not tamper protection or format-conversion modes. Data migration preserves GoBD-compliant access.

B2G e-invoicing. EN 16931 with alternatives, not XRechnung only. B2B receipt versus phased issuance with actual dates, entity and transaction exceptions.

DORA. Actual regulated institution and ICT-contract obligations. VAIT, KAIT and ZAIT revoked January 2025. Residual BAIT applies to specific institutions until 31 December 2026, not all firms remain under BAIT.

Berlin Bildungszeitgesetz. Berlin's current Bildungszeitgesetz (BiZeitG), effective 1 September 2021, replaced the former Bildungsurlaubsgesetz. Staff training and qualification arrangements agreed per engagement scope.

Strangler fig for German systems

Seam selection. Banking seams: account management, payments, lending, regulatory reporting. Insurance seams: policy administration, claims, actuarial. Manufacturing seams: production planning, quality management, procurement. Each function extracted independently.

Single authoritative write. One system authoritative for each transaction type and period during coexistence. Financial dual-write dangerous for HGB and IFRS reporting. CDC with versioning and conflict detection.

Reconciliation. Idempotency keys enforced by receiving side. Finite retries with DLQ. Unknown outcomes require reconciliation before replay, especially for SEPA payments, insurance settlements and production orders.

Data migration methodology

Financial data. Banking and insurance data migrated with reconciliation against agreed record totals, tolerances and exception register with owner acceptance. HGB and IFRS regulatory data verified for completeness. Migration documentation formatted for BaFin examination.

Manufacturing data. Production records, quality data, material master and BOM data migrated with manufacturing verification. IATF 16949 quality records preserved.

SAP data. Custom ABAP data structures mapped to S/4HANA data model. Historical data archived or converted per retention requirements.

Data type mapping. Types, nulls, time zones, currency, rounding, identifiers, encoding, history and crosswalks reconciled. German-specific: EUR currency precision, German date conventions, Umlauts and special characters in customer names.

Cutover rehearsal. Observable acceptance with measurable RTO, RPO and latency targets. Banking cutover timed for settlement cycle boundaries. Manufacturing cutover timed for production schedule boundaries.

Inventory and discovery

Berlin enterprise modernization begins with complete inventory: applications, users, scheduled jobs, database procedures, reports, file and EDI dependencies, vendor contracts, supported versus end-of-life versions.

Business rules discovered with users through representative transaction analysis and fixture-based testing. Banking rules validated against BaFin requirements. Manufacturing rules validated against OEM specifications and IATF 16949. SAP customisations classified against standard S/4HANA functionality.

Integration and dependency management

Banking integrations. SEPA payment networks, BaFin regulatory reporting, SWIFT and correspondent bank connections. Each integration documented and migration coordinated.

Manufacturing integrations. OEM EDI connections, supplier portals, logistics providers and Catena-X data exchange where applicable.

SAP integrations. Custom interfaces to downstream systems documented and migrated. DATEV, proALPHA and other German enterprise software integrations preserved with actual product version capabilities.

Authentication versus authorisation. Authentication identity distinct from account-level, role-level and transaction-level authorisation. Modernization addresses both with appropriate granularity.

Modernization approach selection

Berlin enterprises need clear criteria for choosing between approaches.

Targeted remediation. Adding specific capabilities to otherwise functional systems. Example: adding API layer to legacy core banking for PSD2 open banking while keeping mainframe for transaction processing.

Re-platforming. Moving to modern infrastructure while preserving logic. Example: migrating Java monolith to containerized deployment while preserving business logic.

Re-architecture. Decomposing monolith into services. Example: extracting payment processing, compliance and customer management from monolithic fintech platform.

Full rebuild. Ground-up development for systems where legacy code is unmaintainable.

SaaS replacement or upgrade. SAP S/4HANA migration, licensed platform upgrade or commercial replacement. Low build risk but high fit risk for heavily customised German enterprise workflows.

Regression and testing

Representative business-critical paths: banking transaction lifecycle, insurance policy lifecycle, manufacturing production order, SAP financial close. Meaningful integration, performance and manual UAT with domain expert approval. Betriebsrat-relevant testing for systems affecting employee data.

Cost and timeline

Legacy system modernization follows the published cost guide.

Tier	Range	Timeline	Example
UI Modernization	$40K to $100K	8 to 16 weeks	New frontend, API wrapper, improved UX
Re-Platforming	$100K to $250K	16 to 32 weeks	Modern stack, containerization, cloud, data migration
Re-Architecture	$250K to $400K	8 to 14 months	Decompose monolith, event-driven, modern data layer
Full Rebuild	$400K to $500K+	12 to 18+ months	Ground-up rebuild, agreed availability target, rehearsed staged cutover

Vendor comparison

Ranges are 2026 US-buyer guide-based estimates for re-platforming a 10 to 15 year old business-critical system using a strangler fig approach, modern stack, API wrappers, phased data migration and regression harness.

Vendor type	Typical cost	Timeline
Freelance or dev collective	$40K to $130K	5 to 12 months
Offshore systems integrator	$60K to $200K	8 to 14 months
ZTABS	$100K to $280K	6 to 12 months
Big 4 consultancy	$300K to $1M+	10 to 18 months
SaaS replacement vendor	$50K to $200K implementation	4 to 9 months

Parallel-running infrastructure, senior knowledge-transfer time and where applicable compliance revalidation can add a combined scope-dependent $100K to $500K+ planning allowance. The guide's examples are SOX, HIPAA and FDA; actual applicable regime depends on the engagement.

Proposal evaluation criteria

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

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

How delivery works

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

When ZTABS is not the right fit

• The system still works and nobody is asking for changes. Wait for a real forcing function.
• SAP S/4HANA implementation from licensed partner. SAP licence selection, greenfield configuration and partner-led implementation are the licensed vendor's and customer's scope. This engagement modernizes the surrounding integration, data migration and custom development that connects to the new platform.
• On-site programme office and multi-vendor coordination. This engagement delivers application modernization. Separately contracted programme governance, on-site management and advisory retainers have different scope and responsibilities.
• On-site embedded team. ZTABS is remote-first by design. On-site staffing, training and support retainers for this engagement are separately agreed.
• BaFin or BSI regulatory advisory. This engagement builds platforms, not regulatory advice. Regulatory advisory is separately engaged.

White-label AI products

ZTABS builds custom white-label AI products for clients to brand and resell. Berlin technology companies can commission white-label AI platforms for distribution under their own brand.

Logs and retention

Logs minimise and redact secrets and regulated payloads with actual retention and legal holds. HGB 10-year book retention, 8-year voucher retention, 6-year correspondence retention; KWG institutions keep vouchers for 10 years. Calendar-year-end document-event clocks under Section 257(5). GoBD access levels addressed during migration.

Risks and mitigations

SAP custom code complexity. Systematic classification reduces migration scope. Standard S/4HANA functionality replaces custom solutions where possible.

Betriebsrat timeline. Early engagement during assessment reduces delay risk. Consultation periods built into programme plan. No guaranteed prevention of all schedule impact.

Character encoding. German Umlauts and special characters preserved throughout migration. UTF-8 encoding standard.

Data type mapping for Berlin industries

Berlin industry data has unique types requiring careful migration planning. Banking: SEPA payment identifiers, BaFin regulatory reporting fields, settlement dates with T2 conventions. Insurance: policy inception and expiry dates with German convention, Solvency II reporting fields, actuarial valuation dates. Manufacturing: SAP material master numbers, BOM structure identifiers, production order numbers with plant-specific sequences, IATF 16949 quality inspection record identifiers.

Handover

Modernization handover includes runbooks, data lineage, licensing, support contacts and accountable owners. Banking handover includes BaFin compliance documentation and regulatory reporting specifications. Manufacturing handover includes IATF 16949 quality documentation and OEM integration specifications.