Migrating and updating

Migrate HCL Connections and its supporting software to the latest release and then update the installation with the latest deployment, interim fixes, or Cumulative Refresh (CR). Refer to the What's New in HCL Connections to review the latest new features in a release, gather download links, look over the latest fix list and update strategy information. HCL Connections supports upgrading to Connections 7.0 from 6.5 CR1. If you are on a release prior to 6.5, refer to the Knowledge Article, Road map for Upgrading Connections, for guidance on first upgrading to 6.5. You will then need to apply 6.5 CR1 and then can proceed with upgrading to 7.0.


The only supported migration strategy is a multi-stage process that requires setting up a new environment that mirrors production, upgrading and validating that environment, and migrating production data before routing client traffic to the new environment. Specifically, administrators will need to:

  • Set up a new production staging environment that mirrors the live production environment. Ensure that the environment is sized appropriately as this will be the new production deployment, and adjust resources as needed. Specifically, all product versions need to initially be the same as production.
  • Perform an in-place upgrade of the new production staging environment.
  • Implement any configuration changes and customizations.
  • Validate product functionality.
  • Take the live production deployment offline to migrate data during a scheduled maintenance window.
  • Migrate data to the new environment and perform any necessary database updates.
  • Evaluate data integrity in the new environment now that production data is migrated.
  • Complete any remaining post-migration tasks.
Important: If Feature Foundation is included in your HCL Connections 7.0 installation then both Rollback and Uninstall will fail in the IBM Installation Manager. Make sure you have a full backup of the Connections server before upgrading. Refer to Backing up HCL Connections for details. You can use this backup to restore your existing deployment if the migration or update fails.