Enterprise · CHG Global (World Balance Philippines)

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.

Cost savings reported by the clientMeasured Result
Minimal-disruption cutoverTarget
Automated deployment pipelineMeasured Result
Illustration: a factory and a delivery truck connected to a cloud, with a database, a report and a boxed sneaker.
The project

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.

Measured Result
Cost savings reported by the client

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.

Target
Minimal-disruption cutover

The migration was planned and executed against a minimal-disruption target, with an agreed downtime window and rollback points.

Measured Result
Automated deployment pipeline

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.

The system

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.
Architecture

How it fits together

A layer-level view. We do not publish hostnames, addresses, credentials, firewall rules or topology detail for systems in production.

Business
SAP application usersReporting consumers
Application
SAP environmentIntegration interfaces
Platform
Cloud computeCloud storageAutomated deployment pipeline
Operations
MonitoringBackup & recoveryEnvironment definitions
Security and rollout

How it is protected, and how it went live

Controls in the delivered system

Delivered under ITDC’s information security practices, which follow ISO/IEC 27001 and NIST guidance.
Separate credentials and access boundaries for development, staging and production environments.
Encryption in transit and at rest as provided by the cloud platform.
Backup regime and recovery objectives re-established and tested on the new platform.
Access to the deployment pipeline controlled and audited.
Documentation and runbooks handed to the client so operation does not depend on the contractor.

High-level controls only. Detailed security design is shared under NDA with the client organization, not published.

How it was rolled out

  1. AssessmentCurrent environment, interfaces and dependencies documented before anything moved.
  2. Target buildCloud environment built from repeatable definitions, with non-production first.
  3. Migration and cutoverExecuted to an agreed plan with defined rollback points and a bounded downtime window.
  4. Stabilisation and handoverPost-migration support, then handover of runbooks and documentation.
Questions

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.

Let's talk

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.