Filevine and SharePoint: what two-way document sync has to get right
Every firm running Filevine alongside SharePoint eventually asks the same question, usually after somebody works for an hour on the wrong version of a demand letter. Why is the copy in our document system not the same as the copy on the matter?
The honest answer is that most of what gets sold as sync is not sync. It is a backup. Files leave the case management system on a schedule and land in a folder somewhere, and that is where the relationship ends. Edit the copy in SharePoint and nothing goes back. Six weeks later you have two document sets and no way to tell which one a paralegal was working from.
Filevine is not the problem here, and we say that as one of their implementation partners. The gap opened up because the bridge firms relied on went away. Neostella retired File Sync for new firms, Fuel Digital moved to one-way, and the no-code options fall over somewhere north of fifty documents a day. So firms are left comparing a backup, a discontinued product, and a $30,000 custom build nobody will support in two years.
What two-way actually requires
If you are evaluating options, these are the four things that separate a real integration from a file copier. Ask about all of them.
1. Conflicts have to be decided by a rule
Two people editing the same document in two systems is not an edge case, it is Tuesday. An associate opens the deposition summary in SharePoint while the case manager edits it in Filevine. Both save. Something has to decide what happens, and “last one wins” is only acceptable if you chose it.
What you want is a choice. Last writer wins is fine for working drafts. Filevine authoritative makes sense when the matter is the source of truth and the DMS is for convenience. Destination authoritative suits firms whose document team works in SharePoint all day. Keeping both versions and flagging one for review is the safest option for anything close to a filing deadline. A product that gives you one strategy and no say is making a decision that belongs to your firm.
2. Loops have to be prevented, not patched
This is the failure that kills the Zapier builds. A change in Filevine writes to SharePoint. SharePoint fires a change webhook. That webhook writes back to Filevine. Which fires another webhook. By lunchtime you have 400 versions of one PDF and an API rate limit error.
The fix is not a delay or a retry cap. Every write has to carry metadata saying which system originated it, so the inbound event can recognize its own echo and stop. If a vendor cannot explain how they do this in one sentence, they have not solved it.
3. Names and paths will break, quietly
Filevine has a 250 character limit on document paths. SharePoint has its own limits and its own opinions about characters. Real legal filenames are long, and they contain brackets, ampersands and case numbers. A sync that does not handle truncation intelligently will either fail silently on a small number of documents or, worse, rename them in a way that makes them unfindable later.
The right behavior is to shorten what has to be shortened, keep the original name recorded somewhere you can query, and never drop a file on the floor.
4. You need proof, not a status light
When a partner asks whether every document on a case is in both systems, “the integration is running” is not an answer. You want a log of every sync event, a queue of anything that conflicted, a retry history for anything that failed, and a way to see volume over time. This is also what your auditor will ask for, and what you will want the first time a client requests a complete file.
Backup is not sync, and the difference shows up in six weeks
Filevine’s native SharePoint integration is a genuinely useful backup. It is not designed to be a working document environment, and it does not claim to be. The distinction matters because the failure is invisible at first. Everything looks fine for the first fortnight. The drift starts when somebody edits outside the case management system, which they will, because that is where the rest of their day happens.
Here is a test worth running on any option you are considering. Open a document from the DMS side, change one line, save it, and go look at the matter in Filevine ten minutes later. If the change is not there, you are looking at a backup.
Where MatterOrbit fits
We built MatterOrbit because our own clients kept asking for this after the Neostella exit, and because we were already doing the Filevine implementations underneath. It is a Filevine approved integration, it syncs both ways with SharePoint, OneDrive and Dropbox, it handles the four problems above by design, and it starts at $575 a month rather than a custom build quote.
If you are moving onto Filevine at the same time, the sequence matters. Migrate the existing SharePoint files into Filevine first, into the right matter and the right folder, then turn the sync on. Start in sync rather than spending your first quarter catching up. That is the same migration work we do for firms coming off Needles, Neos and ProLaw, so it tends to be one project rather than two vendors.
If you want to see it running on your own matters, that takes about twenty minutes and no data moves until you say so. Tell us what you are running and we will show you the specific case.
