Why Box Matters for Both Law Firms and Corporate Teams

Many firms maintain a Box presence specifically to work with clients and external advisors on their preferred platform. Today, getting NetDocuments content into Box workflows generally means a manual export, which strips away the metadata and governance that made the document trustworthy inside NetDocuments in the first place.

Use Cases a netDocShare + Box Integration Can Support

  • Client collaboration on Box: Firms whose clients standardize on Box could sync relevant matter content there, the way netDocShare Sync mirrors content into SharePoint today.
  • Governance parity with existing sync targets: A Box integration aims to preserve Document IDs, metadata, and Ethical Wall permissions consistent with netDocShare's existing approach to SharePoint sync.
  • Migration support: Firms migrating content from Box into NetDocuments could use a governed sync or migration path rather than a one-time manual transfer.
  • Consistent collaboration model across platforms: Firms working across Microsoft 365 and Box clients could apply a consistent sync and governance approach regardless of which platform a given client uses.

Frequently Asked Questions

Would Box sync work the same way as SharePoint sync?

The intent is governance parity preserving Document IDs, metadata, and Ethical Wall permissions consistent with how netDocShare Sync already works with SharePoint.

Why would a firm need Box integration if it already uses SharePoint?

Some firms maintain a Box presence specifically because their clients standardize on Box, separate from the firm's own internal Microsoft 365 environment.

Could this help with migrating content from Box into NetDocuments?

That's one of the use cases a governed sync or migration path rather than a one-time manual transfer.

Will our existing NetDocuments sync jobs automatically follow our SharePoint migration?

Not automatically. Sync jobs need to be deliberately reconfigured to target the new SharePoint Online environment.

Should we migrate SharePoint and reconfigure sync at the same time?

The sequencing should be planned carefully to avoid a window where content isn't syncing at all.

Do metadata mappings carry over automatically?

They should be validated again after migration, since site and library structures in SharePoint Online may differ from the on-premises setup.

Is this a good time to clean up our sync configuration?

Yes, a SharePoint migration is a natural opportunity to review and simplify sync job configuration.

Tell us about your firm's or your organization's Box use case to help shape this roadmap.

Request a Demo →

Quick Answer

A netDocShare integration with Box is being explored to support both law firms that run Box internally and corporate legal teams that standardize on Box independently, aiming for governance parity with existing SharePoint sync preserving Document IDs, metadata, and Ethical Wall permissions along with potential use cases in firm-side collaboration, corporate self-service access, and migration from Box into NetDocuments.

Key Takeaways

  • Box is a primary content platform for many law firms and many corporate legal teams alike, not a secondary system for either side.
  • Some firms run Box internally; many corporate teams standardize on Box independent of their outside counsel's tooling.
  • A Box integration would aim for the same governance parity netDocShare provides for SharePoint sync, regardless of which side initiates it.
  • Migration from Box into NetDocuments is one potential use case for a governed sync path, for firms and corporate teams alike.