---
title: "Upgrade server"
description: "\"This document lists the steps required to upgrade a CircleCI server v4.7 installation.\""
platform: "Server"
doc_version: "Server 4.7"
last_updated: "2026-09-28"
---

> For current CircleCI product defaults, deprecated patterns, and Cloud/Server differences, see [AGENTS.md](https://circleci.com/docs/AGENTS.md).
>
> For the complete documentation index and site structure, see [llms.txt](https://circleci.com/docs/llms.txt).

# Upgrade server

This page describes the steps needed to upgrade your CircleCI Server installation to v4.7.

## Upgrade paths

Our general recommendation is not to skip releases when upgrading. However, we validated that **you can seamlessly upgrade directly from server 4.3, 4.4, 4.5 and 4.6 to server 4.7**. While future version skips may not be tested by CircleCI, this ensures a clear path to adopt server 4.7 and stay on a newly supported version.

We recommend that you **do not** skip releases when upgrading, however some patch releases can be skipped. Your upgrade path will depend on your current version, and the currently available version releases.

When upgrading from one minor version to the next, ensure your upgrade path includes the last patch release for your current minor version.

To see some common upgrade path options, see [this support article](https://support.circleci.com/hc/en-us/articles/15819961443483-Server-4-x-Upgrade-Path).

## Recommendations

We have moved away from Vault to Tink for encryption. The process for migration is [documented here](https://github.com/CircleCI-Public/server-scripts/tree/main/vault-to-tink). The migration includes a convenience script to move existing secrets.

If you are using Vault, complete the migration to Tink on your current installation. Complete this migration before backing up your server in preparation for upgrading to 4.7.

Customers that do not perform this step may have issues restoring Vault from backup in 4.7.

## Prerequisites

*   Ensure you have access to the Kubernetes cluster in which server is installed.
    
*   Ensure you have set up [Backup and Restore](https://circleci.com/docs/server-admin/server-4.7/operator/backup-and-restore/).
    
*   Ensure there is a recent backup. For more information, see the [Backup and Restore](https://circleci.com/docs/server-admin/server-4.7/operator/backup-and-restore/#creating-backups) guide.
    

## Upgrade steps

1.  Ensure your cluster is running a compatible Kubernetes version for this release (1.31 - 1.33).
    
2.  Check the [changelog](https://circleci.com/server/changelog/) and make sure there are no actions you need to take before deploying a new version.
    
3.  Optionally, confirm what the update is going to do using [Helm Diff](https://github.com/databus23/helm-diff):
    
    ```shell
    helm diff upgrade circleci-server oci://cciserver.azurecr.io/circleci-server -n $namespace --version 4.7.15 -f <path-to-values.yaml> --username $USERNAME --password $PASSWORD
    ```
    
4.  Upgrade your Nomad clients Terraform module to the [4.7 release](https://github.com/CircleCI-Public/server-terraform/releases/tag/4.7.0). Follow the documentation to plan and apply the Terraform changes for your [AWS](https://circleci.com/docs/server-admin/server-4.7/installation/phase-3-aws-execution-environments/#create-your-cluster-with-terraform) or [GCP](https://circleci.com/docs/server-admin/server-4.7/installation/phase-3-gcp-execution-environments/#create-your-cluster-with-terraform) environment.
    
5.  Perform the upgrade:
    
    ```shell
    helm upgrade circleci-server oci://cciserver.azurecr.io/circleci-server -n $namespace --version 4.7.15 -f <path-to-values.yaml> --username $USERNAME --password $PASSWORD
    ```
    
6.  Deploy and run [`reality check`](https://github.com/circleci/realitycheck) in your test environment to ensure your installation is fully operational.