Transferring or Renaming Repositories

Warning: In rare cases, renaming and/or transferring your organization or a repository in your VCS may lead to lost contexts, project build history, and settings in CircleCI. Please be sure to keep this in mind. You may want to backup any valuable data.

Data loss can occur due to difficult edge cases in the way CircleCI syncs organization and repository data from your VCS. This is especially true in cases where the previous name is immediately recreated as a different organization or repository.

Best Practices

When transferring a repository in your VCS to another organization, renaming a repository or organization, or transferring ownership of an organization - the following are best practices: 

• Login to your VCS and rename and/or transfer your organization/repository (Please try and avoid renaming your organization multiple times)
• Login to CircleCI using your new organization's name and confirm that your projects, contexts, settings and billing are all up to date. Make sure you are following all transferred projects within your new organization . If you have only changed the name of your repository or transferred one project, this should be reflected in CircleCI automatically once you login to your account. 
• After confirming the above, you can create a new organization or repository under the old name in your VCS, if desired.

Additional resources

• Transferring a repository on GitHub
• Transferring an organizations ownership on GitHub

Note: You can login to CircleCI's UI using your new organization by navigating through CircleCI's homepage and selecting your new organization or by using this URL directly: https://app.circleci.com/projects/project-dashboard/:VCS/:NEW_ORG_NAME

If you come across any issues when renaming your Organization or Repository please reach out to CircleCI Support.