Migrate from CI insights to Continuous integration

Last Reviewed:2026-05-13()
3 minute readKnowledge base

Issue

The CI insights integration type has been removed from the CloudBees Unify UI as of CloudBees CI version 2.555.2.36753. If you previously connected CloudBees CI or Jenkins® to CloudBees Unify using this integration type, you must migrate to the Continuous integration type. This migration consolidates how CloudBees CI sends data to CloudBees Unify into a single, more secure integration.

All CI data, including controller metrics, system health, and plugin information, now flows through a single Continuous integration, which also handles CloudBees CI and Jenkins build data and test results. This also simplifies authentication, consolidating from a separate access key for CI insights plus a key pair for Continuous integration down to a single key pair for all data flows.

Historical CI insights data is not migrated to the new integration. The CI insights integration remains accessible in CloudBees Unify for up to three months, so you can still view historical data after migration. The new integration starts collecting data from the point of setup; if you select Collect historical insights data during setup, it also sends all jobs and the last 100 executions per job. Once the new integration is configured, the CI insights plugin automatically stops sending data to CloudBees Unify.

Environment

Resolution

CloudBees Unify does not support automatic migration. Migrating requires installing the required plugins, setting up the new integration, and then uninstalling the old plugin once the new integration is confirmed working.

The CI insights plugin continues sending data to CloudBees Unify until the new Continuous integration is configured, so there is no gap in data collection during migration.

To migrate from the CI insights integration:

  1. Upgrade CloudBees CI to version 2.555.2.36753 or later.

  2. Install the required plugins:

  3. Set up a new Continuous integration in CloudBees Unify. For full instructions for both single-controller and multi-controller setups, refer to Get started with CloudBees CI / Jenkins® and CloudBees Unify.

    When approving the connection in your controller or operations center, you can optionally select Collect historical insights data to send all jobs and the last 100 executions per job to CloudBees Unify.

    Collecting historical data may cause a temporary performance impact on controllers with a large number of historical build records.

  4. Confirm the new Continuous integration is connected and data is populating in CloudBees Unify.

  5. Uninstall the CloudBees Platform Insights plugin from each controller:

    1. From the controller dashboard, select in the upper-right corner to navigate to the Manage Jenkins page.

    2. Select Plugins  Installed plugins.

    3. Search for CloudBees Platform Insights and select to the right of the plugin.

    4. When prompted, select Yes to uninstall the plugin.

    5. Restart the controller.

  6. Delete the old CI insights integration for each controller in CloudBees Unify.

    Deleting the old CI insights integration removes access to historical CI insights data in CloudBees Unify. If you want to retain access to historical data, wait until it is no longer needed before deleting. .. Navigate to Configurations  Integrations. .. Locate the CI insights integration for the migrated controller. .. Select , and then select Delete integration.
This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.