Migrating SaaS Product to Elastic Cloud Infrastructure Case Study

The Client

Client is the leading provider of performance-centered Business Intelligence solutions to world-class collision repairers and their associated business stakeholders.

The Challenge

The client needed to migrate their existing software as a service (SaaS) collision repair system from a single server to elastic cloud infrastructure in order to allow further growth and continue adding features to the product. Additionally, the client wasn’t happy with their original infrastructure support team who weren’t properly documenting solutions making it hard to properly manage their product.

Their product is a huge enterprise solution which included a mix of different technologies ranging from SSIS, SSRS, WCF, Website, Window Services, SQL Jobs, Shell scripts and VB scripts.

The Optimus team had to migrate the existing setup to cloud infrastructure without affecting the large number of client body shops from where data is being pulled and without losing any data in the process.

The team had to learn how the application worked and how it communicated with clients to migrate it without losing data.

As the application has a large number of existing customers with predefined DNS mappings, Optimus needed account for the time it takes for DNS mapping to propagate across the Web.

The Process

  1. Study application and propose migration strategy.
  2. Simulate migration on local and production systems.
  3. Perform migration and test the solution.
  4. Maintain and support the infrastructure in an ongoing manner.

How Optimus Helped

Optimus studied the entire system and the various applications and the data flows between different systems and came up with a checklist detailing steps required to migrate to the cloud.

After examining their system, Optimus proposed a new cloud infrastructure and configuration that met their needs and would avoid current bottlenecks and improve the overall performance of the new system.

To make sure that all of the data communication workflows remains intact in the new production server, Optimus created a dummy environment in local servers and simulated the migration verifying that the prototype solution worked. We then simulated the same steps in the production server.

To minimize down time, Optimus performed the migration over the weekend  when  usage is at its lowest. We setup the system on the first day of weekend. On the second day, we changed the DNS mappings and performed the final round of testing when the DNS mapped to the new system.

The project is under a regular support and enhancement phase. The client is happy with the results and has offloaded all of the technical maintenance and support work to Optimus.

Optimus is providing visibility through daily updates, weekly meetings and status reports as well is complete access to project and technical documentation which is giving them better control over their infrastructure, product and IT costs.