# Granular Scope Migration - Existing users

**URL:** <https://community.hubspot.com/t/granular-scope-migration-existing-users/49126>\
**Category:** APIs & Integrations\
**Tags:** professional\
**Created:** [January 3, 2022, 7:29am UTC](https://community.hubspot.com/t/granular-scope-migration-existing-users/49126 "2022-01-03T07:29:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![RM456](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/rm456/32/78108_2.png) [@RM456](https://community.hubspot.com/u/RM456)\
**Post date:** [January 3, 2022, 7:29am UTC](https://community.hubspot.com/t/granular-scope-migration-existing-users/49126/1 "2022-01-03T07:29:30Z")

</div>

Hi there,

I’m in the process of doing the granular scope migration for our HubSpot App and I wanted to confirm that this update will NOT require our existing customers to re-authenticate?  
Based on the communication we received, it sounds like they would not need to, however, while I was busy setting the permissions in the configuration I see the following message.

 ![Screenshot 2022-01-03 at 09.22.22.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/c/a/cad256169330867ca64903f4ec3ef3d25a0312ff.png)

Can you please confirm so we know how to handle the update process?

---

<div class="post-metadata">

**Author:** ![dennisedson](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/dennisedson/32/28044_2.png) [@dennisedson](https://community.hubspot.com/u/dennisedson)\
**Post date:** [January 3, 2022, 2:20pm UTC](https://community.hubspot.com/t/granular-scope-migration-existing-users/49126/2 "2022-01-03T14:20:11Z")

</div>

@RM456

You are correct! No change required for portals who have previously installed your app. Any new installs will need to use the install URL with updated scope requirements and you will need to update anything in your code base referencing the old scopes if necessary.

[Per the docs](https://developers.hubspot.com/docs/api/oauth/contacts-scope-migration):

Update your install URL for **new app installs** and any associated code referencing the old contacts scope by February 28, 2022. You will need to make these updates for your app to continue working.

---

<div class="post-metadata">

**Author:** ![JGM](https://avatars.discourse-cdn.com/v4/letter/j/96bed5/32.png) [@JGM](https://community.hubspot.com/u/JGM)\
**Post date:** [January 4, 2022, 9:58am UTC](https://community.hubspot.com/t/granular-scope-migration-existing-users/49126/3 "2022-01-04T09:58:09Z")

</div>

Facing a similar issue, with scope migrations. Forms scope does not seem to take effect.  
more details here ([https://community.hubspot.com/t5/APIs-Integrations/Granular-scope-migration-Forms-scope-not-working/m-p/549618#M49800](https://community.hubspot.com/t5/APIs-Integrations/Granular-scope-migration-Forms-scope-not-working/m-p/549618#M49800)), unfortunately, my post is marked as spam at the moment

---

<div class="post-metadata">

**Author:** ![RM456](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/rm456/32/78108_2.png) [@RM456](https://community.hubspot.com/u/RM456)\
**Post date:** [January 4, 2022, 3:12pm UTC](https://community.hubspot.com/t/granular-scope-migration-existing-users/49126/4 "2022-01-04T15:12:22Z")

</div>

Hi Dennis,

Something else that came to my attention now that concerns me.

I noticed the Workflow scope has been moved to legacy and that it was not auto-migrated. Can you please also confirm this won’t break any existing users experience with using automations?  
From my understanding legacy scopes will become obsolete?

---

<div class="post-metadata">

**Author:** ![RM456](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/rm456/32/78108_2.png) [@RM456](https://community.hubspot.com/u/RM456)\
**Post date:** [January 3, 2022, 2:22pm UTC](https://community.hubspot.com/t/granular-scope-migration-existing-users/49126/5 "2022-01-03T14:22:29Z")

</div>

Hi Dennis,

Thank you for the quick response, I just wanted to be 100% sure.