Once you are running version 4.1.x, use the standard upgrade process for Alfresco to upgrade to 5.2, and then when the Alfresco installation is upgraded, you can apply the new AMP files for Alfresco Records Management 2.5.
- Ensure that your current Records Management production environment is running an Alfresco version that is supported for upgrading.
- Download Alfresco Version 5.2 and the Records Management AMP zip from the Support Portal.
Upgrade to Alfresco 5.2.
For more information about upgrading Alfresco One, see Upgrading Alfresco.
You can start the Alfresco server at this point to verify that the upgrade was successful.
Apply the Alfresco Records Management 2.5 to the upgraded
Follow the instructions in Applying the Records Management AMP files.Note: If you have easy access records (previously know as in-place records) that are pre-184.108.40.206 versions of Records Management, then you also need to run a webscript so that easy access records created in pre-220.127.116.11 sites are shown in the search results of users without Records Management permissions.
- Restart the Alfresco server, if it is already running.
- Log in to Share to view the Records Management data.
When you upgrade from a previous version of Records Management to the Alfresco Records Management 2.5 install, any existing Records Management data is preserved (it is 'patched' in the same way as updated data in the server). The File Plan structures will appear as they did in 1.0 and the previous Records Management site is migrated. Therefore, you do not need to create the Records Management site again.
From Records Management 2.0 onwards you cannot create a record series; instead you create a record category with no retention schedule. The record series is retained as a deprecated model construct to be used when migrating existing record series from a 1.0 installation. This means that any previously created record series will appear and behave as record categories in 2.2, but will be of the deprecated type record series (directly extended from record category). If any custom data was defined for record series in 1.0, this will still appear in the Records Management site, but only for the migrated record series.
Note also that any pre-configured saved searches from your previous version are not available after an upgrade.