A second office usually means a second file mess. Drive ShareSync is Synology's answer: put a NAS in each office, and the same Team Folders quietly stay identical on both — each office working at local speed. Here is how it works and what to decide before switching it on.
Emailing files between offices and wondering which copy is current is a tax every multi-site business pays daily. Synology Drive ShareSync removes it: it is the part of the Drive Server package that synchronises Team Folders between Synology NAS devices. Staff in both offices open the same folder from their own local NAS — fast, familiar, and always in step. The setup is simple; the decisions around it deserve a page of their own.
One NAS hosts the Team Folder with Drive Server running — call it the main side. On the second NAS, you open Synology Drive ShareSync, connect it to the first NAS (by its address, DDNS name or QuickConnect ID, with an admin-level account), choose the Team Folder, and pick where it lands locally and which way it syncs. From that moment the two folders mirror each other over the connection: a save in the branch appears at head office, a save at head office flows down to the branch. The second NAS's own users then sync their PCs to their local NAS, so day-to-day work never crosses the internet at all.
ShareSync offers three directions, and the right one depends on how your offices actually work:
Pick per folder, not per NAS. Most offices end up with a mix, and that is a sign the choice was made thoughtfully.
The first sync is the mountain: an existing 800 GB folder must cross your internet connection once, and on a typical office upload speed that is days, not hours. The professional trick is to do the heavy part on the LAN — bring the second NAS to head office (or copy the data to it locally), let ShareSync complete its first pass at local speed, then ship the NAS to the branch. After seeding, daily changes are small and the internet link keeps up easily. Skipping this step is how sync projects earn a bad name in week one.
ShareSync keeps folders in step; it cannot make two people in two cities into one typist. If the same file is edited at both ends before a sync passes, one version wins and the other is preserved as a conflicted copy for a human to sort out. Versioning on the Team Folder softens this further — earlier states remain restorable. But the real fix is social, not technical: agree ownership per folder (this project's files are edited at the branch; accounts only at head office) and conflicts become rare events instead of weekly chores.
After seeding, ShareSync traffic is roughly the size of your team's daily editing — documents are small, and the system settles quickly. The exceptions are folders full of large media or database-style files that change wholesale; a single 4 GB video re-save is a 4 GB trip across your link. Put such folders on a schedule-friendly footing, watch the branch's upload speed (the number home and small-office connections are worst at), and remember both offices also share their links with everything else they do online.
The video shows the full Synology Drive setup this builds on — Team Folders, versioning and clients — the foundation every ShareSync deployment needs first.
▶️ Watch Full VideoNo. ShareSync is part of Synology Drive Server and works Synology-to-Synology only — both ends must be Synology NAS units running Drive. That is the price of how neatly it integrates with Team Folders and versioning.
No. The second NAS can reach the first by a DDNS name or QuickConnect ID, so offices on normal dynamic-IP connections can still stay in sync. What matters is a stable name and a connection that is up — not a fixed address.
Both offices keep working normally on their local NAS — that is the beauty of the design. Changes queue up on each side and flow through when the connection returns, with any true clashes preserved as conflicted copies to review.