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 was implemented
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 project
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 ITDC delivered
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.
What the system does
Cloud migration
SAP environment migrated from on-premise hardware to cloud infrastructure.
Automated deployment pipeline
Environment and change deployment automated rather than performed by hand.
Cutover planning
Sequence, rollback points and downtime window agreed with the business before execution.
Environment parity
Non-production environments built from the same definitions as production.
Operational handover
Runbooks and documentation handed to the client's own operations team.
Backup and recovery
Backup 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.
Built with
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
Assessment
Current environment, interfaces and dependencies documented before anything moved.
Target build
Cloud environment built from repeatable definitions, with non-production first.
Migration and cutover
Executed to an agreed plan with defined rollback points and a bounded downtime window.
Stabilisation and handover
Post-migration support, then handover of runbooks and documentation.
What came of it
Each outcome carries the label that describes what kind of claim it is. We never present a target as a measured result — see our claims policy.
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.
The capabilities behind this project
Related projects
Power BI Implementation & Unified Reporting
A Power BI implementation unifying SAP, Salesforce and spreadsheet data into one analytics platform, with standardized dashboards and user training.
InfrastructureNetwork, Security & Command Center Infrastructure
Fiber backbone, structured cabling, firewall, PABX and CCTV across city facilities, with a command center for the CDRRMO.
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.