# Migrating from travis-ci.org to .com not possible for repo in other organization **URL:** \ **Category:** Travis CI Discussions & Feedback\ **Created:** [January 9, 2020, 2:53pm UTC](https://travis-ci.community/t/migrating-from-travis-ci-org-to-com-not-possible-for-repo-in-other-organization/6789 "2020-01-09T14:53:01Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![lelegard](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/lelegard/32/3583_2.png) [@lelegard](https://travis-ci.community/u/lelegard)\ **Post date:** [January 9, 2020, 2:53pm UTC](https://travis-ci.community/t/migrating-from-travis-ci-org-to-com-not-possible-for-repo-in-other-organization/6789/1 "2020-01-09T14:53:01Z")
Hi, I am in the process of migrating open source projects from [travis-ci.org](http://travis-ci.org) to [travis-ci.com](http://travis-ci.com). I cannot migrate a repo from a GitHub organization. In my legacy [travis-ci.org](http://travis-ci.org), I had the following: - On GitHub, I have several repos in my account plus two organizations I own, tsduck and qtlmovie. - I authorized Travis-CI access to “selected repositories” (not all repositories). - Access was granted to Travis CI on two repos: one in my account (a simple travis-test repo) and one in a separate organization (tsduck/tsduck). - Access was granted to organization tsduck but not to organization qtlmovie. When I performed the migration, only the repo in my account was migrated. The second repo from the tsduck organization was not migrated. In the Travis-CA settings for repositories, we have “Missing an Organization? Review and add your authorized organizations.” This brings me to a GitHub settings page for Travis CI. There, under the “Organization access” part, I have my two organizations, qtlmovie and tsduck. The “Grant” button is available only for the qtlmovie organization (which was never authozized for Travis-CI). The tsduck organization has no button (no “Grant”, not even a “Revoke”). In the GitHub settings Application / Travis-CO / Configure, “Only select repositories” is checked. In the “Select repositories” combo, only the local repos are proposed, no repo from the tsduck organization. According to [Beta migration to travis-ci.com: Repo list incorrect](https://travis-ci.community/t/beta-migration-to-travis-ci-com-repo-list-incorrect/6407/4), a similar issue was reported. The solution mentioned “Ok so the problem was that this belonged to a different organisation, and that I had to execute the 2nd part of the migration, namely to go to the Migrate tab on [travis-ci.com](http://travis-ci.com) and to select the repository there.” Doing the same thing, I just get a button “Activate all repositories using GitHub Apps” which brings me again to the usual GitHub settings. Back at the beginning. I also tried to give Travis-CI access to all repositories. This does not change anything. Even stranger: I give Travis-CI access to my second organization (qtlmovie) and now I can see it under [travis-ci.com](http://travis-ci.com). But my first organization (tsduck), which was alread authorized on [travis-ci.org](http://travis-ci.org), cannot be seen on [travis-ci.com](http://travis-ci.com). How would you migrate a repo from an organization? What did I miss? ---
**Author:** ![Helveg](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/helveg/32/3372_2.png) [@Helveg](https://travis-ci.community/u/Helveg)\ **Post date:** [January 9, 2020, 3:15pm UTC](https://travis-ci.community/t/migrating-from-travis-ci-org-to-com-not-possible-for-repo-in-other-organization/6789/2 "2020-01-09T15:15:08Z")
There’s a button or something somewhere that completes a second step to the migration process. It’s a while ago I forgot the specifics ---
**Author:** ![lelegard](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/lelegard/32/3583_2.png) [@lelegard](https://travis-ci.community/u/lelegard)\ **Post date:** [January 9, 2020, 3:40pm UTC](https://travis-ci.community/t/migrating-from-travis-ci-org-to-com-not-possible-for-repo-in-other-organization/6789/3 "2020-01-09T15:40:43Z")
> I forgot the specifics That is exactly the point, the devil is in the details. I went through this second step, the “Migrate” tab, without luck. ---
**Author:** ![safris](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/safris/32/5881_2.png) [@safris](https://travis-ci.community/u/safris)\ **Post date:** [December 20, 2020, 11:56am UTC](https://travis-ci.community/t/migrating-from-travis-ci-org-to-com-not-possible-for-repo-in-other-organization/6789/4 "2020-12-20T11:56:13Z")
I am facing the same issue. I see a message saying: > Please be aware [travis-ci.org](http://travis-ci.org) will be shutting down in several weeks …and I cannot migrate repositories in my organizations. Please help! EDIT: I figured it out with the help of [this post](https://travis-ci.community/t/migration-is-not-available-for-this-account/10490/2). ---
**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:** [December 20, 2020, 12:46pm UTC](https://travis-ci.community/t/migrating-from-travis-ci-org-to-com-not-possible-for-repo-in-other-organization/6789/5 "2020-12-20T12:46:48Z")
See this for caveats associated with migration: > [@Build delays for open source project](https://travis-ci.community/t/build-delays-for-open-source-project/10272/26): > > As was pointed out in [Builds hang in queued state - #6 by Montana](https://travis-ci.community/t/builds-hang-in-queued-state/10250/6) linked to earlier in this topic, Travis is moving workers from [travis-ci.org](http://travis-ci.org) to [travis-ci.com](http://travis-ci.com) in preparation to fully close .org (or rather, make it read-only) around the New Year. So you need to migrate to .com to stop experiencing delays. Note the caveats: