How a Chennai Logistics Company Migrated to AWS and Cut IT Infrastructure Costs by 42%

Anish Pandey · 2026-01-20 · 10 min read

SwiftMove Logistics is a 150-employee third-party logistics (3PL) company based in Chennai managing warehouse operations, fleet tracking, and client billing across Tamil Nadu and Andhra Pradesh. In 2024, their IT infrastructure was a mix of HP ProLiant servers bought in 2018, a rack in the corner of the Chennai warehouse that nobody wanted to be responsible for, and an IT support contract that cost ₹45,000 per month with an SLA that delivered next-day resolution — which in logistics, where a billing system going down at 5 PM means delayed truck dispatches, is unacceptable. The migration to AWS took 14 weeks and the results are documented in this article.

The Hidden Cost of On-Premise Servers

SwiftMove's initial instinct was that their on-premise servers were 'cheaper' than cloud because they had already paid for them. This is the most common misconception in IT procurement. The true cost of on-premise infrastructure includes hardware depreciation (the 2018 servers had 18 months of useful life remaining and then needed ₹15 to ₹20 lakh in replacement hardware), power and cooling (a modest server rack consumes approximately 3 kW continuously — at Chennai's commercial electricity rate of ₹7.50 per unit, that is ₹16,200 per month in electricity alone), the IT support contract (₹45,000 per month), and the cost of unplanned downtime. SwiftMove tracked three major server incidents in 2023, totalling 19 hours of downtime at a cost they estimated at ₹2,800 per hour in delayed billing and driver overtime — ₹53,200 in total.

What AWS Replaced and How

SwiftMove's workloads were assessed and categorised into four migration groups. The billing and dispatch system (a custom application built on PHP and MySQL) was migrated to EC2 instances (two t3.large instances in active-passive configuration) with RDS MySQL Multi-AZ for the database — the Multi-AZ setup means the database automatically fails over to a standby in a different Availability Zone if the primary fails, with no manual intervention. The fleet tracking system was migrated to EC2 t3.medium with higher IOPS storage for the GPS data stream. Internal tools (HR, email, file storage) were moved to AWS WorkMail and S3, replacing the on-premise file server. The warehouse management system, which was already a SaaS product, simply continued as-is — the migration from on-premise did not affect it.

The Migration Process: 14 Weeks From Assessment to Go-Live

our team ran the migration in four phases. Phase 1 (weeks 1–3) was assessment and architecture design: documenting every workload, its dependencies, its performance requirements, and the target AWS services. Phase 2 (weeks 4–7) was environment setup and testing: building the AWS environment in parallel with the existing on-premise setup, migrating data, and testing the application on AWS against the production database (using a recent backup). Phase 3 (weeks 8–11) was the parallel run: both environments running simultaneously, with SwiftMove's team using both and comparing outputs. Phase 4 (weeks 12–14) was cutover and decommission: DNS cutover to AWS, monitoring, and then decommissioning the on-premise servers. The cutover happened on a Sunday at 2 AM to minimise business impact.

The Cost Comparison: On-Premise vs AWS

SwiftMove's fully-loaded on-premise IT infrastructure cost was ₹3.22 lakh per month: ₹45,000 (IT support contract) + ₹16,200 (electricity) + ₹18,000 (hardware depreciation pro-rated over remaining useful life) + ₹38,000 (hardware insurance and data centre colocation fees they were paying for the disaster recovery server at a third-party data centre) + ₹90,000 (salary and overhead for the part-time IT administrator) + ₹15,000 (miscellaneous licences and renewals). The AWS monthly bill for their workloads is ₹1.87 lakh per month — EC2 instances on a 1-year Reserved Instance contract (approximately 30% cheaper than on-demand), RDS Multi-AZ, S3 storage, and CloudFront for the external customer portal. Net saving: ₹1.35 lakh per month, or ₹16.2 lakh per year.

Reliability: The Metric That Mattered Most

In the 11 months since the AWS migration, SwiftMove has had zero unplanned system outages. The billing and dispatch system has had three AWS maintenance events (pre-announced, during off-peak hours) and one Availability Zone degradation event — which the Multi-AZ database handled automatically with no user-visible impact. Downtime in the 11 months post-migration: 0 hours. Downtime in the 12 months pre-migration: 19 hours. The operations director at SwiftMove put it simply: the AWS migration was the best IT decision the company had made in five years, and its value was not primarily the cost saving — it was that the billing system simply works now, every day, including peak periods like Diwali season when their dispatch volumes are 3x normal.

What to Expect From an AWS Migration for Your Business

Every migration is different based on the age of your applications, the complexity of your data, and your team's readiness for cloud operations. The most common mistakes in Indian SMB cloud migrations are under-resourcing the assessment phase (which leads to unexpected costs post-migration), migrating to the cloud without optimising (lift-and-shift of an inefficient on-premise setup creates an expensive and inefficient cloud setup), and not negotiating Reserved Instances (on-demand AWS pricing is significantly more expensive than 1-year or 3-year reserved pricing for stable workloads). our team is an AWS Partner with certified architects who have completed migrations for manufacturing, logistics, healthcare, and financial services companies. We provide a free migration assessment that includes a total-cost comparison of your current infrastructure versus AWS.

Conclusion

The decision to migrate to AWS should be made on economics and reliability, not on ideology about cloud versus on-premise. For SwiftMove, the economics were clear once the full cost of on-premise was visible. The reliability improvement was an added benefit they did not quantify beforehand but now consider the most important outcome. If your business is running on servers that are more than 3 years old, or if you have experienced downtime that directly impacted operations, the migration conversation is worth having. The assessment is free, the numbers are objective, and the decision becomes straightforward.

Topics: AWS, Cloud Migration, Data Center, Logistics IT, Cloud Cost Savings, Chennai, India