Nobody in a small business decides to run the company’s files on personal sync accounts. It happens one account at a time. A founder shares a folder from a free account, a new hire shares another, and a few years later client files live in nine places owned by seven people.

Consumer sync tools such as Dropbox are designed around one person’s files on several devices, with easy sharing. Moving a team off them is not a judgment on the tool. It is the business taking ownership of its own files. This article lays out how to make that move without losing files, links or a working Monday.

Signs it is time to move

  • Shared folders are owned by personal accounts, some on free plans.
  • People pay for their own storage and expense it.
  • Nobody can say who outside the company can open the client folders.
  • When someone leaves, their folders, and the links clients use, leave with them.
  • A mapped drive, two sync apps and email attachments all hold versions of the same file.

There is also a plain reason to keep your own copy of anything held on a consumer service. The Microsoft Services Agreement, which covers Microsoft’s consumer services, says in section 6.b: “We recommend that you regularly backup Your Content and Data that you store on the Services.” The provider says it plainly.

What business sync changes

Managed business sync feels the same to staff day to day. The ownership underneath is different:

  • The company owns every account and every shared folder.
  • Access is granted by role (“partners,” “admin,” “agents”), not person by person.
  • An admin can see every outside share and switch it off.
  • Leavers are offboarded without losing the folders they owned.
  • Version history and a separate backup sit under the synced files.

The Team Sync plan runs exactly this, from $9 per user per month, with 180 days of version history and a nightly backup of the sync store.

Decide what not to move

A migration is the cheapest moment you will ever have to tidy up. Before you plan the copy, agree what stays behind:

  • Personal files. Family photos and private documents stay with their owners.
  • Duplicates. Where three folders hold the same files, pick one and move only that.
  • Dead archives. Folders nobody has opened in years can go to a single archive folder, still backed up, out of everyday view.

Moving less makes the copy faster, the checks simpler and the new tree easier to learn.

Plan the move in five steps

  1. Inventory. List every account, every shared folder, its size, its owner and who it is shared with, inside and outside the company. Note links that clients, vendors or your website rely on.
  2. Folder map. Write down where each old folder goes in the new structure. Keep the tree shallow: by client, by year or by department, not all three. Decide what stays personal and does not move.
  3. Permissions map. Turn the person-by-person sharing into a few groups. This is the step where most surprises appear, such as a former contractor who still has edit rights.
  4. Links and outside shares. List the links people outside rely on, decide which ones get new links, and draft a short note to those people.
  5. Cutover. Pick a weekend. Freeze the old folders on Friday evening, copy the final changes, check, and switch everyone on Monday morning. Keep the old platform readable for a while in case something was missed.

What tends to go wrong

Most migration problems are small and predictable:

  • Path length and names. Deep folder trees and unusual characters in file names can break when files move between platforms.
  • Files open during the copy. Someone works late on Friday and their edits miss the final copy.
  • Old habits. The old app is still installed, so people keep saving to it on Monday.
  • Big files on slow lines. A few hundred gigabytes of video or drawings can take days to upload from an office connection.
  • Database files. Accounting and other database files should not sit in sync at all.

Each of these has a fix in the plan: a scan for long paths and bad names before the move, a clear freeze time, removing the old app on Monday, an early bulk copy of the large folders, and a separate home for databases. Why sync loses files covers the database problem in more detail.

Example: a 22-person real estate brokerage

Take a brokerage with 22 agents and staff. Listings, transaction files and marketing photos sit across nine personal sync accounts and a mapped drive on an old office PC, about 700 GB in total. Two agents have left in the past year, and one of their accounts still owns the “Closed deals” folder.

  • Week 1: inventory. The scan finds 40 shared folders. Of those, 14 are shared outside the company, with lenders, inspectors and escrow staff. Three hold copies of the same transaction files.
  • Week 2: maps. The new tree has three top folders: Listings, Transactions by year, and Office. Agents edit their own transactions, the managing broker sees all of them, and the office manager owns the structure.
  • Friday, 6 p.m.: freeze. Sharing on the old folders is switched to view-only. Agents get a one-page note on where things moved.
  • Saturday: copy and check. The final changes are copied. File counts and total sizes are compared folder by folder, and 20 files picked at random are opened.
  • Monday, 8 a.m.: switch. Everyone signs in to the new sync. Outside partners get new links with a short explanation.
  • Day 30: close. The old platform has stayed readable for 30 days. With nothing missing, the personal accounts are closed, and the departed agent’s folder now sits safely in the company’s own tree.

At indicative prices, this fits the Sync Migration plan: a fixed fee from $900 for up to 25 users and 1 TB, with files, folder structure, sharing and links mapped, a weekend cutover and the old platform kept read-only for 30 days. Team Sync for 22 users is then 22 × $9, or $198 a month.

What to tell your team

Most of a migration is invisible to staff. The part they see is a short change on a Monday, and it goes better when they hear about it twice.

  • A week before: a short note saying what is changing, why, and the freeze time on Friday.
  • Friday afternoon: a reminder to save and close open files before the freeze.
  • Monday morning: a one-page note with the new folder map, how to sign in, and who to ask.
  • One rule for the first week: if a file seems to be missing, ask before recreating it.

That last rule matters more than it looks. A recreated file is how duplicates start again.

The first 30 days after cutover

The old platform stays readable for a month, and that month has its own short list:

  • Watch for files saved to the old app, and move them across.
  • Check that outside partners are using the new links.
  • Remove the old sync app from each laptop once its owner is settled.
  • Run one test restore from the new backup, so you know the safety net works.
  • Close the personal accounts only when nothing has been missed.

A migration checklist

  • Every account and shared folder listed, with owner and size.
  • A written folder map, old path to new path.
  • Permissions grouped by role, with leavers removed.
  • Outside shares and important links listed, with a note drafted.
  • Database files moved out of sync.
  • Large folders copied early.
  • A freeze time everyone has been told.
  • A check method: counts, sizes and a sample of opened files.
  • The old platform readable for 30 days, then closed.
  • A backup under the new sync from the first day.

If you want to see how the days of an onboarding run in order, how it works, from free check to first restore shows the same rhythm for backup. For terms you meet in migration quotes, the backup and recovery glossary is a quick reference.

A calm next step

A move like this is mostly careful listing. If you would like a clear view of what you have before you plan anything, the free backup check takes 45 minutes, remotely, and includes one test restore and a written page of findings. It is a reasonable first step: book a free backup check.