...
Once you have decided on migration, an important step is to first familiarize oneself with the new version. The new modular version of openIMIS is expected to be everything that you had with your legacy version of openIMIS and more. All functionality of the original legacy version has been transferred into the new modular version, though what might have changed for you is the interface through which you interact with these modules. i.e. how you enter a family or a claim into the system follows still the same logic but the buttons to Add or Save might have moved to another spot. The new modular version as well allows you more flexibility to modify these interfaces further to your own needs. Therefore while the screens might look different from your legacy version, the functionality remains the same and hence important that you first familiarize yourself with the new modular version and can assure yourself that this version can do the same and more than your legacy version. You can do this by going to the demo server and trying out the different functionalities here: Log In - openIMIS
...
It is possible that you might find certain functionalities missing in the new modular version due to the fact that your implementation might have done some country specific changes to the software that were not contributed back to the openIMIS initiative. The openIMIS initiative has developed the new modular version as a reflection of the legacy version that they maintained in the past years, so in case country developments were not shared back with the Initiative, these changes might not be part of the new modular version. For example, if an additional field with some additional checks was added to the page which captures data of each individual in the legacy version of a country implementation and this was not indicated to the openIMIS initiative, then it will most likely not be present in the current modular version but would need to be re-done in the modular version. Therefore, implementers should be in contact with developers to communicate these needs to make sure that once the migration is complete, the future releases of the new modular version carry their country specific functionality so its available to you as well as other users. The following sub-steps should be followed:
...
You should therefore organize a testing approach within your country implementation. Guidance on testing approaches and steps can be found here that the openIMIS Initiative endorses and can be used as a guide by country implementations. While these are an extensive lists of tests you are encouraged to undertake as many of these functional and non functional test categories as possible.
...
The main difference between the legacy and the modular version, from the point of view of the end user, is the interface. Indeed, colors, fonts, and certain tabs have changed and perhaps some features provide you with more flexibility which might also allow you to enhance your usage of openIMIS. So this would also be a good opportunity for you to review the way in which you are using openIMIS and in that regard also revise the way you want to train or rather retrain users on use of the new modular version of openIMIS. Therefore, an important step in the transition will be to conduct trainings to introduce different end user groups to the new interfaces. This will also mean to consolidating and updating all training material and other documentation beforehand. The following sub-steps hence are useful to have at hand:
...
Once the new modular version is ready to be rolled out and gone through you own teams testing process and subsequent trainning training of respective user groups it would be advisable to introduce the system in steps to allow for a gradual transition. As per your implementation realities it is possible that a one time complete transition and roll out is a better approach. Generally speaking though, it is useful as with any introduction of a new software, a new module or a prototype, to introduce the new solution in steps either geographically or by user groups or other categories that you might find as meaningful in your context. This would allow for gradual introduction and resolution of issues if they come up as well easier roll back that impacts lesser part of your operations in case of any major issues that you might observe.
...