Case Study · Manufacturing / Cloud Migration · SAP on Oracle
Lifting FRESH’s SAP database off legacy iron — from POWER to AWS
How Khwarizm re-platformed FRESH Home Appliances’ Oracle Database behind SAP — capacity-planned from POWER to Intel to AWS — then added Oracle Data Guard on AWS so the platform stays resilient in the cloud.
FRESH is one of the top home-appliance manufacturers in the Egyptian market — and, like its closest competitor, it runs its business on SAP over Oracle Database. As the business grew, the platform underneath SAP had to grow with it: off aging proprietary hardware, onto modern infrastructure, and eventually into the cloud — without ever putting the SAP system that runs the company at risk. FRESH chose Khwarizm to plan and carry out that journey, and then to make the result resilient.
Two rivals, one trusted database partner
Among the top five home-appliance manufacturers in Egypt, the two dominant competitors both settled on the same three things: SAP, a relentless focus on customer satisfaction, and Khwarizm Consulting as the team behind their Oracle databases. FRESH is one of those two — and its SAP-on-Oracle platform is the system of record for manufacturing, distribution, and sales.
When the database that carries SAP is the database that carries the business, every platform move is a high-stakes move.
From POWER to Intel — right-sizing the platform
The starting point was proprietary POWER hardware. Rather than simply buy the next big box, Khwarizm did the disciplined work first: capacity planning and sizing — measuring the real workload SAP placed on Oracle, then designing the target platform to fit it. That analysis let FRESH move its Oracle Database from POWER onto commodity Intel infrastructure with confidence that performance would hold and headroom would be there.
…then to AWS
With the workload properly understood, the next step was the cloud. Khwarizm planned and executed the move of FRESH’s Oracle Database onto AWS — turning a fixed hardware estate into elastic cloud infrastructure, and giving FRESH a platform it could scale with demand rather than re-buy every few years.
Three weeks planned — six hours delivered
The cutover itself is where the risk concentrates, and where the plan is tested. SAP and its implementation partners scoped it conservatively: a roughly three-week window in which the system would be offline or read-only while the database was moved. For a business that runs on SAP, three weeks of read-only is a serious cost.
Khwarizm closed that window to a single overnight run — about six hours, over a weekend. The precise capacity planning and a carefully rehearsed migration meant the team could take the platform down after hours and hand it back the same night, migrated and verified. The business left on the old platform and returned to the new one, with the offline period measured in hours rather than weeks.
Resilience with Oracle Data Guard on AWS
A production database in the cloud still needs a disaster-recovery answer. At a later stage, FRESH chose Khwarizm again — this time to implement Oracle Data Guard over AWS, maintaining a synchronized standby of the SAP database so that a failure in one place does not take the business down. The platform that had been re-based and moved to the cloud was now also protected in it.
Khwarizm sized our SAP database properly, moved it off legacy hardware and into AWS, and then made it resilient with Data Guard — every step planned, and every step without disrupting the business.
Why it matters
Re-platforming the database under a live SAP system is one of the riskiest things an enterprise can do — and doing it in stages, from proprietary hardware to Intel to AWS, multiplies the places it can go wrong. FRESH ran that journey without losing the platform that runs its factories and sales, because each step started with engineering: measure the workload, size the target, prove it, then move. That is the difference between a migration that modernizes the business and one that merely relocates the risk.
The results
FRESH’s SAP platform now runs on cloud infrastructure that was sized to its real workload and protected by a Data Guard standby — the product of a staged, engineered migration from POWER to Intel to AWS, delivered in a single overnight cutover where weeks had been expected. For a manufacturer whose operations depend on SAP every day, the win is quiet but complete: the same business, on a modern, resilient, cloud-based database.