Estimate storage needed before upgrading

Estimate storage needed before upgrading with a controlled test, clear verification, limits, and recovery steps.

Last reviewed

Estimate storage needed before upgrading is easier to verify when you use one controlled item and confirm the account, workspace, source, and destination at each step. This guide follows the current Dosya workflow and identifies the result you should see.

Before you start

  • Open Account settings > Plan and storage in the current released client.
  • Confirm the active account and workspace, then identify current usage and upcoming file volume.
  • Use a small non-confidential test item and record its current state before changing it.
  • Keep passwords, API keys, recovery codes, private links, personal data, and confidential file contents out of screenshots and support messages.

Steps: estimate storage needed before upgrading

  1. Open Account settings > Plan and storage and confirm the active account and workspace.
  2. Locate current usage and upcoming file volume and verify its name or identifying details.
  3. Add current usage, expected uploads, version growth, and operating headroom, then choose the smallest suitable tier.
  4. Read the displayed warning, permission, progress, or confirmation state before leaving the screen.
  5. Confirm that the selected tier covers the planned data with reasonable headroom.
  6. Refresh, fetch, or reopen the relevant view once to verify the result persisted.
Dosya storage breakdown used to review capacity before a plan change.
Measure current usage and confirm the effective date before changing storage capacity. Open full-size screenshot.

Expected result

The controlled workflow completes and the selected tier covers the planned data with reasonable headroom. The result remains visible after a refresh, reconnect, or return to the relevant screen.

Limits and important details

  • Available controls depend on the current client version, account plan, workspace role, policy, and selected integration surface.
  • Processing, indexing, background transfer, provider authorization, or storage accounting can delay a visible result.
  • For destructive, access-changing, or automated actions, validate with disposable data before applying the workflow to important files.

Troubleshooting

The expected control is missing. Return to Account settings > Plan and storage, confirm the active workspace, and check that your role and client version support the action.

The operation is rejected or stalls. Read the exact message and check permissions, locks, storage, network state, source availability, and any third-party authorization before retrying.

The result is still unclear. Repeat with one small test item, then contact support with the time, client version, workspace, and a nonsecret error, delivery, or request identifier.

Was this helpful?

Loading helpfulness results…

Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.

Questions and replies

Ask about the steps in this guide. Questions are reviewed before publication.

Keep account details, credentials and private files out of public questions. Use private support for those.

Loading questions…

    Sign in to your Dosya account to ask a question.