Moving core server workloads from on-premises infrastructure to AWS

The challenge

Data Steels needed to move core server workloads from an on-premises environment to AWS without breaking the business processes that depended on those systems. The migration had to account for application dependencies, access patterns, data transfer, user connectivity and the continued use of QuickBooks by the finance team. Because the local site would remain operational during and after the transition, this was a hybrid-infrastructure project rather than a simple server copy. Connectivity between the site and AWS needed clear routing, controlled access and an operating model that the team could support after cutover. The project also required a practical rollback path so that individual workloads could move in stages instead of placing the whole business on a single migration event.

What we delivered

## Discovery and migration planning We began by mapping the server workloads, the people and systems that depended on them, and the network paths required after migration. The plan separated preparation, replication, validation and cutover so that each workload could be assessed on its own risk and dependency profile. ## AWS environment and secure connectivity We established and managed the AWS infrastructure needed for the migrated workloads. A site-to-site VPN connected the on-premises location to AWS, allowing authorised users and remaining local services to communicate with the cloud environment through controlled private routes. Route validation, tunnel monitoring and documented ownership were treated as operational requirements rather than one-time configuration. ## Staged workload transition Workloads were moved in stages with validation at each boundary. The approach covered data transfer, service testing, user access checks and cutover coordination. This reduced the number of variables changing at once and kept recovery options available throughout the migration. ## QuickBooks ERP enablement and support The infrastructure work was coordinated with implementation and support for the team's QuickBooks-based ERP workflow. That meant checking application reachability and user access as part of the infrastructure acceptance process, rather than considering the server migration complete when instances merely started in AWS. ## Ongoing management After migration, the engagement continued around AWS management, VPN support and the operational needs of the server environment. Documentation and clear support boundaries gave the team a maintainable hybrid setup instead of an undocumented collection of cloud resources.

Outcome

The project established an AWS-hosted environment for the selected server workloads while preserving secure connectivity with the Data Steels site. The staged approach allowed infrastructure and business-system checks to happen together, with the QuickBooks workflow included in acceptance and support. The resulting platform gave Data Steels a clearer foundation for server management, remote access and future cloud changes. The site-to-site VPN retained a controlled path to systems that remained on premises, while operational documentation made routing, access and support responsibilities easier to understand. No unsupported performance, savings or availability figures are claimed for this engagement. The value delivered was a controlled move to AWS, continuity for the business systems involved and an environment that could be managed after the migration event.

Technology and platforms

• AWS
• Site-to-site VPN
• On-premises infrastructure
• QuickBooks ERP