# Granular Scope Migration

**URL:** <https://community.hubspot.com/t/granular-scope-migration/45539>\
**Category:** APIs & Integrations\
**Tags:** developer-tools\
**Created:** [October 19, 2021, 7:08am UTC](https://community.hubspot.com/t/granular-scope-migration/45539 "2021-10-19T07:08:44Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![NNelissen](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/nnelissen/32/47092_2.png) [@NNelissen](https://community.hubspot.com/u/NNelissen)\
**Post date:** [February 21, 2022, 4:36am UTC](https://community.hubspot.com/t/granular-scope-migration/45539/3 "2022-02-21T04:36:52Z")

</div>

Hi @dennisedson  
Since ours is an integration platform, we have a lot of existing Hubspot connections which was connected with the old scope before scope migration. The access token, refresh token generated earlier where of using the old scope and once the access token is expired we keep on the refreshing token and it won’t go through OAuth authorize the first step

Do you think after the deprecation date will the existing connection works with access token,refresh token generated using old scope, or do we need to reconnect the connection

Please let us know your insights on this

Please get back ASAP

Thanks!!

---

_[View the full topic](https://community.hubspot.com/t/granular-scope-migration/45539)._