Can we use our existing SharePoint library?

How the layer attaches

During implementation, we configure the active-lifecycle layer to govern specific SharePoint document libraries. The libraries themselves don’t move. Documents inside them stay where they’ve always been. What changes is the governance behavior applied on top — templates become enforced, approvals become structured, audit logs attach to each document.

What happens to existing content

Existing documents in those libraries. By default, existing documents continue to be accessible and usable. They can be brought into the active-lifecycle governance individually (assigned owners, reviewed, given expiration dates) or left in a “legacy” state that’s visible but not yet governed.

Existing metadata. SharePoint columns that already exist become available to the governance layer. We often add new columns (protocol code, document type, expiration date) but don’t remove existing ones.

Existing permissions. The SharePoint permission model is preserved. We don’t replace it.

When a new library is better

Sometimes we recommend creating a new governed library rather than retrofitting an existing one:

• The existing library has thousands of uncontrolled documents that would take longer to assess than to archive.
• The existing library has inconsistent metadata that’s not worth cleaning up.
• Organizational change wants a clean-slate library that signals “this is the governed library going forward.”

In these cases, we set up a new library, migrate the critical documents from the old one, and archive the old library in a read-only state for audit-retrieval purposes.

Practical recommendation

Start by reviewing your existing libraries. For libraries that have reasonable structure and contain important documents, retrofitting is usually the right call. For libraries that are chaotic and full of low-value content, a fresh start with selective migration is cleaner.

We’ll walk through your specific situation during implementation assessment.