Executive Summary

UniCredit Bulbank, one of Bulgaria's leading banks, successfully modernized its enterprise data integration platform by migrating from Oracle Warehouse Builder (OWB) to Oracle Data Integrator (ODI). IBS Bulgaria delivered this critical transformation, migrating approximately 170 primary data flows and 1,600 sub-flows while implementing comprehensive execution monitoring. The project was completed on schedule and within budget, enabling platform modernization while maintaining continuous, reliable data processing for reporting, analytics, and regulatory compliance.

Client

The Challenge

UniCredit Bulbank's enterprise data warehouse depends on a large, interdependent ELT infrastructure that consolidates data from multiple operational systems. These pipelines produce cleaned datasets critical for:

• Reporting and analytics across the organization
• Regulatory compliance workloads
• Daily business operations

The bank needed to modernize by migrating from the legacy Oracle Warehouse Builder platform to Oracle Data Integrator while avoiding any disruption to business operations, managing complex dependencies between primary and sub-flows at scale, and improving operational visibility through execution monitoring.

Project Objectives

Platform Modernization: Upgrade the enterprise ELT toolset from OWB to ODI

Operational Excellence: Implement execution monitoring for visibility and control over data flows

Delivery Assurance: Complete the program on schedule and within budget

The Solution

ODI-Based ELT Migration

IBS Bulgaria employed a factory-based migration approach, maintaining like-for-like conversions by default with targeted refactoring only where necessary to preserve correctness and ensure operational stability. The migration was designed to be dependency-aware, carefully managing the complex relationships between primary flows and sub-flows.

Execution Observability Layer

A custom-built monitoring application was developed to provide execution dashboards showing status, durations, and failures, along with SLA tracking focused on technical execution monitoring. This operational layer enabled faster detection of issues and clearer visibility into run-state, reducing the need for manual interventions.

Implementation Approach

Discovery and Mapping

Comprehensive inventory of flows, dependencies, and schedules; establishment of migration design rules

Iterative Build and Test

Migration in manageable batches with regression validation ensuring continued production of expected cleaned datasets

Parallel Run Strategy

OWB and ODI operated in parallel until full migration completion, minimizing cutover risk

Operationalization

ODI agent-based scheduling and operational handover aligned with day-to-day DataOps requirements

Technology Stack

Results

• Successfully migrated 170 primary flows and 1,600 sub-flows to Oracle Data Integrator at scale
• Zero disruption to business operations – continuous reporting, analytics, and regulatory compliance throughout the migration
• Enhanced operational visibility through execution monitoring dashboards and SLA tracking
• Improved operational efficiency with fewer manual interventions due to clearer execution tracking
• Delivered on schedule and within budget

Key Success Factors

Dependency-First Planning

Managing primary and sub-flow relationships as the critical migration path

Parallel Run Strategy

De-risking cutover by running legacy and target platforms in parallel

Operational Observability from Day One

Preventing 'black box' batch processing through execution dashboards and SLA tracking

Controlled Refactoring Approach

Like-for-like migration by default, with refactoring only where it materially reduces risk