Migrating from Cloud to Server
There is no formal process or toolset to migrate between CircleCI Cloud (SaaS) to an installed CircleCI Server setup. The process is to perform a fresh install of CircleCI 2.0, using AWS and Terraform—see Installation for instructions.
Next, you will need to manually copy over all of your project settings including Contexts, environment variables, and API tokens.
Note: It is not possible to bring your projects’ build histories from SaaS; you will have to re-add all of your projects to your Server installation.
config.yml files should work as-is on Server, assuming they are working on SaaS. There are small differences between the 1.0 build environments that may result in some 1.0 configs not translating 100% from SaaS to Server.
machine executor AMIs and configurable instance types are defined in a specific way, so consider how your teams may be using configurable resources (
resource_class) on SaaS when defining your Server build cluster.
- Currently the
macosexecutor is not supported on Server.
- Bitbucket is not supported on Server; GitHub/GitHub Enterprise is the only supported VCS.
Help make this document better
This guide, as well as the rest of our docs, are open-source and available on GitHub. We welcome your contributions.
- Suggest an edit to this page (please read the contributing guide first).
- To report a problem in the documentation, or to submit feedback and comments, please open an issue on GitHub.
- CircleCI is always seeking ways to improve your experience with our platform. If you would like to share feedback, please join our research community.
CircleCI Documentation by CircleCI is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.