Migration from Oracle CRM to MS Dynamics 365 CRM (Enterprise CRM)
About the Client:
Client focuses on international student exchange and aid, foreign affairs. Client creates programs of study and training for students, educators, and professionals from various sectors. Client’s vision is a peaceful, equitable world enriched by the international exchange of ideas and greater understanding between people and cultures.
Background:
Client was working with a legacy CRM system which was hampering their new expansion plans. They were looking for a system which seamlessly integrates with all the new age source systems and helps client to scale up their enterprise evolution.
Challenges:
- Complications with third party integrations (Sunapsis, Canvas, CSI watch dog and few more..)
- Enhancement of few specific business process not possible with legacy Oracle CRM
- System was not user friendly
- Legacy system didn’t have an inbuilt document management system
- No options to customize the system
Approach:
- RAS spoke to key stakeholders to find out the business requirements
- RAS put together a team of Business analysts, Project manager and solution architect.
- Fit-Gap analysis – RAS found out which business requirement can fit the new system and where do gaps lie.
- RAS prepared questionnaire on the clarification needed by the client
- Based on client current data infrastructure client wanted to choose MS-Dynamics 365
- Fit- Gap analysis report was submitted (92-96% business requirement fitted the new tool)
- Recommendations were made to enhance the new product so that rest of the requirements can be implemented
- High level architecture design and solution approach documentation was submitted to the client
Solution:
- RAS started the project with the submitting of project timeline estimation, cost and effort, sprint model.
- Agile model was selected for the development
- RAS requested the client for access to their data environment
- RAS identified the features to be implemented and listed them as stories in the user storage (Azure directory ADO)
- RAS identified the list of the entities needed and prepared the entity relationship model, and created a data model.
- RAS identified the integration systems and defined their integration approach
- RAS did the classification on which will be master entities and which will be transactional entities.
- RAS started to create the entities in MS- Dynamics environment, customization and configuration and integration
- Built Data Migration package in parallel to the entity model development
- Customization by using plugins (Jscripts, power automate flows, Azure integration services)
- Integration – Outlook integrations, SharePoint integration, campaign management, sales process development.
- RAS did a custom portal development for participants and partners.
- Test plan and scripts were built
- Build reports and dashboards on Power BI
Outcome:
- Third party integration became easy with the new Dynamics 365 e-CRM.
- Enhancement of the new e-CRM was done to incorporate the business processes.
- Sales and administration team found the final solution to be extremely user friendly.
- A document management system was built into the new Microsoft Dynamics 365 e-CRM