Coverting a SharePoint Application to a Multi-Tenant Custom Web Applications

150

Screens. This was a customer of ours who had their core set of applications in SharePoint. It was close to 150 screens. Over multiple tenants with customization within tenants, all that comes default with SharePoint. All the security that came with it.

We helped them build their complete suite into a custom web application using React JS and Node JS hosting it on AWS. The whole project took about 14 months for us to finish and go live with the first tenant. Over a period of 3 months we migrated all their customers into the new platform and it is at a very robust stage adding more tenants making this a high availability application.

150 Screens. This was a customer of ours who had their core set of applications in SharePoint. It was close to 150 screens. Over multiple tenants with customization within tenants, all that comes default with SharePoint. All the security that came with it.

We helped them build their complete suite into a custom web application using React JS and Node JS hosting it on AWS. The whole project took about 14 months for us to finish and go live with the first tenant. Over a period of 3 months we migrated all their customers into the new platform and it is at a very robust stage adding more tenants making this a high availability application.

Design
Our first step was to design application in such a way that single code based can be used for many tenants and a single database also to store and secure the data for all tenants.
Plan
Planning was very crucial for this because we were moving away from sharePoint. A lot of things are taken for granted in sharePoint as they come with the platform. Authentication, Authorization, Always deployed in the cloud, redundancy etc. We had to ensure we plan for everything today and also future ready.
Conceptualize
The next was to build proof of concept and proper frameworks on which we can build the 12S screens rapidly. We built our frameworks on a concept called scaffolding. Build security for both authentication and authorization in the framework. Once that was completed development started.
Develope and deploy
The team was in 3 different places. This forced us to create a lot of automation in the devops to make sum given the different time zones in which development happened, there was not a roadblock because of one team or the other. Testing and Deployment were automated.