At 4:50 p.m. on a Friday, someone needs space on their laptop. They delete a folder called “Old events” that they assume is their own copy. By 4:52 it has gone from 11 other laptops and from the cloud as well.
Nothing malfunctioned. The sync tool did exactly what it is built to do. That is the uncomfortable part, and also the useful one: sync loses files in a few predictable ways, and each one has a plain fix.
How sync decides what is true
A sync tool keeps one folder the same on every device and in the cloud. Each device reports what changed, and the service applies the change everywhere else. It does not ask whether the change was a good idea.
A deletion is a change. So is a rename, a move, or a file overwritten with an older version. Sync copies all of them as faithfully as it copies the work you meant to save. Backup and sync are not the same covers the difference in depth; this article is about the specific ways files go missing.
Five ways files go missing
- Deletions that spread. One person deletes, everyone loses. Common triggers are freeing up disk space, tidying a desktop, or removing a folder that looks like a duplicate.
- Conflicted copies. Two people edit the same file while one of them is offline. When both sync, the tool keeps both and renames one, often with “conflicted copy” in the name. People keep working in the wrong one, and weeks later someone deletes the “duplicate” that held the real changes.
- Moves and renames. Dragging a shared folder into a personal folder can remove it from everyone else’s view. Renaming a top-level folder breaks links inside other documents.
- Files that never entered sync. Work saved to the desktop or a local drive outside the synced folder never leaves the laptop. When the laptop is replaced, it is gone.
- Closed accounts. When a departing person’s account is deleted, the folders that account owned can go with it, including folders the whole team used.
A sixth case deserves its own line: files that do not handle sync well. Database files, accounting company files and some design formats are written in pieces while open. Sync can copy a half-written file, or two people can open it from different laptops and damage it. These files belong on a server or in their own application, not in a synced folder.
Version history helps, within limits
Most business sync tools keep earlier versions and a recycle bin. That is real protection, with two limits.
The first limit is time. Microsoft’s support documentation on the SharePoint recycle bin says that in SharePoint in Microsoft 365, “items are retained for 93 days from the time you delete them from their original location.” A deletion noticed after that window has passed is permanent.
Ransomware tests the same limit from another side. When it encrypts files in a synced folder, every file gets a new, scrambled version at once, and sync sends those versions everywhere. Version history can roll them back, but only if it keeps enough versions and lets you restore a whole folder to a point in time.
The second limit is notice. Version history only helps if someone knows a file is missing, and knows where to look. Folders that are opened once a year, such as last year’s contracts or a closed project, are exactly the ones whose loss goes unseen until a client asks.
This is why the Team Sync plan pairs 180 days of version history with a separate nightly backup of the sync store. A deletion that reaches every laptop does not reach the backup.
Habits that prevent most losses
You can stop most sync losses with a few settings and a short conversation:
- Company-owned folders. Shared folders belong to a shared space or an admin account, never to one person.
- Narrow delete rights. Most people can edit files; only two or three can delete or move top-level folders.
- Co-editing where it works. For documents and spreadsheets, edit the shared online copy rather than offline copies.
- One owner where it does not. For drawings, layouts and other single-user files, agree who holds the file at any time.
- Online-only, not deleted. Teach people to mark folders online-only instead of deleting them to save disk space.
- A backup underneath. Keep a copy of the synced data that a sync deletion cannot reach.
Handling a conflicted copy
When you find a file with “conflicted copy” in its name, resist the urge to delete it. Work through it instead:
- Compare the two. Check the modified time and the author of each, then open both side by side.
- Ask the authors. The people who saved each version usually know which changes matter.
- Merge into the original name. Copy any missing changes into the file with the normal name, so links and shortcuts keep working.
- Move, then delete. Put the conflicted copy in a dated “resolved” folder for a week before deleting it.
If the same file keeps producing conflicts, the cause is usually two people editing it offline. Move that file to co-editing, or give it one owner.
Offboarding without losing folders
The closed-account problem has a simple fix, as long as it happens in the right order. Before a departing person’s account is closed:
- List every shared folder the account owns.
- Transfer ownership of each one to the company’s shared space or an admin account.
- Check that the people who used those folders can still open them.
- Only then close or delete the account.
Put those four steps on your offboarding list beside returning the laptop and the keys.
Example: a deleted folder at an events company
Take a 12-person event planning company. Everything lives in one synced shared folder: contracts, vendor quotes, floor plans, invoices. On a Friday at 4:50 p.m., a coordinator deletes “2025 events” to free up space on a nearly full laptop. The deletion reaches every laptop by 4:52.
Nobody notices on Monday or Tuesday. On Wednesday a client asks for last year’s signed contract to renew, and the folder is not there.
Without a backup underneath. An admin opens the sync tool’s recycle bin. If the folder is still inside the retention window, and nobody has emptied the bin, it can be restored by someone who knows where to look. If it is outside the window, it is gone.
With Team Sync. The office emails support@ezbre.com at 9:15 a.m. on Wednesday. Our target for a single file or folder is within 1 business hour of the request. The folder comes back from version history with its structure intact. If version history had not held it, the separate nightly backup is a second place to look.
Then the cause gets fixed, which is the step most offices skip. Delete rights on top-level folders move to two people, and the coordinator learns the online-only option for freeing space.
A 10-minute sync health check
Run through this with whoever manages your sync accounts:
- Who owns each shared top-level folder: a person or the company?
- Who can delete or move those folders?
- How long does version history last, and who knows how to use it?
- Search for “conflicted copy”: how many are there, and which version is current?
- Are any database or accounting company files sitting in a synced folder?
- When someone leaves, are their shared folders transferred before the account is closed?
- Is there a backup of the synced files that a deletion cannot reach?
If several answers are “not sure,” the backup readiness check scores your setup in six areas and suggests one next step for each weak one. File sync and sharing describes how we run sync for teams, with the backup underneath built in.
A calm next step
Sync losses are rarely dramatic. They are quiet, and they are found late. If you would like a second pair of eyes on how your shared files are set up, the free backup check takes 45 minutes, remotely, includes one test restore, and ends with a written page of findings. Book a free backup check when it suits you.
