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.