Information systems form the backbone of many organizations today and are vital for their daily activities. For each day these systems grows bigger and more customized to the point where it is heavily integrated in the current platform.
However, eventually the platform grows obsolete and the system itself becomes an obstacle for further development. Then the question arises, how do we upgrade the platform while retaining customizations and data? One answer is data migration which essentially is the process of moving data from one device to another. The problems of data migration becomes evident with extensive and heavily customized systems which effectively lead to the absence of any general guidelines for data migration.
This project attempts to take a first step in finding and testing a set of general migration guidelines that might facilitate the creation of future migration projects. This is achieved using a comparative analysis of the general migration guidelines contra the process of migrating data between different editions of the Microsoft SharePoint framework. The analysis attempts to find out if the general guidelines are general enough for this migration process and leave it to future research to further assess their generality.
This paper will also investigate the importance of using incremental migration and the ability to perform structural change during migration as well as how these issues is handled by the built in migration tool of SharePoint. In the end the general guidelines proved to be sufficient to express the SharePoint migration process and should therefore be used for further research to assess their worth in other projects. In terms of the second issue, the built-in migration tool proved weak in handling either incremental migration nor structural change which is unfortunate due to the benefits these features bring.
Source: Linköping University
Author: Eng, Dennis