= Theme Migration
This process can be used to transform the existing Theme data of the old ADITO 5.0 implementation of the topic tree to the new datastructure to 
make the data work with the current implementation.
The original data keeps unchanged, this process doesn't delete anything!

This process migrates to things:
1. the HISTORY_THEME datasets to TOPICTREERELATION datasets
2. the THEME datasets to TOPICTREE datasets

1: The datastructe hasn't changed much, only difference being, that TOPICTREERELATION allows to link topics to more than just activities (object_type get's set accordingly)
2: the topicTree sorting functions a little different before (6 sorting columns, the last one that's filled has to be the relevant one)
    topics are still assigned another topic above it using  a column called ASSIGNEDTO.
    Little example to make the whole thing more understandable:
    TopicA:              SORTING_LAYER_1: 1;                                            ASSIGNEDTO: null
        TopicAA:                            SORTING_LAYER_2: 1;                         ASSIGNEDTO: topicTreeIdOfTopicA
        TopicAB:                            SORTING_LAYER_2: 2;                         ASSIGNEDTO: topicTreeIdOfTopicA
        TopicAC:                            SORTING_LAYER_2: 3;                         ASSIGNEDTO: topicTreeIdOfTopicA
                TopicACA:                                       SORTING_LAYER_3: 1;     ASSIGNEDTO: topicTreeIdOfTopicAC
        TopicAD:                            SORTING_LAYER_2: 4;                         ASSIGNEDTO: topicTreeIdOfTopicA
    TopicB:              SORTING_LAYER_1: 2;                                            ASSIGNEDTO: null
    TopicC:              SORTING_LAYER_1: 3;                                            ASSIGNEDTO: null
        TopicCA:                            SORTING_LAYER_2: 1;                         ASSIGNEDTO: topicTreeIdOfTopicC

    KIND, REMINDER, REMINDER_SUBJECT, REMINDER_GROUP, REMINDER_ROLES, REMINDER_SILENT are all columns for functionality that's not (yet?) implemented, so those don't get migrated
    -> altough it shouldn't be a problem to migrate them in the future, since no uuids get changed by this process