Introduction
Understanding organizationsUnderstanding componentsManage organizationsManage componentsManage component Jira integrations
Set up your first organizationUnderstanding users and teamsUnderstanding role-based access controlManage usersManage teamsConfigure role-based access controlRBAC permissions reference
Understanding authentication in CloudBees UnifySet up multifactor authenticationConfigure SAML single sign-onConfigure OIDC authenticationConfigure network security policiesNetwork security reference
Understanding platform configurationUnderstanding environmentsManage properties and secretsManage environmentsTrack environment inventoryConfigure containersSet up preconfigured actionsConfigure notificationsSet up Slack webhook notifications
Accessibility policy referenceShared responsibility model referenceSubscription and services agreementSupport policiesSupported browsers and external tools
Introduction
Understanding feature managementUnderstanding Configuration as CodeGet started with feature managementCreate and manage feature flagsConfigure feature flag targetingOrganize feature flagsImplement feature flag governanceConfiguration as Code reference
Understanding flag impressions and activity statusUnderstanding flag healthUnderstanding code referencesReview and clean up feature flagsSet up code references
Understanding Jira integration for feature flagsSet up the Jira integrationLink Jira tickets to feature flags
Understanding multiple SDK keysBuild your first mobile app with feature flagsBuild your first feature-flagged web applicationBuild your first feature-flagged backend serviceInstall client-side SDKsInstall server-side SDKsConfigure multiple SDK keysMobile SDK referenceWeb SDK referenceBackend SDK referenceClient SDK referenceFlag implementation reference
Introduction
Understanding CI workflowsUnderstanding custom actionsCreate a build workflowCreate a custom actionCreate and manage workflowsCreate reusable workflowsTest and validate containers in workflowsCheck out source codeTrigger workflows remotelyWorkflow syntax referenceJobs syntax referenceSteps syntax referenceServices syntax reference
Monitor workflow runsView test results in runsView evidence in runsView deployments in runsManage workflow artifactsPublish test resultsPublish evidence itemsGenerate a software bill of materialsManage ServiceNow change requests
Configure workflow credentialsConfigure AWS credentialsConfigure container registry credentialsConfigure Git credentialsIntegrate CyberArk Conjur secrets
Understanding GitHub Actions integrationSet up GitHub Actions integrationDisplay GitHub Actions workflows and runsRegister GHA build artifactsPublish GHA deployed artifactsPublish GHA test resultsPublish GHA evidence itemsTrigger CloudBees workflows from GitHub ActionsScan with GitHub Actions
Understanding CloudBees CI and Jenkins® integrationConnect CI and Jenkins controllersMonitor CI and Jenkins buildsRegister CI build artifactsRegister CI deployed artifactsPublish CI test resultsConfigure CI security scanningCI and Jenkins integration reference
Build and publish container imagesUnderstanding external CI/CD integrationsRun external CI/CD jobsExternal CI/CD action reference
Introduction
Understanding release orchestrationManage applicationsCreate deployer workflowsCreate staged workflowsCreate and manage releasesOrchestrate multi-workflow releasesRelease management reference
Understanding artifact managementRegister and track artifactsStore and retrieve artifactsPromote artifactsGenerate a software bill of materialsArtifact management reference
Deploy with HelmDeploy to KubernetesContainer deployment reference
Deploy to AWSAWS deployment reference
Deploy with enterprise platformsExecute remote deployment commandsEnterprise deployment reference
Verify deployments with New RelicDeployment verification reference

Transition from Rollout to CloudBees Unify

5 minute read

This guide is for existing Rollout customers who are migrating to CloudBees Unify after a CloudBees-managed data import. The sections below explain what CloudBees has already done, what to expect during the transition, and the steps you need to complete: sign in, validate your applications, flags, and environments, update your SDK keys, and finish with post-transition clean-up.

Milestone Owner Purpose

Email notice

CloudBees

Email announcement of transition from rollout.io to CloudBees Unify.

Kick-off call

CloudBees and Customer

Confirm timeline, tenant name, and special requirements.

Tenant setup

CloudBees

Provision the new platform tenant.

Initial import

CloudBees

Copy applications, flags, and environments into the new tenant.

  • Existing users are not migrated; tenant admins must re-invite users.

  • SAML/SSO is not migrated; reconfigure SAML in CloudBees Unify. Refer to the NOTE below.

Initial validation

Customer

Sign in and verify that all data migrated correctly.

Transition

Customer

  1. Update client/server SDKs to version 6.x (refer to Install client-side SDKs and Install server-side SDKs). Version 6.x is backward compatible with Rollout, so your existing functionality remains unchanged.

  2. Update your non-production environments by updating the SDK keys so that your applications point to CloudBees Unify instead of rollout.io.

Engage CloudBees on the following:

  • Request CloudBees to conduct a refresh sync (which will sync any new flags created on Rollout and update them on CloudBees Unify).

  • Identify features that you use in Rollout that are either different or not on CloudBees Unify, such as:

    • Specific APIs you depend on.

    • Multi-platform feature flags and experiments.

    • Set granular permissions on environments and applications.

The initial import does not migrate user accounts or SAML/SSO settings. Tenant admins must re-invite users and reconfigure SAML in CloudBees Unify.

Prerequisites

Before validating your feature flags and transitioning to CloudBees Unify, ensure the following:

  • You have received the email notice and scheduled or completed the kick-off call with CloudBees. The call confirms your timeline, tenant name, and any special requirements.

    For any transition questions, email the CloudBees representative who ran your kick-off call and copy rollout-migration@cloudbees.com, so the team can track your request. Open a CloudBees support ticket only if you need an immediate response because your Rollout account is blocked or your production environment is affected.

  • You have received confirmation from CloudBees that your tenant has been created and the initial import has been completed.

  • You can sign in to CloudBees Unify: https://cloudbees.io.

Complete the transition

Follow these steps after CloudBees completes the one-time import:

  1. Sign in to your new tenant using the link provided in the email notice.

  2. Open each imported application and confirm that applications, flags, and environments appear as expected.

    Applications
    Figure 1. Applications
    Flags
    Figure 2. Flags
    Environments
    Figure 3. Environments

  3. Upgrade your client and server SDKs.

    Begin upgrading your server- and client-side SDKs to version 6.x. All 6.x SDKs are backward compatible, so Rollout continues to work during the transition.

  4. Replace your SDK keys.

    Start with your non-production environments and replace your SDK keys in your applications from Rollout to CloudBees Unify.

    To locate the new keys in CloudBees Unify, navigate to Feature management  Flags. By default, All environments is selected in the environment selector, and the SDK key copy links appear in the column headings for each environment (for example, Local, Pre-prod, Sandbox).

    SDK key
    Figure 4. SDK key copy links for each environment

    Update keys in non-production environments first, verify parity, and then change the production keys.

    Configuration as Code (CasC) and migration validation:

    Do not enable CasC integrations until the end of the migration. CloudBees cannot migrate or re-sync applications with CasC enabled.

    If you need a new sync:

    • Disable CasC on the affected applications.

    • Request CloudBees to run the sync.

    • Re-enable CasC only after verification is complete.

  5. Validate flag behavior in a non-production environment:

    1. Toggle a flag on and off.

    2. Check target-group rules.

    3. Verify that SDK evaluations return the expected values.

    4. Proceed to the next non-production environment until you can validate that all of your environments are working as expected.

  6. Recreate or adjust items that were not migrated automatically (for example, new target groups or properties created after the import).

    Request a sync whenever you need CloudBees to refresh CloudBees Unify with new flags you add in Rollout. The transition tool performs a one-way sync from Rollout to CloudBees.

  7. Post-transition clean-up: archive unused flags, rename legacy items, and delete obsolete environments.

FAQ and troubleshooting

Will CloudBees migrate my flags for me?

Yes. A one-time sync is performed by CloudBees. Additional syncs are available upon request.

What if I used secret mode in Rollout?

Secret mode is supported and improved in CloudBees Unify with UI configuration options.

Can I import flags from Rollout automatically?

Flags are imported as part of our transition script. Our transition script includes the transition of applications, feature flags, and environments.

What happens to my old Rollout account?

Your Rollout account stays online in read-only mode during the transition. This gives you time to review settings and compare data. CloudBees will close it once your transition is finished or when Rollout is sunset, whichever comes first. If you need access for a longer period, contact your CloudBees transition representative to discuss options.

What if I have devices that don’t regularly receive SDK updates?

Contact us by sending an email to your primary CloudBees contact who initiated the kick-off with you and copy rollout-migration@cloudbees.com to discuss your options.

How do I set up custom roles?

Refer to Configure role-based access control for details.

Do you support SAML?

If you are currently using SAML on rollout.io or want to set up a new SAML connection, refer to Configure SAML single sign-on.

What CloudBees Unify features can I use after migrating?

You currently have access to all CloudBees Unify features. Limits normally align with the Team tier; refer to CloudBees Unify pricing. More specific questions can be answered by your transition project lead.

What will happen with my flag impressions data on Rollout?

Flag impressions data is not part of the transition process. However, you can export impression data using the Rollout API.

What will happen to my audit history on Rollout?

Rollout history is not part of the transition process.

Although audit history is not officially exportable, an internal API may be available; contact your CloudBees transition project lead for more information.
What happens to my existing integrations?

Integrations (for example, Jira, GitHub Apps, CasC, webhooks) are not migrated automatically. Some must be reauthorized in CloudBees Unify.

Alert your CloudBees transition lead to any specific integrations you rely on.
Will my secret mode settings be migrated automatically?

No. Secret mode settings will not be migrated by default. If you configured secret mode prior to the migration and want to retain those settings in CloudBees Unify, contact your CloudBees transition representative to request this.

How can I identify and remove old flags before transitioning to CloudBees Unify?

Cleaning up unused or outdated flags before migration is not required, but it can simplify the process.

  • Use the flags overview to filter by stale and inactive status and review flags for possible deletion.

  • Use the flags API with the includeFlagStatus=true parameter to review flags by status.

  • Use the impressions API to identify flags that only serve the default value and are not toggling values based on environment or user targeting.

  • Not sure about a flag? Tag it (for example, candidate-for-removal) for review after migration.

Additional resources