# .org to .com migration deadline?

**URL:** <https://travis-ci.community/t/org-to-com-migration-deadline/10260>\
**Category:** Travis CI Discussions & Feedback\
**Tags:** org-com-migration\
**Created:** [October 23, 2020, 6:53am UTC](https://travis-ci.community/t/org-to-com-migration-deadline/10260 "2020-10-23T06:53:43Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![hugovk](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/hugovk/32/684_2.png) [@hugovk](https://travis-ci.community/u/hugovk)\
**Post date:** [October 23, 2020, 6:53am UTC](https://travis-ci.community/t/org-to-com-migration-deadline/10260/1 "2020-10-23T06:53:43Z")

</div>

I stumbled across this email from Travis CI on another project’s tracker (emphasis mine):

> In an effort to ensure that all of our users - whether you build open-source, public or private repositories - receive regular feature updates, security patches and UX/UI enhancements, we are announcing that **[travis-ci.org](http://travis-ci.org) will be officially closed down completely on December 31st, 2020**, allowing us to focus all our efforts on bringing new features and fixes to [travis-ci.com](http://travis-ci.com) and all of our awesome users like yourself on the [travis-ci.com](http://travis-ci.com) domain.

[https://mailchi.mp/3d439eeb1098/travis-ciorg-is-moving-to-travis-cicom](https://mailchi.mp/3d439eeb1098/travis-ciorg-is-moving-to-travis-cicom)

I didn’t receive this email; couldn’t find anything on [https://blog.travis-ci.com](https://blog.travis-ci.com); and the FAQ doesn’t mention the new year deadline, nor any other deadline:

> **[Travis CI Documentation](https://docs.travis-ci.com/user/migrate/open-source-repository-migration)**
>
> Migrating repositories to travis-ci.com

Please could you confirm this deadline, and publicise it more widely? For example, send the mail out to more people, put it on your FAQ and blog and other channels.

Thank you!

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [October 23, 2020, 1:58pm UTC](https://travis-ci.community/t/org-to-com-migration-deadline/10260/2 "2020-10-23T13:58:02Z")

</div>

I wonder why they don’t use the announcement feature in the web ui actually. That’s a super convenient way to bring a message to either all of just affected users.

---

<div class="post-metadata">

**Author:** ![dfawley](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/dfawley/32/5385_2.png) [@dfawley](https://travis-ci.community/u/dfawley)\
**Post date:** [October 23, 2020, 4:07pm UTC](https://travis-ci.community/t/org-to-com-migration-deadline/10260/3 "2020-10-23T16:07:20Z")

</div>

This was surprising to me as well. And with the performance issues ([Builds hang in queued state](https://travis-ci.community/t/builds-hang-in-queued-state/10250/6)), it looks like we need to prioritize the migration work ASAP, not just “by Dec 31st”.

---

<div class="post-metadata">

**Author:** ![dgw](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/dgw/32/2638_2.png) [@dgw](https://travis-ci.community/u/dgw)\
**Post date:** [October 26, 2020, 7:11pm UTC](https://travis-ci.community/t/org-to-com-migration-deadline/10260/4 "2020-10-26T19:11:45Z")

</div>

I didn’t get a notification about this deadline either.

Was I supposed to just panic on January 1 when everything simply stopped working? (Not that .org has been working very well this past week, with queue depths of 7k+ Linux builds…)

---

<div class="post-metadata">

**Author:** ![hugovk](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/hugovk/32/684_2.png) [@hugovk](https://travis-ci.community/u/hugovk)\
**Post date:** [October 29, 2020, 8:53am UTC](https://travis-ci.community/t/org-to-com-migration-deadline/10260/5 "2020-10-29T08:53:49Z")

</div>

The [migration FAQ](https://docs.travis-ci.com/user/migrate/open-source-repository-migration#frequently-asked-questions) has been updated:

> #### Q. When will the migration from [travis-ci.org](http://travis-ci.org) to [travis-ci.com](http://travis-ci.com) be completed? [#](https://docs.travis-ci.com/user/migrate/open-source-repository-migration#q-when-will-the-migration-from-travis-ciorg-to-travis-cicom-be-completed)
> 
> A. In an effort to ensure that all of our users - whether you build open-source, public or private repositories - receive regular feature updates, security patches and UX/UI enhancements, we are announcing that [travis-ci.org](http://travis-ci.org) will be officially closed down completely no later than December 31st, 2020, allowing us to focus all our efforts on bringing new features and fixes to [travis-ci.com](http://travis-ci.com) and all of our awesome users like yourself on the [travis-ci.com](http://travis-ci.com) domain.
> 
> #### Q. What will happen to [travis-ci.org](http://travis-ci.org) after December 31st, 2020? [#](https://docs.travis-ci.com/user/migrate/open-source-repository-migration#q-what-will-happen-to-travis-ciorg-after-december-31st-2020)
> 
> A. [Travis-ci.org](http://Travis-ci.org) will be switched to a read-only platform, allowing you to see your jobs build history from all repositories previously connected to [travis-ci.org](http://travis-ci.org).

Thank you for clarification. I still recommend Travis sends a mail out to more people, puts it on the FAQ and blog and posts to other channels, but marking as solved.

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [October 30, 2020, 1:30am UTC](https://travis-ci.community/t/org-to-com-migration-deadline/10260/6 "2020-10-30T01:30:03Z")

</div>

2 posts were merged into an existing topic: [Is there a plan to _stop_ Travis requesting read / write access on travis-ci.com login?](https://travis-ci.community/t/is-there-a-plan-to-stop-travis-requesting-read-write-access-on-travis-ci-com-login/1364/17)
