Moving 3.6M Lines of Natural Code to the Cloud Without Changing a Single Line

case study

Adabas/Natural Migration

From Unix machine to Cloud 3.6+ millions of Natural Lines of Code 130+GB of Adabas Compacted Database Within 45 Days Zero Code Changes

Industry:  Private Sector

Headquarters: Brazil

Coverage: Country

Core Technologies: Software AG Adabas/Natural → Oracle/ Natural migration runtime to Java

Our Customer

It is the largest consortium operator in the country, with over four decades of history. The migrated application is the heart of the company that manages all of its consortiums in the areas of real estate, automobiles and motorcycles.

To reduce costs, the Accounting and Financial applications were also migrated, instead of implementing them in a market package.

The Challenge

The systems were running in an obsolete Unix environment platform, the costs to relicense Natural and Adabas to another hardware were very high and hooked in dependencies.

Mission-critical systems, the heart of the company, to be migrated during a weekend to cloud architecture of a cloud supply company.

The Solution

Natural Migration with mLogica

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

  • Natural runtime 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.

Implementation Approach

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 rehosting 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 3.6+ millions of Natural source code lines 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.

Results and Benefits

- Over the weekend, the final migration of the Adabas database to Oracle was completed, along with the final compilation of all updated Natural sources in the new environment.

Then the upload proceeded to the cloud environment contracted by the client so that the new environment could be accessed on Monday by users as usual.

Hot support measures were adopted to ensure that any unforeseen events were promptly addressed. All areas involved, such as communication links support, cloud support analysts, migration technology support analysts, business analysts, production analysts, and others, were on standby for the system's entry on Monday.

Everything went smoothly without any incidents requiring team intervention. The on-call service was maintained during the first week but was not used.

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

Financial Impact

  • Eliminated upwards of $750,000 (or more) in recurring annual Adabas and Natural licensing costs, as well as the Financial Accounting package and implementation consulting, in addition to expenses associated with the legacy platform
  • Achieved upwards of a 14-month payback window, driven primarily by avoided licensing and accelerated realization of savings
  • The intangible gain of eliminating a production stoppage due to a failure in unsupported, obsolete equipment, going to cloud

Timeline and Risk Reduction

  • Delivered in 45 days versus an estimated of at least 3 years path for conversion-based modernization, not counting the time required for adaptation and replacement with the Financial Accounting package
  • 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 3.6+ 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.

Key Outcomes

  • 3.6+ Natural lines of source code unchanged
  • 130+GB of Adabas compacted database automatically migrated to Oracle (about 300GB)
  • 45 days delivery duration, 4 months approval testing
  • Zero code changes
  • Zero operational disruption
  • ~$750K+ annual licensing eliminated
  • 1 years of support services included

Technology Snapshot

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

Why mLogica is a Proven Path to Modernization without Disruption

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.