# Beta migration from .org to .com leaves old webhooks behind
**URL:** https://travis-ci.community/t/beta-migration-from-org-to-com-leaves-old-webhooks-behind/2488
**Category:** Travis CI Discussions & Feedback
**Tags:** github-integration
**Created:** [February 28, 2019, 11:27am UTC](https://travis-ci.community/t/beta-migration-from-org-to-com-leaves-old-webhooks-behind/2488 "2019-02-28T11:27:32Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@smola](https://travis-ci.community/u/smola)
#### Post date: [February 28, 2019, 11:27am UTC](https://travis-ci.community/t/beta-migration-from-org-to-com-leaves-old-webhooks-behind/2488/1 "2019-02-28T11:27:32Z")
We are trying the new beta migration from .org to .com. We noticed that our PRs are working correctly with .com, but have a pending CI check, apparently from .org.
See an example: [https://github.com/src-d/gitbase/pull/714](https://github.com/src-d/gitbase/pull/714)
The old .org webhook is still in the repo settings. We can remove this manually, but I’m wondering if this is something that should be automated in the migration process.
---
### Author:  [@smola](https://travis-ci.community/u/smola)
#### Post date: [February 28, 2019, 11:54am UTC](https://travis-ci.community/t/beta-migration-from-org-to-com-leaves-old-webhooks-behind/2488/2 "2019-02-28T11:54:18Z")
I found the issue. Branch protection settings need to be changed to require the new .com integration and uncheck the .org one.
---
### Author:  [@native-api](https://travis-ci.community/u/native-api)
#### Post date: [February 28, 2019, 3:49pm UTC](https://travis-ci.community/t/beta-migration-from-org-to-com-leaves-old-webhooks-behind/2488/3 "2019-02-28T15:49:39Z")
Note that by migrating to .com, [you’re giving Travis many additional access rights to your repos](https://travis-ci.community/t/travis-ci-com-privacy-concerns/2315). Your management may want to know this.