What happens if we want to leave?

Why exit is structurally simple

Our product is a governance layer on top of SharePoint, not a separate storage system. When the contract ends:

• Documents stay in the SharePoint libraries where they’ve always lived.
• Version history (minor and major versions) remains intact in SharePoint’s native version engine.
• Audit log events are stored in SharePoint and remain queryable through Microsoft’s audit tools.
• Metadata fields are standard SharePoint columns and continue to function.

What turns off is the active-lifecycle governance itself — the approval flows stop running, the expiration reminders stop sending, the automatic Word-to-PDF transition stops happening. The library becomes a “regular” SharePoint library again.

What exits with you vs stays

Stays with you (in your tenant): all documents, all version history, all metadata, all audit log data that’s in SharePoint.

Turns off at the vendor level: the active-lifecycle layer’s automation, the Power BI dashboards we maintain, our service-account access, our admin console.

Practical consequence

The exit cost is the loss of the governance discipline, not the loss of data. Organizations that leave typically either switch to a different governance tool on top of the same libraries, build a DIY governance layer, or accept that the library goes back to being “just storage.” All three outcomes preserve the content you’ve accumulated.

This matters for audits. A regulator asking about documents five years from now, assuming you left our platform three years ago, still finds those documents in the same SharePoint libraries with the same version history. The evidence chain doesn’t break at the platform-exit moment.