Case study · GCC · Oracle Fusion Cloud
ERP data migration and restructuring for a large public-sector organization in Saudi Arabia
Large public-sector organization · Saudi Arabia · Oracle E-Business Suite to Oracle Fusion Cloud
Five business domains and 25+ Oracle modules migrated to Oracle Fusion Cloud with automated validation, while keeping more than ten critical national and banking integrations alive.
- 5 business domains
- 25+ Oracle modules
- 10+ critical integrations preserved
Context
A large public-sector organization in Saudi Arabia ran its finance, human resources and payroll, supply chain, procurement and enterprise asset management on Oracle E-Business Suite, integrated with national platforms, banks, point-of-sale and hospital systems. The organization was moving to Oracle Fusion Cloud with SAMA Systems, an Oracle implementation partner based in Riyadh.
Challenge
Migrate and restructure the data of five business domains — 25+ modules — into the target Fusion Cloud modules, while keeping more than ten critical integrations alive through the transition: tax authority (ZATCA), social insurance (GOSI), banks, point of sale, hospital information systems, handheld and biometric devices.
My role
Data migration architecture and delivery lead: migration strategy, data analysis and restructuring, validation automation — working alongside SAMA Systems’ Oracle implementation team.
Architecture / approach
A module-by-module migration map from the legacy landscape to the target Fusion Cloud modules; automated extraction, cleansing, mapping and load pipelines with reconciliation at every stage; data-quality analysis before each cutover; repeatable runbooks for every migration wave.
Technology
Oracle E-Business Suite (Financials, HRMS, SCM, Purchasing, EAM); Oracle Fusion Cloud (ERP, HCM, SCM, Procurement, EPM); migration and validation automation; data profiling and reconciliation tooling.
Execution
The landscape was migrated in waves, domain by domain. Each wave followed the same runbook: profile and cleanse the source data, map it to the target structures, load it, reconcile source and target automatically, and validate the integrations before moving on.
Constraints
National scale; integrations with government platforms (ZATCA, GOSI) and banks that could not be interrupted; data restructuring imposed by the new modules; a multi-party program delivered with the partner’s implementation team.
Business impact
Five business domains and 25+ modules mapped and migrated with automated validation instead of manual rework; national and banking integrations preserved through cutover; a migration playbook reused across Oracle programs in the Gulf, including an Oracle Cloud data-residency relocation from Frankfurt to Dubai.
Key takeaways
- Build the migration map before the first pipeline: the target modules define the data restructuring, not the other way around.
- Automated reconciliation at every stage is what makes a national-scale migration auditable.
- A repeatable runbook turns one migration into a playbook for the next program.