# Will builds' logs be migrated upon .org -\> .com migration? **URL:** \ **Category:** Travis CI Discussions & Feedback\ **Tags:** org-com-migration\ **Created:** [March 30, 2020, 6:01pm UTC](https://travis-ci.community/t/will-builds-logs-be-migrated-upon-org-com-migration/7906 "2020-03-30T18:01:49Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![nkoep](https://avatars.discourse-cdn.com/v4/letter/n/d9b06d/32.png) [@nkoep](https://travis-ci.community/u/nkoep)\ **Post date:** [March 30, 2020, 6:01pm UTC](https://travis-ci.community/t/will-builds-logs-be-migrated-upon-org-com-migration/7906/1 "2020-03-30T18:01:50Z")
Hey, I’m considering migrating a repository from .org to .com. Unfortunately, there seems to be some contradictory information in the docs regarding build history. In the documentation [here](https://docs.travis-ci.com/user/migrate/open-source-repository-migration#what-information-will-be-transferred-to-travis-cicom) it states that build history will be migrated. However, in the modal that appears in the settings on [travis-ci.com](http://travis-ci.com) to confirm the migration of the repo, it says “Please note that your build history will not be migrated at this time. Until then, you can access the existing build history at [travis-ci.org](https://travis-ci.org).” I would assume that the latter is the case, but I’d be interested to hear from someone who already went through the migration process what happens to the build history. Thanks! ---
**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 22, 2020, 3:15pm UTC](https://travis-ci.community/t/will-builds-logs-be-migrated-upon-org-com-migration/7906/2 "2020-10-22T15:15:58Z")
It’s still the case that history is not fully migrated. The old builds are shown, but not their logs. Is there a target for when it will be migrated? When ready, will already-migrated repos have the history back-filled, or will only new migrations have history migrated? ---
**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, 6:59pm UTC](https://travis-ci.community/t/will-builds-logs-be-migrated-upon-org-com-migration/7906/3 "2020-10-23T18:59:52Z")
Confirming what Hugo says. In [https://travis-ci.com/github/native-api/test\_travis/builds](https://travis-ci.com/github/native-api/test_travis/builds), builds [#423](https://travis-ci.com/github/native-api/test_travis/builds/172767870) (the last one at [https://travis-ci.org/github/native-api/test\_travis/builds](https://travis-ci.org/github/native-api/test_travis/builds)) and earlier are present but not their logs. The UI says: _“There was an error while trying to fetch the log.”_ ---
**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:14pm UTC](https://travis-ci.community/t/will-builds-logs-be-migrated-upon-org-com-migration/7906/4 "2020-10-26T19:14:18Z")
Supposedly, .org is going to shut down [in about two months](https://travis-ci.community/t/org-to-com-migration-deadline/10260). What are the odds that we have working log migration by then? Bueller…? ---
**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, 12:48pm UTC](https://travis-ci.community/t/will-builds-logs-be-migrated-upon-org-com-migration/7906/5 "2020-10-29T12:48:43Z")
I emailed support: > Second, this is a blocker for migrating. > > When migrating a repo from .org to .com there’s a warning: > > “Please note that your build history will not be migrated at this time. Until then, you can access the existing build history at [travis-ci.org](http://travis-ci.org).” > > Is there a target for when it will be migrated? > > When ready, will already-migrated repos have the history back-filled, or will only new migrations have history migrated? Reply: > Unfortunately, since we don’t have ETA for the migration build logs, I would like to confirm that you will be able to access your build history on [travis-ci.org](http://travis-ci.org/) but your current builds will be happening on [travis-ci.com](http://travis-ci.com/). ---
**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 29, 2020, 2:27pm UTC](https://travis-ci.community/t/will-builds-logs-be-migrated-upon-org-com-migration/7906/6 "2020-10-29T14:27:34Z")
Frustrating that your support rep ignored the second question, about back-filling log history once it’s able to be migrated. Maybe I’ll send my own ticket and see if I can get that answered. **Edit:** Quick response, same non-answer: logs won’t migrate, but will remain accessible on .org in read-only mode. No commitment to fixing this for real and having all logs on .com it seems. ---
**Author:** ![tanzislam](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/tanzislam/32/2591_2.png) [@tanzislam](https://travis-ci.community/u/tanzislam)\ **Post date:** [November 15, 2020, 9:36am UTC](https://travis-ci.community/t/will-builds-logs-be-migrated-upon-org-com-migration/7906/7 "2020-11-15T09:36:48Z")
I suppose if they were to migrate the past logs to .com, any existing links to those logs (or log lines) – e.g. in this forum – would get broken. ---
**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:** [November 15, 2020, 10:05am UTC](https://travis-ci.community/t/will-builds-logs-be-migrated-upon-org-com-migration/7906/8 "2020-11-15T10:05:26Z")
Counterpoint: If they migrated _everything_ including logs from .org to .com, then .org doesn’t even need to remain up as an application in read-only mode. The entire legacy infrastructure could be shut down and replaced by a few simple redirection rules at the CDN layer. ---
**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:** [November 15, 2020, 2:32pm UTC](https://travis-ci.community/t/will-builds-logs-be-migrated-upon-org-com-migration/7906/9 "2020-11-15T14:32:42Z")
I don’t see how _copying_ stuff to another site would break anything whatsoever. ~~If~~ When [travis-ci.org](http://travis-ci.org) is finally shut down, any links to it will become invalid anyway – that’s what happens when a site is shut down 🙂 – so that’s hardly a stumbling block.