Skip down to the research record

Dropbox 30-day recovery: 3 figures to check before close

Quota Forecast Editorial Team · Published · 12 min read

Dropbox keeps deleted files and folders for 30 days or longer, depending on your plan. The Plus page adds that you can restore anything in your account for up to 30 days, and the three figures below cover removal, restore, and edits.

Key takeaways

  • Confirm the plan on the account that owns the forecast folder, because the window depends on it.
  • Treat 30 days as the longest window you can count on, and plan rollback dates inside it.
  • Test a deletion and an edit recovery before close, and write down what you see.
  • Keep at least one dated copy outside the shared folder.

Why a 30-day window matters for a shared forecast

Most revenue teams have one spreadsheet that everyone trusts a little too much. It lives in a shared folder, gets edited by sales ops, finance, and regional leads, and somewhere along the way a number changes that nobody can fully explain. When that happens in the week before a close, the first question is rarely "who did this?" It is "can we get the earlier version back, and how far back can we go?"

Dropbox answers that question with a retention window measured in days. For a forecast file, those days decide whether you get a clean rollback or a rebuild from memory and email threads. This post covers three Dropbox recovery figures worth checking before close: what each one covers, and what each one leaves open.

This guide is for the people who own the forecast, the operations leads who manage the shared folder, and the finance partners who rely on its numbers. Nothing here is legal, accounting, or compliance advice. It is a practical checklist for one question: if the forecast changes in the next few days, what can we undo, and how far back can we go?

Figure 1: deleted files and folders are kept for 30 days

The first figure comes from Dropbox's description of its cloud storage. The cloud storage page says: "Dropbox stores copies of all deleted files and folders for 30 days—or longer, depending on your plan."

Read the sentence in two parts. The first part is the number, 30 days. The second part is a qualifier: the period can be longer, and the length depends on the plan on your account. Check the plan on your own account before you rely on it.

This figure matters most when a whole file or a whole folder disappears. A forecast workbook is often moved into an archive folder during a reorganization, or deleted by someone who thought it was a duplicate. The file is not gone the moment it leaves the folder view.

That detail changes how fast you need to act. If a forecast file is deleted on a Monday and nobody notices until the Friday before close, part of the window is already gone. The earlier you notice, the more of the window you still have. So build a habit of checking, rather than counting on a heroic recovery at the last minute.

Two habits make this figure useful in practice:

  • Write down the date and time whenever someone reports a deleted or moved forecast file. Recovery is a race against the window, and the start date is the first thing anyone will ask for.
  • Keep the forecast in a folder that one or two named owners control (see Dropbox shared folder rules for deal files). Fewer people with delete rights means fewer accidental removals.

Before close, run a small test to see how this figure works in your own account. Create a throwaway file in a test folder, delete it, and try to find it again. Note how long the search took and which path you used. For more on restore steps, see recovery rules for deleted sales records. You are not testing Dropbox so much as your team's ability to recover under a little pressure, which is what close week will feel like.

Figure 2: restore anything for up to 30 days on Plus

The second figure comes from the Dropbox Plus page, which says: "Now you can restore or recover anything in your Dropbox account for up to 30 days."

This wording is broader than the first figure. "Anything in your Dropbox account" is a statement about restore power on that plan, not only about one deleted file. It is also worded as "up to 30 days," which makes 30 days a ceiling. It is the outer limit the page promises, not a promise that every item will be available on day 30 in every situation. Read it that way when you make decisions.

The gap between those two readings is where close-week mistakes happen. A team hears "30 days" and assumes it has the full window in every case. A safer rule is to treat the window as the longest you can count on, and to plan rollback dates inside it with some margin. If a change falls outside that window, do not expect this page to help. Look for another copy: a snapshot you exported, an email attachment sent to finance, or a version saved in a system of record.

The Plus page is also the source for the third figure below, so it is worth reading the whole page once, not just the headline. Ask the person who manages your Dropbox account which plan the forecast team is on, and confirm the answer against the page yourself. Do not rely on a plan name from a slide deck or an old renewal email.

Figure 3: deleted or modified files for 30 days on Plus

The third figure is the easiest to miss and the one most likely to matter for a forecast. The Plus page says the plan includes "the ability to recover deleted or modified files for 30 days." The same sentence lists two-factor authentication and remote wipe capabilities as other features of the plan.

Deleted files are obvious. Modified files are the quiet problem. A forecast is rarely deleted; it is edited. A rep moves a close date from the end of the quarter into the next one. A finance analyst changes a probability column. A formula is overwritten with a typed value so the total looks right on a call. The file still exists, so nobody thinks to restore anything. The change simply becomes the new truth, and the earlier truth drops out of view.

This figure is the one that lets you roll back to an earlier state of the same file. That is a different job from restoring a deleted copy, and it needs its own test. Pick a throwaway file, change one cell, save, and then recover the earlier version through Dropbox's recovery features. Confirm three things: the earlier version opens, the numbers match what you expected, and you can name the date that version came from. If your team cannot do all three in a few minutes, it is not ready for close.

Be careful about what this figure does not tell you. It says modified files can be recovered for 30 days on the plan on that page. It does not say how many earlier versions are kept inside that window, how often a version is captured, or whether every save creates a separate restore point. Do not write those details into your process from memory. Test them in your own account and record what you see.

The security features in the same sentence matter too, though for a different reason. A forecast file is easier to damage when an account is compromised. Two-factor authentication for everyone who can edit the forecast is a practical control that pairs well with a recovery window. A recovery window helps you undo a mistake; two-factor authentication helps make sure someone outside the team cannot make the mistake for you.

Illustrative example: a rollback in a shared forecast

Picture a four-person revenue team on a plan that matches the Plus figures above. On a Tuesday, a regional lead moves a large deal into the next quarter and the total drops. Nobody notices until Thursday, when the CFO asks why the commit number fell.

The team confirms the edit date from its review notes, then picks the version saved before the edit, which is the state agreed on in Monday's review. It recovers that version, checks that the commit total matches Monday's numbers, and names it the official forecast. The regional lead then re-enters the deal in the restored copy with a note.

Notice what made this easy: the change was caught within days, the date was known, and the restore had been tested the week before.

Put the three figures side by side

Here is the short version:

  1. Deleted files and folders: kept for 30 days or longer, depending on your plan (cloud storage page).
  2. Restore anything: up to 30 days on Plus (Plus page).
  3. Deleted or modified files: recoverable for 30 days on Plus (Plus page).

The first covers removal. The second covers restore in general. The third covers edits. A forecast team needs all three in view, because damage to a forecast is often an edit, and edits are the failure that a casual check misses.

The close-week rule that follows is simple. The oldest change you might need to undo must sit inside the window you have confirmed for your plan. If your window is 30 days and close is a week away, a change made before the window opened is out of reach. Pick the date you would need to roll back to, count backward from today, and make sure that date falls inside the window with room to spare.

A checklist to run a week before close

Work through these steps about a week before the close date. Each one should take minutes, not hours. The goal is to find gaps while there is still time to fix them.

  1. Confirm the plan. Open the plan details for the account that owns the forecast folder and write down the plan name. The cloud storage page says the deletion window depends on the plan, so the plan name belongs in your record.
  2. Run a deletion test. Create a dummy file in a test folder, delete it, and restore it. Record the path you used and how long it took.
  3. Run an edit test. Change a value in a dummy file, save, and recover the earlier version. Check that the numbers match.
  4. Map the folder. List who can delete, move, rename, or edit the forecast. Remove rights that nobody uses.
  5. Set the rollback date. Choose the oldest version you would need on close day, count back, and confirm that the date falls inside the window.
  6. Check restore access. Make sure the people who may need to restore have accounts and permissions now, not during an incident.
  7. Name an owner. One person decides which version becomes the official forecast after a rollback, and that decision is written down.

Step seven matters more than it looks. A restore that brings back two different versions, each defended by a different person, creates a second problem on top of the first. Someone has to own the choice, and the team has to know who that is before the choice is needed.

Keep your own snapshots

The 30-day figures are good for emergencies. They are not a replacement for a snapshot you control. A snapshot is a copy of the forecast, taken at a known time, that sits outside the day-to-day edits in the shared folder. Consider these habits:

  • Export on a fixed rhythm. A weekly export is a reasonable starting point for a forecast that changes every day. Pick the rhythm that matches your close calendar and keep to it.
  • Date every export. Use a filename pattern such as forecast-YYYY-MM-DD.xlsx so the name tells you the state without opening the file.
  • Snapshot at milestones. The start of the month, the middle of the month, and the day before close are useful fixed points. When someone asks what the number was on a given day, you can answer from a file rather than from a search.
  • Keep one copy with a single administrator. A copy held by one named person, in storage that person controls, means a folder-level mistake cannot remove every copy.
  • Keep a short change log. Record who changed what, when, and why in a close date change log kept next to the forecast. A log does not restore numbers, but it tells you which version to ask for.

Snapshots also help after the close. When finance or an auditor asks how a figure moved during the quarter, a set of dated exports is faster to explain than a long recovery exercise. Keep them where your team can reach them, and decide now how long you will keep them. That retention decision belongs to your finance or IT policy, not to a blog post.

What the figures do not tell you

Be clear about the limits before you build a process on them:

  • They do not state your window if you are on a plan other than the ones described.
  • They do not say that every version of a file is kept. Test your own files.
  • They do not cover a copy after it leaves your Dropbox account. Once a file has been exported or emailed, these windows say nothing about it.
  • They do not replace a backup or retention policy approved by your finance or IT team.

These points are not reasons to distrust Dropbox. They are reasons to write down what you tested and what you confirmed, so the next person on the team does not have to guess.

Bottom line

Three figures, one habit. Know which window applies to your plan, test deletion and edits before close, and keep at least one dated copy outside the shared folder. A forecast that can be rolled back is a forecast your team can defend when a number moves in the week it matters most.

Next step today: open the plan details for the account that owns your forecast folder and write the plan name beside the folder's path.

Related guides: Pipedrive deleted products: check the 30-day restore window · Cancellation billing day: 8 steps to check credit · File size limits: 8 checks before evidence uploads.

Frequently asked questions

How long does Dropbox keep a deleted forecast file?

Dropbox keeps copies of deleted files and folders for 30 days or longer, depending on your plan.

Does the 30-day figure cover every earlier version of a file?

No. The 30-day figure covers recovery of modified files, and how many earlier versions sit inside that window is something to test in your own account.

Is a copy safe once it leaves Dropbox?

Not under these windows. Once a file has been exported or emailed, the recovery windows in this post do not apply to that copy, so keep a dated export of your own.

Sources