End of support for legacy manual organizations November 2, 2021#
On November 2, 2021, as part of our efforts to improve Codacy Cloud and allow all our customers to benefit from a more seamless experience, we’re removing the support for legacy manual organizations. As part of this process, we'll automatically migrate your legacy organization to a new synced organization.
To make sure that Codacy will continue to analyze your repositories please perform the following steps before November 2, 2021:
Make sure that your Git provider organization owners belong to the Administrators team of your legacy organization on Codacy.
If you already have any synced organizations on Codacy, the migration process won't overwrite any data on those synced organizations, nor copy any repositories that you have in your legacy organization.
After the migration process ends on December 2, 2021, we'll delete any existing legacy organizations that we couldn't migrate.
How does this impact me?#
Synced organizations have several advantages, such as keeping the repositories and team member permissions in sync with the Git provider. Besides this, Codacy is actively developing new features and improvements for synced organizations only.
However, the following scenarios may impact you:
If your legacy organization is using the Open source plan then Codacy has already stopped analyzing your repositories. Codacy will attempt to migrate your organization and restore the analysis of your repositories.
If we can't automatically migrate your legacy organization Codacy will stop analyzing your repositories, and you'll lose access to your existing repositories on Codacy. Please make sure that you follow the steps above to guarantee that the migration is successful.
Codacy appreciates your continued support through this time of growth and change. If you have any questions, please don’t hesitate to reach out by sending an email to email@example.com or by using the in-app chat.
Share your feedback 📢
Let us know if this page was helpful:
Thank you for the feedback!
We're sorry to hear that. Please let us know what we can improve.