Hi Andres,
the linked technote suggests an in-place upgrade from 5.0 to 6.5 (or 7.0).
Anyway, due to the "very old release" I would recommend a side-by-side migration. That means:
1. Install Connections 7.0
2. Implement customizations
3. Perform tests and verify add-ons like ProjExec ... if ProjExec already supports Connections 7.0 you have to check with your contact at Trilog Group
4. Test a data migration side-by-side, which includes (on high level)
- Backup Conn70 databases / Backup shared data directory in target environment
- Data export from Conn50 database source environment and import into target environment using dbt, see https://help.hcltechsw.com/connections/v6/admin/migrate/t_update_databases_side-by-side.html
(NOTE: You have to drop the Conn70 databases and create new one using the database scripts for Conn50 databases, depending on your CR-level of your current Conn50 environment you have to apply the database update scripts as well)
- Database schema upgrade from Conn50 schema level to Conn70 (using Connections database wizard or manually by executing all db schema upgrade scripts up to Conn70: Conn50 CRx -> Conn55 -> Conn55CR3 -> Conn60 -> Conn60CR6 -> Conn65CR1 -> Conn70)
- Data migration from shared data (see https://help.hcltechsw.com/connections/v6/admin/migrate/t_copy_content-store.html
- Post migration tasks (https://help.hcltechsw.com/connections/v6/admin/migrate/t_post-migration_tasks.html)
- Test Connections 7.0 installation with the migrated and upgraded databases (and imported shared data)
5. If all tests are successful and you have a complete migration plan, perform the final productive migration
So, from my experience it is not required to install a complete Connections 5.5 / 6.0 / 6.5 environment to tests interim migration steps. But upgrading such a "very old release" requires a lot of planning up-front ... as you have consider a lot of changes and upgrade steps.
Maik