Preparation

Preparation phase assures that initial actions in the production installation are completed before real migration begins.

1. Fill in the Requirements checklist in Appendix 1 of this document.
2. Prepare the list of critical functionality / customizations at customer site. This document should be used during the configuration and verification phases.
3. Check the critical functionality. Some functionality may be added/removed/changed in new releases, so check that all of the functionality listed in phase 2 is available in the version to be migrated to.
4. Check the system requirements. System requirement changes should be reviewed well before the migration. For example you should verify the server and client side software version requirements in the Kronodoc 5.0 supported 3^rd party software versions –document.
5. Make backups of the database and the projects-directory. In case the migration cannot be completed, reverting back to using the old installation is not possible without restoring the original data from backups. The database dump done during database migration (see section Database migration) is sufficient for database backup, but the backup of the projects-directory must be separately handled.
6. Make a snapshot of information. For quick identification of migration success or failure make printouts of the:

1. Project list
2. Randomly selected properties (5 documents, 5 folders, 5 comments) in active projects
3. 5 document lists where attached files are visible
4. 5 document history listings

7. Copy installation packages.

1. Kronodoc 5.0 installation
2. Necessary add-ons