I was the technical lead on a project worth $170k to migrate the on-premise Discovery solution to to Helix Discovery SaaS.

This was a significant project as it was the first migration I had been asked to architect, so I had no templates or documentation to work off. I created the SOW, Solution Design and Project Plans. I decided that the best approach was to conduct a gap analysis and then work out what needed to achieved from there. As I had already worked several project with the SaaS platform, I was not totally in the dark.

The SaaS migration in some was would be technically easy because it was about determining what functionality would be decomissioned as it was not avialable in the cloud. However this needed to be carefully navigated with the stakeholders to reassure them that the functionality was either not needed for the SaaS platform, or there would be an alternative method/workaround for them to achieve the same results they got from the on-premise solution.

One of the interesting things turned up from the gap analysis was that they were under-licensed. As well as my company as a partner company being affected, we had a fiscal duty to report this back to the vendor. This did trigger a discussion with the client which was not initially well-recieved.

After many discussioned had taken place at the c-level I was asked for technical input as to whether there was a way they could be brought back into compliance. Fortunately, I did have an inelligant workaround solution which required a slightly more hands on approach to managing the scanning schedules and data collection. It did however provide satisfaction of the client and vendor, allowing the migration to continue successfully.