Migrating 22 Government Systems of Mission-Critical Data in Six Months

The company is responsible for the IT execution and operation of the entire state of Bahia, with 22 secretaries covering all activities of state government.

Target: Turn of Mainframe, reduce operational, hardware and software costs. Been ready to use up to date technologies in any operating environment.

Mission-critical systems to be migrated, incrementally and meeting the deadline stipulated for mainframe shutdown:

• School Administration System
• Personnel Information System
• Civil/Criminal/INFOSEG Identification System
• Information Management System
• Human Resources Support System
• Public Expenditure Management System (SIGAP)
• Weapons Control System
• BDRH Download System
• INFARM Registration System
• Microfilming Registration System
• Human Resources Integration System
• Materials Inventory System
• Accounting System
• Security System
• State Protocol System
• Information System Taxation
• Budget And Program System
• PM Scale System
• Mainframe Billing Measurement System
• Criminal Record System
• Data Extraction System for Infoseg
• Civil Identification System

Natural Migration

mLogica implemented a Natural migration approach designed to preserve application behavior while removing legacy dependencies. The solution is centered on:

• Natural migration, emulation to execute existing Natural logic unchanged, in a Java standard environment
• Automated database transformation from Adabas structures to Oracle schemas
• Controlled cutover and validation to ensure functional equivalence and production readiness

This approach enabled the Customer to retain the full value of the existing business logic investment while transitioning to an open, modern data platform and broader talent ecosystem.

mLogica delivered the program through a structured, quality-gated methodology focused on speed, predictability, and low operational risk.

Five-phase delivery preceded by assessment:

1. Assessment
   Comprehensive discovery of application inventory, Adabas data model characteristics, integrations, batch schedules, performance baselines, and risk areas, culminating in an approved modernization plan and migrating decision.
2. Database Migration
   Automated Adabas-to-Oracle conversion, including schema mapping, data migration, and validation. Performance considerations were built into indexing and access patterns to meet or exceed baseline expectations.
3. Application Migration
   Installation and configuration of the migrated environment, migration of runtime dependencies, and transfer of all 6.2+ million Natural lines of source code with zero code changes.
   
   Compiling all objects, deploying and executing them in a new robust and stable environment.
4. Testing & Quality Gates
   Functional equivalence validation, batch reconciliation, interface verification, and performance benchmarking. All test cases were required to pass prior to production readiness.
5. Knowledge Transfer & User Delivery
   Operational handover, enablement, and production rollout, delivering the system to users of each state secretary with zero operational disruption.
   
   No end-user training necessary.

- These were systems that met specific state demands and could not be replaced by standard packages. The systems had been in production for years, were extremely stable, and functionally complete.

- Mainframe shutdown with reduced hardware and software licensing costs;

- Direct integration with other systems via Web Services and Database;

- The existing analysts are supporting and increasing new functionalities in the system.

Financial Impact

• Eliminated upwards of $1.500.000 (or more) in recurring annual Adabas and Natural licensing costs and associated legacy platform expenses
• Achieved upwards of an 36-month payback window, driven primarily by avoided licensing and accelerated realization of savings
• Despite a substantial scope expansion during execution, commercial impact remained minimal, with a <3% price increase even as the scope expanded materially.

Timeline and Risk Reduction

• Delivered in 6 months versus an estimated 3 to 5 yards path for conversion-based modernization
• 75% faster timeline, enabling earlier go-live and faster benefit capture
• Lower risk profile by maintaining the known-good business logic path rather than introducing large-scale recoding variability

Technical Benefits

• All 6,2+ Natural lines of source code unchanged, preserving behavior and reducing regression risk.
• Application performance met or exceeded baseline expectations, supported by Oracle optimization and migrated runtime tuning.
• Modernized data foundation improved maintainability, extensibility, and operational tooling options.

Strategic Advantages

• Reduced reliance on proprietary constraints and improved flexibility for future modernization phases.
• Expanded access to mainstream Oracle skill pools versus scarce Adabas expertise.
• Positioned the Customer for incremental modernization (API enablement, UI modernization, DevOps improvements, cloud readiness) without forcing a “big bang” rewrite.

• 6,2+ Natural lines of source code unchanged
• 270+GB of Adabas compacted database automatically migrated to Oracle (about 600 GB)
• 4 months delivery duration
• 75% faster delivery
• Zero code changes
• Zero operational disruption
• ~$1.5M+ annual licensing eliminated
• 2 years of support services included

Source Environment

• Software AG Adabas database
• Natural application components (online and batch workloads)

Target Environment

• Oracle database
• Natural rehosting runtime with functional equivalence controls
• Modern operational tooling for monitoring, support, and performance management

mLogica delivered a modernization outcome that balanced speed with certainty, protecting business continuity while modernizing the underlying platform. The engagement applied mLogica’s proven legacy-to-modern transformation expertise, disciplined delivery governance, and modernization engineering practices to ensure functional equivalence, predictable execution, and production-ready performance.

This engagement also reinforces a critical modernization principle for SLED organizations: Natural rehosting is a practical, low-risk strategy to reduce cost and dependency while preserving mission-critical functionality. By transitioning from Adabas to Oracle and retaining the Natural logic unchanged, the Customer accelerated delivery, achieved measurable savings, and established a durable foundation for future modernization initiatives, without sacrificing operational stability.

Modernize with Confidence. Operate with Continuity. Scale for the Future.