Legacy App Modernization in Amsterdam for Banking, Pensions and Logistics

ZTABS modernizes legacy applications for Amsterdam enterprises in banking, pension administration, logistics and insurance. Dutch banks operate COBOL mainframe systems processing billions in transactions. Pension administration organisations manage substantial assets on legacy platforms serving millions of participants. Port of Rotterdam logistics systems connect global supply chains through legacy EDI interfaces. ZTABS is remote-first by design from our Houston, Texas office.

Amsterdam's legacy modernization demand spans Dutch banking COBOL mainframe migration for DNB-supervised institutions, pension administration modernization for WTP transition readiness, port logistics system upgrades for real-time supply chain visibility, and insurance platform modernization.

Legacy app modernization in Amsterdam at a glance

Need	What we build	Key requirement
Banking	COBOL mainframe migration	DNB, DORA, SEPA Instant
Pensions	Administration modernization	WTP transition, DNB
Logistics	Port system upgrades	Portbase, customs, EDI
Insurance	Platform modernization	Solvency II, actuarial
Enterprise	Monolith decomposition	GDPR, data protection

Dutch banking COBOL modernization

Dutch banks operate COBOL mainframe core banking systems processing transactions for millions of customers. Legacy systems reliably process SEPA transfers, direct debits and card payments. Assessment determines actual API wrapper, upgrade and integration options for PSD2 open banking, instant payments and mobile banking.

Core banking migration. Account management, transaction processing, general ledger and customer information migrating from COBOL mainframes. DNB supervisory expectations and DORA requirements addressed at each migration phase.

SEPA Instant enablement. Legacy batch-oriented payment processing modernized for real-time SEPA Instant capability. Payment processing latency reduced from batch cycles to real-time.

Regulatory reporting. DNB SREP technology risk assessment addressed. DORA operational resilience requirements assessed in modernized architecture. Automated regulatory reporting replacing manual data extraction where agreed.

Pension administration modernization

Dutch pension administration organisations manage a substantial pension system on legacy platforms. AS/400 RPG systems administer millions of active members, deferred members and pensioners. WTP transition readiness assessed per fund-specific requirements with actuarial and owner acceptance for residuals.

Contribution processing. Monthly contribution calculations for millions of active members with varying rates. Employer contribution processing modernized from file-based to API-based where employers are ready.

Benefit calculation. Pension benefit calculations encoding decades of regulatory changes. Actuarial algorithms for reserves, projections and UPO statement generation preserved and verified.

Participant self-service. Legacy batch-processing architecture modernized for real-time participant portal access. Pension projections, contribution history and scenario modelling enabled.

Port logistics modernization

Port of Rotterdam logistics systems connect global supply chains through legacy EDI interfaces designed for a pre-internet era.

Container tracking. Legacy terminal operating systems modernized for real-time container tracking and supply chain visibility.

Customs integration. Portbase seaport distinct from Cargonaut air-cargo. Dutch Customs and provider API licences and production permissions actual. Legacy customs clearance interfaces modernized for current message formats.

Supply chain visibility. Legacy batch processing systems modernized for real-time tracking. Shipping lines, trucking companies and rail network connections modernized.

Dutch regulation

GDPR. Actual roles, bases, Article 9 sensitive data and transfer routes. No Netherlands or EU hosting alone guarantees compliance or mandates all-local processing. Multiple actual legal bases available.

ACM analytics exception. Low-privacy-impact analytics consent exception distinct from necessary functional or transmission cookies. This exception is specific to Dutch law; other jurisdictions require their own regulatory assessment.

Electronic marketing. Actual consent or sale own similar products no-objection opt-out at collection and each message. Actual B2B statutory route where applicable. Not only existing customers.

WOR. Section 25 advice on significant organisational decisions. Section 27 monitoring-system consent with actual scope. Not all technology changes automatically require ondernemingsraad consent.

Belastingdienst retention. 7 year baseline with 10 year actual categories. Not all logs same retention period.

DigiD and BSN. Access requires actual authorised service and purpose. No general SaaS entitlement to citizen identity data.

AEO. Actual supply-chain operator criteria and authorisations, not simply own-account trader status. Declarant and direct or indirect customs representation separate.

Adyen and Mollie. Actual approved account, payment method, currency and recurring conditions. No billing API automatically grants regulated payment-service status.

Strangler fig for Dutch systems

Seam selection. Banking seams: payments, accounts, lending, regulatory reporting. Pension seams: contribution processing, benefit calculation, participant services, regulatory reporting. Logistics seams: container tracking, customs, billing, scheduling.

Single authoritative write. One system authoritative for each transaction type and period during coexistence. Financial dual-write dangerous for regulatory 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 pension payments, SEPA settlements and customs declarations.

Data migration methodology

Banking data. Account records, transaction history and regulatory data migrated with reconciliation against agreed record totals, tolerances and exception register with owner acceptance. DNB regulatory reporting data addressed at each migration phase.

Pension data. Member records, contribution history, benefit accrual records, actuarial data and regulatory reporting data migrated with actuarial verification. Historical pension data preserved for ongoing administration.

Logistics data. Container records, customs declarations, shipping schedules and billing data migrated with operational verification.

Data type mapping. Types, nulls, time zones, currency, rounding, identifiers, encoding, history and crosswalks reconciled. Dutch-specific: BSN handling per privacy requirements, pension scheme identifiers, customs tariff codes. EUR currency precision.

Cutover rehearsal. Observable acceptance with measurable RTO, RPO and latency targets. Banking cutover timed for settlement cycles. Pension cutover timed around payment cycles. Logistics cutover planned for lower-volume periods.

Inventory and discovery

Amsterdam 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. Banking rules validated against DNB requirements. Pension rules validated against actuarial standards. Logistics rules validated against customs requirements.

Modernization approach selection

Amsterdam enterprises need clear criteria for choosing between approaches.

Targeted remediation. Adding specific capabilities. Example: adding API layer to legacy pension system for participant portal while keeping RPG for core calculations.

Re-platforming. Moving to modern infrastructure while preserving logic. Example: migrating legacy billing to cloud while preserving rating algorithms.

Re-architecture. Decomposing monolith into services. Example: extracting contribution processing, benefit calculation and reporting as independent services.

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

Regression and testing

Representative business-critical paths: banking transaction lifecycle, pension benefit calculation and payment, logistics container tracking, customs clearance. Meaningful integration, performance and manual UAT with domain expert approval.

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 Amsterdam 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.
• Pension platform vendor selection. Pension administration platform licence selection and actuarial product configuration are the licensed vendor's and customer's scope. This engagement modernizes the surrounding integration, data migration and regulatory reporting connections.
• 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.
• DNB or AFM 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. Amsterdam technology companies can commission white-label AI platforms for distribution under their own brand.

Integration and dependency management

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

Pension integrations. Employer data exchange, investment manager connections, DNB and AFM regulatory reporting, Pensioenregister national pension registry.

Logistics integrations. Portbase seaport connections, Cargonaut air-cargo connections, Dutch Customs API, shipping line, trucking company and rail network interfaces.

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

Logs and retention

Logs minimise and redact secrets and regulated payloads with actual retention and legal holds. Belastingdienst 7-year baseline with 10-year categories for specific financial records. Pension records retained per DNB and pension fund requirements. Not all logs require same retention period.

Cutover rehearsal detail

Observable acceptance with measurable RTO, RPO and latency targets. Banking cutover timed for settlement cycles. Pension cutover timed around monthly payment cycles and UPO generation periods.

Rollback feasibility assessed after schema, data and contract changes. Pension payments, SEPA settlements and customs declarations may not be automatically reversible. Compensations can require actuarial, legal or accounting review.

Data type mapping for Amsterdam industries

Amsterdam industry data has unique types requiring careful migration planning. Banking: IBAN formats with Dutch bank codes, SEPA payment identifiers with settlement conventions, DNB regulatory reporting fields. Pension: member identifiers with BSN handling per privacy requirements, contribution dates with employer reporting cycles, actuarial valuation dates, benefit payment dates. Logistics: container identifiers with terminal-specific codes, customs tariff codes, Portbase message identifiers, shipping line booking references.

Assessment methodology

Application archaeology for Amsterdam systems covers COBOL programme analysis for banking business rule extraction, RPG programme analysis for pension calculation rule extraction, EDI interface cataloguing for logistics integration mapping, and regulatory reporting analysis for DNB and customs compliance verification.

Insurance modernization

Dutch insurers operate legacy policy administration, claims and actuarial systems reflecting decades of mergers. Multiple predecessor brands with separate legacy systems requiring consolidation.

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

Claims processing. Claims workflow modernized for digital submission, automated assessment and faster settlement. Multiple predecessor brand legacy systems consolidated where applicable.

iDEAL and Wero payments

iDEAL and Wero have actual merchant, acquirer, product version rollout and callback verification and reconciliation requirements. No arbitrary automatic migration date. Not all merchants have the same contract. Payment system modernization references current product specifications and verified API capabilities.

Risks and mitigations

Pension calculation accuracy. Actuarial verification through parallel operation. Historical benefit calculations validated before cutover.

Customs integration continuity. Portbase and Dutch Customs integrations addressed at each migration phase. Legacy EDI formats supported during transition.

Data residency. Dutch data residency requirements assessed per actual processing basis. GDPR transfer routes applied where cross-border processing involved. No Netherlands hosting alone guarantees compliance and no mandatory all-local processing requirement exists by default.

Government system modernization

Dutch government agencies operate legacy systems requiring modernization for digital citizen services.

Tax administration. Belastingdienst legacy tax processing systems modernized for digital submission and automated processing. Fiscal requirements addressed at each migration phase.

Education and social services. DUO student finance and UWV benefit processing systems on legacy platforms requiring modernization for digital service delivery and citizen self-service.

Handover

Modernization handover includes runbooks, data lineage, licensing, support contacts and accountable owners. Banking handover includes DNB compliance documentation and DORA resilience evidence. Pension handover includes actuarial documentation, DNB reporting specifications and Pensioenregister integration documentation.