ORG Shutdown


May 7, 2021


If you’ve kept up with our announcements, or if you recently accessed the UI, you are likely aware of the planned migration from the domain to This is the final step of a process that started in 2018 to unify Travis CI under a single domain.

We want to clear up any confusion about what this migration means for the future of Travis CI, so we’re here to give you the facts.

Firstly, an update on the timeline for the migration. We’re aiming to sunset the domain on May 31, 2021. Any accounts still on the domain after that date will still have access to historical data for build logs and config information, but builds will no longer run successfully. (Note: You may see builds run for a short period after May 31, 2021, but please do not rely on for performing critical builds after this point.)

This means that any repositories you currently have connected to must be migrated over to before the end of May 2021 if you want your builds to continue without interruption. To do this you can simply sign up to and link the repositories that you want to migrate. Your existing configurations will work as expected on and you do not need to alter your build definitions. Alternatively, there’s a migration feature, which will allow transferring a limited amount of build history data from to

Secondly, what does this mean for the future of Travis CI? As we’ve previously mentioned, for many years the plan has been to migrate all accounts from to The reason is simple: this consolidation will allow updates and improvements made to the core Travis CI platform to be unified under, making changes available to all Travis CI users, at the same time. Furthermore, this change will help make our road mapping, bug fixing, and support processes more efficient and structured, allowing us to provide a better experience to our users.

Here’s the TL;DR version:

  • shut down will occur on May 31, 2021
  • This change is to ensure product updates and fixes can be implemented for all users, at the same time
  • All your repositories on should be migrated to before May 31, 2021 to avoid builds not running
  • All repositories – private, and public – will continue to build as expected on once migrated
  • Your historic build data on will remain available in a read-only state for an indefinite period

If you have any questions about anything relating to the details above, or if you have any issues migrating your repositories from to, please contact [email protected] for help.

Written By

Reviewed By