Migration of Legacy SVN CMS Profile

1. Configure your Subversion servers for CMS-Type Subversion in the CMS section of PKitConfig.xml.
2. Ensure no files are checked out in Stages for the legacy SVN profiles at the time of migration. To create a list of currently checked out SVN files execute the following commands on the Stages server in a shell with administrative permissions.
   1. cd [STAGES_INSTALL_DIR]\stages
   2. bin\listCheckouts.bat SVN

1. Before migrating all existing SVN CMS profiles to Subversion CMS profiles, please review all changes that will be done by the migration script. Therefore execute a dry run of the migration script on the Stages server in a shell with administrative permissions.
   1. cd [STAGES_INSTALL_DIR]\stages
   2. bin\migrateSubversion.bat system show > migration.log 2>&1
2. If the migration dry run was successful, please execute the following commands to actually do the migration.
   1. cd [STAGES_INSTALL_DIR]\stages
   2. bin\migrateSubversion.bat system write > migration.log 2>&1

When all legacy SVN CM profiles are migrated the following clean up steps are recommended:

1. Delete the local SVN sandboxes on the Stages server as they are no longer needed. The file system location is defined in PKitConfig.xml in element

<cms-type name=”SVN” ...>
 ...
 <cms-property name="sandboxDirectory" value="[DIRECTORY_PATH]"/>
 ...
</cms-type>

2. To prevent Stages users from creating legacy SVN CMS profiles, please delete the configuration for the legacy SVN interface in PKitConfig.xml. Delete the

<cms-type name=”SVN” ...>
 ...
</cms-type>

3. Restart Stages for the configuration changes take effect.