Plan Cleanup on Downgrade
How NeoSQL helps you clean up projects, members, connections, and schemas that exceed the new plan limits when downgrading to a lower-tier plan.
Cleanup overview
After the downgraded plan is applied, the Resource Cleanup Modal will automatically open upon login.
To continue using NeoSQL, you must select which resources to keep within the limits of the new plan in the modal.
Data for unselected resources will not be deleted; it will remain inactive and can be restored later when upgrading your plan.
Per-resource cleanup policy
Each resource is cleaned up at a different stage and reacts differently when the limit is exceeded.
| Resource | Cleanup stage | If the limit is exceeded |
|---|---|---|
| Number of projects | Stage 1 / Step 1 | Pick the projects to keep. Unpicked projects are deactivated; they cannot be entered and appear on the dashboard as a grayed-out card with a Disabled badge. |
| Members per project | Stage 1 / Step 2 | Pick the members to keep. Unpicked members are deactivated for that project and can no longer enter it. The owner is always included automatically. |
| Connections per project | Stage 2 / Step 1 | Pick the connections to keep. Unpicked connections are deactivated and shown in the tree with a lock icon and a (disabled) label. |
| Schemas per connection | Stage 2 / Step 2 | Pick the schemas to keep. Unpicked schemas are removed from the connection's schema list. You can freely add them back later within the new limit. |
| Tables per ERD | — | Existing ERDs stay as-is; only adding new tables is blocked when over the limit. |
| Public gallery ERDs | Stage 1 side effect | Any PUBLIC ERD that belongs to a deactivated project is automatically hidden from the gallery (data preserved). It is automatically restored when the plan is upgraded again. |
Stage 1 — At dashboard entry (projects & members)
The first time you sign in after the downgrade takes effect, the dashboard opens a project cleanup modal. It runs in two steps and applies only to projects you own.
Step 1. Pick the projects to keep
You'll see your active owned projects. You must pick exactly the number allowed by the new plan before Next becomes enabled.
Step 2. Pick the members to keep
For each kept project that exceeds the new member limit, a member selection step is shown. You (the owner) are always included automatically; pick the remaining members up to the limit.
Confirmation
On confirm, the cleanup is applied immediately and you can re-enter the dashboard. Unpicked projects and members are kept in a deactivated state and shown on the dashboard as grayed-out cards with a Disabled badge. Their data is not deleted.
Stage 2 — At project entry (connections & schemas)
When you enter a project that you kept in Stage 1, if its connections or schemas exceed the new limits, a connection cleanup modal opens — again mandatory.
Step 1. Pick the connections to keep
From the project's active connections, pick exactly the number allowed by the new plan.
Step 2. Pick the schemas to keep
If any kept connection exceeds the schema limit, you pick which schemas to keep per connection. If the default schema is removed, it automatically moves to the first remaining schema.
Confirmation
On confirm, the cleanup is applied immediately and the project tree is re-rendered.
Unpicked connections are kept in a deactivated state and shown in the tree with a lock icon and a (disabled) label, while unpicked schemas are simply removed from the connection's schema list
(no data is deleted; you can add them back later within the new limit).
How other members are affected
If you are not the owner of a project, the owner's cleanup result may block your access.
Whenever any of the following three reasons applies, the project card is grayed out with a Disabled badge and clicking it opens a reason-specific dialog.
| Reason | When it happens | What you see |
|---|---|---|
| The project itself is deactivated | The owner did not keep this project in Stage 1. | The project card is grayed out with a Disabled badge. Clicking it opens an info dialog, and you can leave the project from the context menu's Leave action. |
| You were deactivated as a member | The owner did not keep you in Stage 1 / Step 2. | The project card is grayed out with a Disabled badge. Clicking it opens an info dialog, and you can leave the project from the context menu's Leave action. |
| Owner cleanup is pending | The owner downgraded but has not finished Stage 1 or Stage 2 yet. | Access is temporarily blocked. Once the owner finishes cleanup, you can re-enter automatically. |
Effect on public gallery ERDs
Automatic hide
PUBLIC ERDs whose project was deactivated due to the downgrade are automatically hidden from the gallery. Their data is preserved.
Automatic restore
When you upgrade your plan and the project becomes active again, those hidden PUBLIC ERDs are automatically restored in the gallery.
If you explicitly Unpublish an ERD from the gallery, the published copy is deleted. It will not reappear in the gallery on a future upgrade.
After cleanup
Behavior of deactivated items and how limits come back after cleanup.
Deactivated items can only be deleted
Once a project, member, or connection is deactivated, there is no toggle to re-enable it within the same plan.
only Delete or recovery after a plan upgrade is allowed.
Schemas stay freely editable
Schemas have no deactivated state. They are simply trimmed from the connection's list during cleanup, and you can add or remove them freely later within the new limit.
When you upgrade again
Upgrading restores your limits, but deactivated projects, members, and connections are not revived automatically — the Owner has to re-enable each item manually:
• Project: on the dashboard, right-click the disabled project card → Enable (its gallery PUBLIC ERDs are restored automatically)
• Connection: in the project sidebar tree, right-click the disabled connection → Enable
• Member: in the project share modal, use the re-enable action next to the disabled member
Each enable succeeds only while the active count is below the new limit; if the limit is already full, it's rejected.
Schemas have no disable concept and can be added or removed freely within the limit.