Law FirmHow setup runs, and what two-way actually requires
Nothing moves until you say so. Filevine stays the record; SharePoint gets a live, working copy.
How setup runs
Nothing moves until you say so.
Setup call
We look at your Filevine structure, your SharePoint sites and libraries, your backfill volume and the conflict policy you want. Nothing moves until you say so.
Mirror
Setup is scoped on the call. A standard mirror, your current Filevine structure copied into a fresh SharePoint location, is the simplest case; mapping work with exceptions per matter type, or folders that need restructuring first, takes more.
Backfill and switch on
Existing documents are brought across and verified, then the webhooks take over. If you are moving onto Filevine at the same time, the SharePoint files are migrated into the right matters first and you start in sync; that is the same migration work Micronetbd does for firms coming off Needles, Neos and ProLaw, so it is one project, not two vendors.
Run
The dashboard shows sync health, volume and the conflict queue, and every event is in the audit trail. Every sync event runs detect, diff, resolve, transfer, verify; a hash match confirms each transfer before the audit record is written, and failed operations retry with backoff.
Extend
OneDrive, Dropbox and Google Drive can be added as connectors later, with the same conflict rules and the same audit trail.
Backup is not sync, and the difference shows up in six weeks
A scheduled copy is a useful backup. It is not a working document environment. Here is a test worth running on any option: open a document from the SharePoint side, change one line, save it, and look at the matter ten minutes later. If the change is not there, you are looking at a backup.
| Scheduled copy or no-code automation | MatterOrbit two-way sync | |
|---|---|---|
| Edit made in SharePoint | Stays in SharePoint; six weeks later there are two document sets | Lands back on the matter |
| Two people edit the same document | Last one wins, whether you chose it or not | Five strategies the firm chooses from; every decision recorded |
| Webhook loops | The failure that kills no-code builds: 400 versions of one PDF by lunch | Every write carries sync-source metadata, so the echo is recognised and stops |
| Long legal filenames | Fail silently or get renamed into something unfindable | Shortened to fit, original kept in the middleware, document stays findable |
| Proof | A status light | Every event logged, a conflict queue, a retry history, volume over time |
| Volume | Falls over somewhere north of fifty documents a day | Near real time off webhooks, a poll fallback and a nightly sweep |
| Cost shape | A $25,000 to $40,000 custom build nobody will support in two years | One monthly subscription quoted for your firm |
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.
- Conflicts decided by a rule the firm chooses, never a silent overwrite
- Loops prevented by sync-source metadata on every write, not patched with delays and retry caps
- Names and paths handled: a name over Filevine's 250-character path limit is shortened to fit while the original is kept and queryable
- A log of every sync event, a conflict queue, a retry history and volume over time
- Near real time off webhooks, a 5-minute polling fallback, a nightly reconciliation sweep across every matter
- Microsoft Graph with Azure AD per-tenant consent; SOC 2 Type 2 controls apply
Book a setup call
Bring your matter structure and your SharePoint sites. We will scope the mirror, the backfill and the conflict policy, and quote the subscription for your firm.