Getting PreCise-ly What

They Need With AWS Migration

Cloud Scalability Meets Data Fleet Solutions Provider's Growing Business Demands

 Migration  Modernization  Serverless

Summary

PreCise MRM, which collects fleet data for government organizations, was using on-premises servers to run their application and was looking to modernize their business before a big office move. Cloud303 was able to migrate both of their workloads onto AWS, allowing them to centralize their data and streamline their business.

Industries:
Local Government
Regions: 
NALADEMEAAPAC
AWS Segment: 
EnterpriseSMB

The Challenge

PreCise MRM came to Cloud303 with aging hardware and a co-location lease that was soon to expire. PreCise MRM was also about to make a big office move, so it seemed like the perfect time for them to modernize the way that they were running their business. Moving their workload onto AWS would allow for a much more seamless transition into the new office space.

PreCise MRM needed both of their products, MyFleet and LiGO migrated to the cloud.

Why PreCise MRM Chose Cloud303?

Cloud303 was suggested to PreCise MRM by an AWS representative with the initial discussion focusing on disaster recovery and AWS Well-Architected Framework. Cloud303 is one of AWS’s top partners for disaster recovery deployments and Well-Architected Reviews. From there, remediations were carried out to ensure all PreCise MRM's AWS accounts were in compliance with the AWS Well-Architect Framework. After that, they started to discuss the two migration projects that would need to be done in conjunction with the AWS Elastic Disaster Recovery deployment.

Cloud303's Solution

Cloud303 started the migration process by setting up a DR environment. CloudEndure was used to replicate the on-prem infrastructure to the cloud. That way, if something happened physically during the migration, Cloud303 would be able to quickly bring the client’s workload up inside of AWS. After that, Cloud303 worked closely with Verizon to establish an AWS Site-to-Site VPN to PreCise MRM’s on-premises location. From there Cloud303 proceeded to scope out the size of the instances and the servers that would be needed in AWS. Once everything was set up, Cloud303 started working on the infrastructure in AWS to make sure that all the details would work with Precise MRM’s new setup. Once the infrastructure was set up, Cloud303 migrated PreCise MRM’s MyFleet software to AWS. The migration was successful and took about five hours to complete.

After a few weeks of tweaking the initial migration, Cloud303 migrated LiGO to AWS as well. Using everything they had learned from the first migration, Cloud303 were able to cut the migration time down to two hours. From there, Cloud303 shifted their focus to modernization and other small updates that needed to happen to ensure a seamless transition.

Results/Benefits

Being liberated from a physical setup allowed PreCise MRM to easily modernize their business without being tied to any long-term lease. They’ve been able to centralize, making it easier to access their data from anywhere. They’ve also been able to merge both of their products into one place, making it much easier to organize everything. They’ve been able to more easily manage the cyclical nature of their business (I.e. snowplows in winter).