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.
- Data ingestion
- Data cleansing
- Data validation
- Data extraction
- Data transformation
- Pre-load reconciliation
- Target data loading
- Post-load reconciliation
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.
Multiple sources, customised systems, custom tables and years of local workarounds are handled through configured connectors and rules, not bespoke scripts.
Duplicates, gaps and values that do not fit the Fusion design are found by profiling and validation before load.
When configuration changes, rules are corrected once and reapplied in the next run, rather than mappings being rebuilt.
Client and delivery teams work on the same data in one place, with no file handoffs between teams.
Representative data is loaded early and often, so it is ready when unit, SIT and UAT testing start.
Data is masked for non-production cycles, so integration and other testing is not held back.
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
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.
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.
Plan it from the first mock load to cutover. Loads are repeatable and version-controlled, and reconciliation reports feed status reporting.
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
A cloud-based module of the DMOne™ Platform, developed by eAppSys, supporting all data migration and data management activities.
Out-of-the-box components for rule-based extraction, transformation, validation, file preparation and reconciliation.
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 model | With 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.
Design
Mappings come from design workshops and the Fusion configuration.
Build
Fusion configuration is read into the module, so data is validated against the current setup.
Unit test
Representative, masked data subsets are loaded as soon as build is ready.
SIT
Managed test cycles, loaded in parallel to separate environments.
UAT and mocks
Full-volume runs with reconciliation evidence.
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.
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.
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.
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.
Source extract
Full or incremental extracts and updates.
Transformation and enrichment
Metadata-driven mappings, copy columns and enrichment rules, configured rather than coded.
Validation and cleanse
Mandatory and lookup validations; deduplication and cleansing that is automated, assisted or user-driven.
Target file generation
Files in each target’s format, for one or several target systems.
Load and error handling
Errors are reported and corrected without restarting the cycle.
Reconciliation and sign-off
Source-to-target reconciliation, signed off by the business.
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
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.
Connect the source
Select the EBS adapter and the Suppliers object.
Map and validate
Review mappings and fix a failed rule in the rule editor.
Environment-specific rules
Apply SIT values without changing the core rule.
Load to Fusion
Generate and submit the load in one action.
Reconcile
Open pre-load and post-load reconciliation.
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.
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
| Today | With 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.
| Channel | Best for | What Data Migration adds |
|---|---|---|
| HDL (.dat files) | High-volume migration and recurring integration across complex object hierarchies | Generates and loads HDL files from mapped, validated data; reconciles results against source |
| HSDL (spreadsheet) | Business-user mass maintenance on a defined subset of objects | Excel-based preparation with validation before load |
| FBDI | Bulk loading of finance, procurement and project data | Generates FBDI files and reconciles loaded records |
| REST and SOAP APIs | Real-time, per-record integration | Loads 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 accelerates | Oracle native tools lead |
|---|---|
| Legacy extraction, cleansing, mapping and transformation | Enterprise data mastering and governance (EDMCS) |
| Inbound load orchestration and reconciliation over HDL, HSDL and FBDI | Runtime 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.
| Sources | Status |
|---|---|
| Oracle EBS | Proven |
| Files: Excel, XML, CSV | Confirmed per programme |
| APIs and external systems | Confirmed per programme |
| Custom tables | Confirmed per programme |
| Descriptive flexfields | Confirmed per programme |
| Oracle Fusion targets | Status |
|---|---|
| Fusion ERP objects | Proven |
| Fusion HCM objects | Confirmed per programme |
| Configuration loads | Confirmed 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.
University
Cleansing and transformation of source data, alongside the SI partner who handled the Fusion load.
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.
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.
Previous stage
Configure: ConfigIQ™Next stage
Protect: MaskIQ™Arrange a demonstration of Data Migration
We will demonstrate the module using a scenario from your programme.