You can choose from two updating strategies:
Update the databases on the same system as the earlier version. This strategy saves time and hardware resources. After updating to version 3.0.1, you can no longer use the version 2.5 deployment.Side-by-side
On a separate system, create version 2.5 databases. Transfer your existing 2.5 databases to that system and then update the new databases to version 3.0. This strategy requires more time and resources but is a good way to test the update while you continue to use your 2.5 production databases.Note:
You can update databases with the wizard or with the SQL scripts that are provided with the product.
Perform the tasks that apply to your deployment configuration:
Parent topic: Migrating to IBM Connections 3.0.1 from version 2.5
IBM Connections system requirements