Introduction
In Skolon, a source system migration means that the system which provisions Skolon with users, classes, and groups is replaced with a new one.
When a migration is carried out, all users will keep their existing user accounts in Skolon and, therefore, also keep the accounts for any digital tools they have used through Skolon. Note that new classes and teaching groups are created during a migration. This means that license assignments that were made to classes and/or teaching groups from the previous source will disappear.
The migration is carried out in 5 steps:
Startup
Synchronization to a test environment
Validation of data in the test environment
New sync is activated in the production environment
Verification and validation
1. Startup
During startup, we collaboratively map the user data that is synchronized from the existing sync and compare it with the user data in the new source system. The purpose is to ensure that the user attributes required to perform the migration are available. The most important attributes we look at are:
Complete user data for the Skolon platform (users, classes, and groups)
A unique identifier between the old and new source systems
Attributes required for authentication with IDP are available
2. Synchronization to a Test Environment
The new source system is configured to send user data to Skolon's test environment. When users, classes, and groups have been synchronized, the customer verifies and validates that the data looks correct from the new sync source.
3. Validation of Data in the Test Environment
Once the new sync is set up in the test environment, the customer needs to validate the data based on two different outputs:
A validation export for the entire organization in the test environment
Validation of user mapping between the production and test environments
3.1 Validation Export from the Test Environment
The customer receives an export file from the validation function in the test environment. The validation file contains all the data synchronized to the test environment from the new sync.
3.2 Validation of User Mapping
Skolon performs user mapping between user accounts in the:
Production environment, i.e., the existing source system
Test environment, i.e., the new source system to be migrated to
The user mapping results in a list of users who have not been mapped between the existing and new source systems. Skolon sends this list of unmapped users to the customer. The customer then verifies that all accounts to be managed by the new sync are correct. A decision on how to handle accounts not managed by the new sync is made in step 5.
4. New Sync is Activated in the Production Environment
Skolon makes a change where the new source system is connected as the provisioning source to Skolon's production environment. The new source system runs synchronization against the production environment and then manages user accounts, classes, and groups in the customer's environment.
Note that new classes and teaching groups are created during a migration, which means that license assignments made to classes and/or teaching groups from the previous source are lost. If tool group assignments were made, these can be migrated, provided that the group names are identical from the new source.
5. Verification and Validation
The customer verifies and validates synchronization against the production environment based on these instructions. After verification and validation, the customer needs to decide what to do with:
Old user accounts that are no longer managed by the new sync
Old classes and groups that were created by the previous sync
Skolon's recommendation is to delete all old user accounts, classes, and groups that are no longer managed by a sync.
Questions or Concerns?
Contact your Customer Lead or our support — we'd be happy to help!