# Technical part of downgrading SaaS - Need Help!

**URL:** <https://gorelay.co/t/technical-part-of-downgrading-saas-need-help/589>\
**Category:** What Am I Missing\
**Tags:** bootstrapping\
**Created:** [June 10, 2021, 7:54am UTC](https://gorelay.co/t/technical-part-of-downgrading-saas-need-help/589 "2021-06-10T07:54:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bharath\_ab](https://sea2.discourse-cdn.com/flex020/user_avatar/gorelay.co/bharath_ab/32/457_2.png) [@bharath\_ab](https://gorelay.co/u/bharath_ab)\
**Post date:** [June 10, 2021, 7:54am UTC](https://gorelay.co/t/technical-part-of-downgrading-saas-need-help/589/1 "2021-06-10T07:54:19Z")

</div>

Hey SaaSy folks,  
I have a few questions related to handling downgrades.

1. If an organization chooses 20 seats initially and downgrades to 10 seats after a few months, what happens to the data (user accounts + work they had done ) of the deactivated 10 seats.

2. If an organization chooses 20 seats initially and downgrades to 10 seats after a few months and then upgrades back to 20 seats with the same 10 deactivated users. should I be creating a new set of user accounts or continue with the same user’s accounts

How do you handle these cases,  
Thank you.

---

<div class="post-metadata">

**Author:** ![kps](https://sea2.discourse-cdn.com/flex020/user_avatar/gorelay.co/kps/32/232_2.png) [@kps](https://gorelay.co/u/kps)\
**Post date:** [June 10, 2021, 5:28pm UTC](https://gorelay.co/t/technical-part-of-downgrading-saas-need-help/589/2 "2021-06-10T17:28:58Z")

</div>

My suggestion would be to keep the data of deactivated accounts unless there is heavy infra cost involved in doing so and allow for reactivating the previously deactivated accounts.

BTW, I am assuming that

- Orgs can choose to deactivate (and reactivate) specific users as part of normal user management and not just during downgrading.
- You don’t allow orgs to downgrade if they have more active seats than they are downgrading to.

---

<div class="post-metadata">

**Author:** ![bharath\_ab](https://sea2.discourse-cdn.com/flex020/user_avatar/gorelay.co/bharath_ab/32/457_2.png) [@bharath\_ab](https://gorelay.co/u/bharath_ab)\
**Post date:** [June 12, 2021, 10:55am UTC](https://gorelay.co/t/technical-part-of-downgrading-saas-need-help/589/3 "2021-06-12T10:55:51Z")

</div>

perfect! thank you for the suggestion.

---

<div class="post-metadata">

**Author:** ![rickghome](https://sea2.discourse-cdn.com/flex020/user_avatar/gorelay.co/rickghome/32/634_2.png) [@rickghome](https://gorelay.co/u/rickghome)\
**Post date:** [July 10, 2022, 6:41pm UTC](https://gorelay.co/t/technical-part-of-downgrading-saas-need-help/589/4 "2022-07-10T18:41:27Z")

</div>

Apply the rule of “minimal friction” – and consider what you would want if you were the customer. I’d suggest archiving the old seats, and allowing the customer to restore them if the user upgrades later.