Title: Heads up — moving/copying files into a folder with same-named files can silently overwrite them, and recovery may be blocked by your plan tier

Title: Heads up — moving/copying files into a folder with same-named files can silently overwrite them, and recovery may be blocked by your plan tier

TL;DR

While cleaning up duplicate files across several of my Box accounts, I asked an AI assistant to move a folder's contents into another folder. Some of the files in the destination folder had the same names as files already there (but different content). Box didn't warn me or ask — it silently uploaded the moved file as a new version on top of the existing file, replacing what was there. When I went to restore the original version from Version History, I found that version history/restore is a paid-plan feature — so even though the old version technically still exists on Box's servers, I can't see it or get it back without upgrading.

Posting this so other users (and anyone using AI assistants to manage their Box files) know to check for this before doing bulk moves/copies.

Background

I have several Box accounts from different periods of my life, and I'd shared/collaborated folders from those accounts into one main account so everything is visible in one place. I was going through a personal folder to find and clean up duplicate files that also existed in a large shared folder (a big old backup with many nested subfolders, one of which held years of personal financial/HR-type records).

I identified duplicates using SHA1 hash comparison (not filename matching — actual byte-for-byte content comparison), confirmed which files were true duplicates, and moved a subfolder plus a batch of confirmed-unique files into that shared folder to consolidate things.

What went wrong

The destination folder already contained files with some of the same names as the ones I was moving in — for example, generic spreadsheets and documents like:

• Report (3).xls
• Report (4).xls
• SummaryData.xlsx

These were different files with different content that happened to share a filename. When the move happened, Box did not:

• Warn me about the naming conflict
• Ask whether to keep both, rename, or skip
• Create a new file with a suffix like "(1)"

Instead, it silently treated the incoming file as a new version of the existing file with the same name — meaning the original file's content was pushed into version history, and the moved file's content became the new "current" version. The file's version badge in Box quietly incremented (e.g. v1 → v2), which is easy to miss unless you already know to look for it.

Why this is worse than it sounds

Normally you'd think "no big deal, I'll just restore the previous version from Version History." That's where the second problem hit:

Version History and restore are paid-plan features on Box. Even though the file clearly showed a version badge (confirming a prior version exists), clicking into Version History returned a server error and "no prior versions available." Logging in as the account that actually owns the file showed the real reason: a paywall screen — "Sorry, version history is not available with your current account plan. To access versioning, select from one of our paid plans."

So the net effect: a routine file reorganization silently destroyed easy access to original file content, with no warning at the time of the action, and the safety net (version history) turned out to be locked behind a subscription I didn't have.

What I'd like Box to consider

1. Warn on filename collision during move/copy, the same way most operating systems and cloud drives do ("A file with this name already exists — Keep both / Replace / Skip"), instead of silently creating a new version.
2. Make it clearer in the UI that a "new version" was just created due to a naming collision, not just a small version badge that's easy to overlook.
3. Consider allowing free-tier users to at least view (even if not restore) their most recent 1–2 prior versions, so people aren't completely blind to what happened to their files.

Practical lesson for other users (and anyone using AI tools to manage Box files)

• Before moving or copying a batch of files into a folder, check the destination for existing files with the same names first.
• Don't assume "move" is a safe, reversible operation — on Box, a name collision means overwrite, not duplicate.
• Don't rely on Version History as a safety net unless you've confirmed your specific account plan actually includes it.
• If you're using an AI assistant (Claude, ChatGPT, etc.) to do bulk file operations on your behalf, ask it to explicitly check for filename collisions in the destination folder first and flag them to you before proceeding.

Hope this saves someone else the same headache. Happy to answer questions if others have run into something similar.