SAP HANA Implementation & AWS Cloud Migration
SAP HANA implementation and AWS cloud migration for a footwear manufacturer and retailer, with an automated deployment pipeline and a minimal-disruption cutover.

What changed, and what came of it
CHG Global operates the World Balance footwear brand — it both manufactures and retails, so its SAP estate carries production and sell-through alike. We upgraded it to SAP HANA and migrated the server infrastructure to AWS, with testing, staff training and support through the transition.
Before
The client’s SAP environment was outdated and its server infrastructure costly to run. Capacity was fixed to the hardware it sat on, environments were built by hand, and any change carried enough operational risk that changes were batched and deferred — which made each one larger and riskier than the last.
What we built
We executed a migration of the SAP environment to cloud infrastructure and introduced an automated deployment pipeline. The cutover was planned around a minimal-disruption approach, with the sequence, rollback points and business downtime window agreed before execution.
The client reported a reduction in the cost of running the environment following migration. We do not publish a percentage because we cannot evidence a specific figure.
The migration was planned and executed against a minimal-disruption target, with an agreed downtime window and rollback points.
Change deployment is automated rather than manual, which is what made subsequent changes smaller and more frequent.
Each outcome carries the label that describes what kind of claim it is. We never present a target as a measured result — see the Ledger and our claims policy.
What the system does
- Cloud migrationSAP environment migrated from on-premise hardware to cloud infrastructure.
- Automated deployment pipelineEnvironment and change deployment automated rather than performed by hand.
- Cutover planningSequence, rollback points and downtime window agreed with the business before execution.
- Environment parityNon-production environments built from the same definitions as production.
- Operational handoverRunbooks and documentation handed to the client's own operations team.
- Backup and recoveryBackup regime and recovery objectives re-established on the new platform.
How it fits together
A layer-level view. We do not publish hostnames, addresses, credentials, firewall rules or topology detail for systems in production.
How it is protected, and how it went live
Controls in the delivered system
High-level controls only. Detailed security design is shared under NDA with the client organization, not published.
How it was rolled out
- AssessmentCurrent environment, interfaces and dependencies documented before anything moved.
- Target buildCloud environment built from repeatable definitions, with non-production first.
- Migration and cutoverExecuted to an agreed plan with defined rollback points and a bounded downtime window.
- Stabilisation and handoverPost-migration support, then handover of runbooks and documentation.
Frequently asked questions
A migration, combined with an SAP HANA implementation — the existing environment moved to AWS rather than being rebuilt from scratch. Vendors frequently bundle the two, and separating them is usually what keeps both the risk and the cost down.
Through cutover planning, environment parity between the old and new estates, an automated deployment pipeline, and a defined backup and recovery position before the move. The production-stopping window was bounded and known in advance rather than discovered during the cutover.
Capacity stopped being fixed to the hardware it sat on, environments stopped being built by hand, and a change stopped carrying the operational risk that came from having no reproducible way to rebuild. Operational handover and a documented recovery position were part of the delivery.
It depends on whether the constraints are real for you. The case for moving was outdated infrastructure, fixed capacity and costly servers. Where hardware is recent, capacity is adequate and the environment is already reproducible, the argument is much weaker and worth testing before committing.
Planning a similar project?
Tell us the organization, the process and the constraint you are working against. We can help shape the architecture, the implementation approach and the next step.