DMOne™ Platformby eAppSysAI-enabled accelerator for Oracle Fusion
DMOne™ / Modules / Data Migration
DMOne™ platform module, stage 2: Migrate

Data Migration

Data Migration is the DMOne™ Platform module for migrating data from legacy systems into Oracle Fusion. It covers the full cycle, from extraction to reconciliation, with cleansing and deduplication built in, and removes the need to build ETL code for each programme.

  1. Data ingestion
  2. Data cleansing
  3. Data validation
  4. Data extraction
  5. Data transformation
  6. Pre-load reconciliation
  7. Target data loading
  8. Post-load reconciliation
100% technical reconciliation out of the box
Pre-built adapter for Oracle E-Business Suite

The problem

What goes wrong without Data Migration

Data migration is usually built on custom scripts and files passed between client and SI teams. Data is loaded once, late, and issues surface when testing is already under way.

ProblemHow Data Migration solves it
Legacy complexity

Multiple sources, customised systems, custom tables and years of local workarounds are handled through configured connectors and rules, not bespoke scripts.

Inconsistent data

Duplicates, gaps and values that do not fit the Fusion design are found by profiling and validation before load.

Late design decisions

When configuration changes, rules are corrected once and reapplied in the next run, rather than mappings being rebuilt.

Multiple handoffs

Client and delivery teams work on the same data in one place, with no file handoffs between teams.

Testing delays

Representative data is loaded early and often, so it is ready when unit, SIT and UAT testing start.

Data security

Data is masked for non-production cycles, so integration and other testing is not held back.

Cutover risk

Issues are found in early, repeated cycles rather than late, so the go-live date is not put at risk.

Common data migration challenges, by stage

Data Migration covers each of these, with change management, governance and audit across every stage.

Cleansing

  • Data duplication
  • Data quality issues
  • Source data cleansing
  • Data audit
  • Data owners
  • Cleansing rules

Extraction

  • Large data volumes
  • Incremental data loads
  • Multiple source extraction
  • Custom EBS module data integration
  • Extraction rules

Transformation

  • Data masking
  • Complex data mapping
  • Old and new segment mapping
  • Data merging and transformation
  • Data enrichment
  • Complex transformation (chart of accounts, payroll)
  • Training data preparation

Load

  • Pre-load reconciliation
  • Incremental file generation
  • Error handling and retries
  • Technical validation

Reconcile

  • Post-load reconciliation
  • Parallel loads to SIT and UAT
  • Source-to-target reconciliation
  • Payroll reconciliation
Change management, governance and audit

The solution

How Data Migration solves it

Data is loaded early and often from pre-built templates, rather than in one late load built on custom scripts.

  • Start from tested migration runbooks, customised for each new client
  • Start from pre-built templates for extraction, mapping and transformation
  • Load representative data for design workshops once the initial configuration is in place
  • Correct a rule once and reapply it in the next cycle; reload only the corrected records
  • Load DEV, SIT and UAT from the same rule set, with reconciliation on every run

In brief

The same module, explained for three readers.

For CXOs and data owners

Data reconciled at every load, with 100% technical reconciliation, lowers the risk at cutover. No custom ETL code to build or maintain for each programme.

For project managers

Plan it from the first mock load to cutover. Loads are repeatable and version-controlled, and reconciliation reports feed status reporting.

For solution architects

Extracts by database link, REST, files or Data Pump; cleanses, deduplicates and transforms through a rule engine; loads via FBDI, HDL or REST; reconciles pre-load and post-load per object.

What it does

Extract

Database links, REST APIs, CSV files with any delimiter, Excel and XML files, and Data Pump import, with a preview before you load.

Cleanse and deduplicate

Rules-based and AI-assisted cleansing runs before matching, then exact and confidence-scored fuzzy matching flag duplicates, with an audit trail.

Transform

A rule engine handles complex nested rules. Legacy-to-target mappings stay aligned with target configuration.

Load

Generates FBDI and HDL files or uses REST APIs. Supports incremental loads, version control and multiple environments.

Excel-based interface

Functional users take part in mapping and loads through Excel, without authoring HDL .dat files.

Tracking and audit

Real-time tracking of every stage, with a full audit trail and reconciliation reporting across the migration.

Reconcile

Pre-load and post-load reconciliation for each master and transaction object, at technical and business level.

Complex transformations

Old-to-new segment mapping for the chart of accounts, payroll transformations, data merging and preparation of training data.

Payroll reconciliation

Payroll results reconciled between the legacy system and Fusion for parallel runs and cutover.

Object library

Pre-built objects across Global HR, Global Payroll, recruitment, absence, expenses, Payables, Receivables, General Ledger and Fixed Assets.

Meeting your data obligations

In most transformations the client is responsible for its data and for supplying it to the SI partner when requested. If data is late or not usable, the programme is delayed, and the client is usually responsible for that delay.

  • Templates for extracting and preparing each data object, so client teams are not waiting on specialists
  • Cleansing rules owned and approved by the business
  • Early quality checks, so problems are found before the delivery date rather than after it
  • A clear view of which objects have been supplied and which are outstanding
  • A time-stamped record of every data delivery, check and sign-off
  • Shared evidence that protects both the client and the SI partner if timelines are questioned

Data Migration at a glance

ExtractionCleansingEnrichmentTransformationLoadingReconciliationAnalysisDMOne™Data MigrationFrom any legacy system to Oracle FusionA module of the DMOne™ PlatformHCM CloudERP CloudSCM CloudCX CloudPPM CloudOracle Cloud Infrastructure and PlatformData masking, data integrity checking, insights, governance, security
1

A cloud-based module of the DMOne™ Platform, developed by eAppSys, supporting all data migration and data management activities.

2

Out-of-the-box components for rule-based extraction, transformation, validation, file preparation and reconciliation.

3

Handles multiple source systems and multiple target file formats, to multiple target systems if required.

Three reasons teams choose it

Don’t build ETLs. Just DMOne™ it.

End-to-end control

The full migration lifecycle on one governed platform.

Adaptability

Configurable for complex client landscapes, without custom code for each source.

Potential cost and risk benefits

Less rework and more predictable cycles.

From handoffs to one platform

In many programmes the client extracts, cleanses and transforms data, and the SI loads and reconciles it. The handoff in the middle is where time is lost.

Traditional modelWith Data Migration
Files change hands
Every cycle depends on files being passed between client and SI teams.
No file handoffs
Client and delivery teams work on the same data in one place.
Errors travel back
Load failures return to the client team to fix and resend.
Errors fixed at source
Rules are corrected once and reapplied in the next run.
Evidence is assembled late
Reconciliation is pieced together from separate tools.
Evidence as you go
Pre-load and post-load reconciliation is produced on every run.

Illustrative. Responsibilities vary by engagement. The client continues to own its data, approve the rules and sign off each cycle.

Data migration starts with design and enables testing

Migration is scheduled against configuration and test readiness, so it supports the programme instead of following it.

  1. Design

    Mappings come from design workshops and the Fusion configuration.

  2. Build

    Fusion configuration is read into the module, so data is validated against the current setup.

  3. Unit test

    Representative, masked data subsets are loaded as soon as build is ready.

  4. SIT

    Managed test cycles, loaded in parallel to separate environments.

  5. UAT and mocks

    Full-volume runs with reconciliation evidence.

  6. Cutover

    The rehearsed process is run on the same rule set.

Automated, governed and accountable

The full data migration lifecycle runs in one module of the DMOne™ platform.

Automated

The work is automated

Source extraction, profiling, mapping and transformation, validation, Fusion load and reconciliation.

No file handoffs
Client and delivery teams work on the same data in one place.
Governed

Every stage is controlled

Approvals and audit evidence are recorded at each stage of each cycle.

Errors fixed at source
Rules are corrected once and reapplied in the next run.
Accountable

Data owners stay in charge

Client data owners approve rules and sign off each cycle.

Evidence as you go
Pre-load and post-load reconciliation is produced on every run.

What is different from conventional migration tooling

Fusion-aware validation

Data is checked against the target pod’s configuration before load.

Governed rules

Transformation rules are approved and owned in one place, and reused in every cycle.

Multiple target environments

DEV, SIT and UAT are loaded from the same platform and rule set.

Version control

Rules, files and batches are versioned across cycles.

Data masking

Masked data is used for non-production cycles.

Controlled deletions

Loaded data is removed in a controlled way between cycles.

Incremental reloads

Only corrected records are regenerated and reloaded.

Linked to configuration loads

Configuration and data migration loads are managed together.

Source-to-target traceability

Data is tracked from source to target at each step, and the business stays in charge of its own data through version-controlled iterations.

  1. Source extract

    Full or incremental extracts and updates.

  2. Transformation and enrichment

    Metadata-driven mappings, copy columns and enrichment rules, configured rather than coded.

  3. Validation and cleanse

    Mandatory and lookup validations; deduplication and cleansing that is automated, assisted or user-driven.

  4. Target file generation

    Files in each target’s format, for one or several target systems.

  5. Load and error handling

    Errors are reported and corrected without restarting the cycle.

  6. Reconciliation and sign-off

    Source-to-target reconciliation, signed off by the business.

  7. Feedback and insights

    Visibility for the project team and early insight into data issues.

Data users work in familiar Excel, with export from and import to the module.

Key benefits

Shorter migration cycles, and fewer of them

Repeatable, iterative cycles replace one-off scripts.

Tested runbooks and templates

Tested migration runbooks, template documents, template builds and performance-tested components, customised for each new client.

Reduced testing effort

Data is validated and reconciled before it reaches testers.

Traceability at every step

Every record can be followed from source to target.

Visibility and monitoring

The project team sees the status of every object and cycle.

Less code, no code

Configured, not coded, so changes are quick and low-cost.

Architecture: four components

From source connection to reconciliation.

Source connectivity

Databases, files and applications, including Oracle E-Business Suite.

Transformation

Configurable rules for mapping, enrichment, deduplication and validation.

Oracle Fusion loading

Loads generated and submitted to Fusion, validated against its setup.

Reconciliation

Pre-load and post-load reconciliation, with dashboards and audit history.

One rule set promoted across every environment

DEVSITUATProduction

Mapping and rule promotion

Fixes made in one cycle carry forward under version control.

Batch management

Mock, SIT, UAT and cutover rehearsal run as separate batches in parallel.

Traceability

Each load is traced to its rule version, file set and approver.

Test-data preparation

Representative subsets are prepared for unit testing ahead of full-volume mocks.

Example: suppliers from Oracle EBS to Fusion

One object, end to end, as a consultant runs it.

  1. Connect the source

    Select the EBS adapter and the Suppliers object.

  2. Map and validate

    Review mappings and fix a failed rule in the rule editor.

  3. Environment-specific rules

    Apply SIT values without changing the core rule.

  4. Load to Fusion

    Generate and submit the load in one action.

  5. Reconcile

    Open pre-load and post-load reconciliation.

  6. Evidence

    Export the report for client sign-off.

Configuration, not code

Complex client landscapes, including custom tables, flexfields, spreadsheets with varying layouts and external systems, are handled by configuring the module rather than writing code for each source. Rules are reused across objects and programmes.

Who runs it

Delivery teams run the module themselves. It does not need tool specialists.

Who operates itFunctional and data migration consultants, in client and SI partner teams
Skills neededOracle Fusion knowledge, with some technical knowledge of the relevant modules
Time to onboard a team1 to 2 weeks

Change a mapping rule

Edit the rule, revalidate and see the error count change.

Rerun a validation

Run again on the same batch after a fix.

Reload a failed record

Correct the record and reload only that record.

Promote a rule

Carry a fix to the next environment under version control.

Approve a batch

A data steward reviews and approves the batch.

Export evidence

The reconciliation report is ready for client sign-off.

What changes for the project team

TodayWith Data Migration
Custom scripts
The client’s extraction team writes scripts to extract and bring data together.
Pre-built templates
Mapping, data migration strategy and extraction rules are set up quickly with the functional team.
Mapping built by hand
Mappings and rules are assembled separately from the functional design.
Configuration read from the environment
Fusion setup is taken directly from each environment.
One load, late
Data is typically loaded as a single version, late in the programme.
Start early, load often
Test data supports design workshops, with multiple cycles on top of data already loaded.

This keeps data migration on track through design changes, missing rules and new transactional mappings.

Sources and load methods

Extract from

  • Oracle E-Business Suite, through a pre-built adapter
  • Database links
  • REST API services
  • CSV files with any delimiter
  • Excel and XML files
  • Oracle Data Pump import

Load into

  • Oracle Fusion Cloud through FBDI and HDL files
  • Oracle Fusion Cloud through REST APIs, where applicable
  • Other target systems through generated files
  • Several environments from the same rule set
  • Incremental file generation and loading
  • Version control to track every change

Inbound channels into Oracle Fusion

Data Migration does not replace Oracle’s load mechanisms. It prepares, validates and reconciles data around them.

ChannelBest forWhat Data Migration adds
HDL (.dat files)High-volume migration and recurring integration across complex object hierarchiesGenerates and loads HDL files from mapped, validated data; reconciles results against source
HSDL (spreadsheet)Business-user mass maintenance on a defined subset of objectsExcel-based preparation with validation before load
FBDIBulk loading of finance, procurement and project dataGenerates FBDI files and reconciles loaded records
REST and SOAP APIsReal-time, per-record integrationLoads objects through REST where applicable

Clear scope

Data Migration focuses on data readiness, migration and reconciliation. Oracle’s platform tools remain the system of record for mastering and runtime propagation.

DMOne™ platform acceleratesOracle native tools lead
Legacy extraction, cleansing, mapping and transformationEnterprise data mastering and governance (EDMCS)
Inbound load orchestration and reconciliation over HDL, HSDL and FBDIRuntime outbound propagation (HCM Extracts, BI Publisher, BICC)
Configuration migration (ConfigIQ™) and data archival (ArchiveIQ™)Operational and enterprise analytics (OTBI, Oracle Analytics Cloud)

Source and target coverage

Proven patterns are marked. Other coverage is confirmed for each programme during scoping.

SourcesStatus
Oracle EBSProven
Files: Excel, XML, CSVConfirmed per programme
APIs and external systemsConfirmed per programme
Custom tablesConfirmed per programme
Descriptive flexfieldsConfirmed per programme
Oracle Fusion targetsStatus
Fusion ERP objectsProven
Fusion HCM objectsConfirmed per programme
Configuration loadsConfirmed per programme

Proven: delivered on a reference engagement, with 68 data objects migrated from Oracle EBS to Oracle Fusion.

Beyond the initial migration

The same platform supports data work after go-live.

Business-as-usual data change

Onboarding new employees, worker moves, mass updates to employee and project data, and business unit mergers in live Fusion, run by in-house teams without specialist technical skills.

Data profiling

Assessing source data quality ahead of design decisions.

Archiving

Retaining legacy data that is not migrated to Fusion, with ArchiveIQ™.

MDM enablement

Preparing governed master data for master data management initiatives.

Additional transformations

Restructures, acquisitions and data corrections.

Reference results

Results from large UK public sector migrations.

Shared-services organisation

Oracle EBS to Oracle Fusion Cloud, end to end, with built-in reconciliation and audit.

8M+records migrated68data objects50operating units

University

Cleansing and transformation of source data, alongside the SI partner who handled the Fusion load.

3M+records in scope205data objects20+cleansing reports

Object library

Pre-built objects reduce build effort. Objects not listed can be added for a programme.

HCM and Payroll

Workers, work structures, payroll, absence, talent and expenses

Financials

General Ledger, Payables, Receivables and Fixed Assets

Suppliers and customers

Supplier and customer records, sites and contacts

Procurement

Purchase orders, receipts and agreements

Supply chain

Items and inventory

Projects and grants

Projects, budgets, costs, billing and awards

Detailed architecture, object lists and security documentation are available to clients and SI partners on request. Request the architecture pack

Case study: migration followed by system mergers

eAppSys moved a major UK healthcare organisation from Oracle EBS R12 to Oracle Fusion Cloud. The organisation then asked eAppSys to bring separate systems and organisations together on the same platform.

In a merger, source data arrives in different formats, with inconsistent naming and duplicate records across organisations. Data Migration applied cleansing rules first, standardising names and formats so records could be compared like for like. It then matched records in two ways: custom exact-match rules for records that could be merged with certainty, and fuzzy matching with a confidence score for likely duplicates that needed review.

Supplier 100482 and Supplier 100482Exact match, 100%Merged under a custom rule
“Acme Logistics Ltd” and “Acme Logistics Limited”Fuzzy match, 94%Flagged as a likely duplicate for review

Illustrative examples. Every match decision is recorded for audit.

Where it fits

From the first mock load to cutover, and for later rollouts, mergers and business unit consolidations.

For SI partners

Partners use the DMOne™ Data Migration module as the migration tooling on their Fusion programmes, with their own team running loads and eAppSys providing platform support, or ask eAppSys to run the migration workstream.

How the partner model works

Arrange a demonstration of Data Migration

We will demonstrate the module using a scenario from your programme.