IT systems · Practical guide

Migrating SOPs to SharePoint: preserving history and approvals

The SOP files have arrived in SharePoint, but earlier revisions, approvals or original authors may be missing. Test whether users can still retrieve the content and context required for the regulated document process, including historical enquiries.

Table of contents

At a glance

What should you test when migrating GxP SOPs to SharePoint?

Define the documents, versions, metadata, approvals and relationships to preserve. Use representative reference packages to test the migration tool, mappings, identities and permissions. After transfer, reconcile completeness, business meaning, historical access and the authoritative effective version. Bring the old process to a controlled end only after those checks.

Understand data transfer during system migration

A SOP comprises more than a single file within a regulated process. Depending on its intended use, the content, revision status, approvals, validity, training linkage, and change history must be accessible. Effective documents, drafts, withdrawn versions, and retention-required historical records should be segregated. Not all content needs to reside in the same target environment. However, the decision must be traceable and enable future usability.

This guide addresses controlled transfer in SharePoint Online. The existing storage may be a network drive, SharePoint Server, or another document management system. This results in different technical options. A migration tool for SharePoint Server does not automatically cover transfers from every QMS. Before defining test cases or acceptance criteria, describe source, destination, tool used, and relevant versions.

Sources: [1] [2]

What is obtained, depicted, or separately archived

Prepare a technical inventory. Capture document ID, title, revision, status, expiry date, owner, and relevant relationships. Supplement with required approval and training documentation. Explicitly determine which information is to be structured and migrated to SharePoint and which remains in a controlled historical archive. A link to the legacy system is only viable if the system continues to be actively operated and remains accessible.

Be aware of semantic shifts. The technical modification date following an upload is not automatically equivalent to the original approval date. A migrated author shall not be substituted by the technical migration user if the original identity is required as proof. The same applies to status designations: "Approved" and "Effective" may represent different states. Document the mapping and evaluate known edge cases, rather than merely aligning fields that sound similar.

Sources: [1] [3]

Define and distinguish between tools and transfer procedures correctly

Microsoft documents specific settings for version inheritance and user assignment within the SharePoint Migration Tool. When version inheritance is disabled, only the most recent file version is migrated; when version inheritance is enabled, version boundaries can be defined. These options must align with the technical and operational concept. The documentation does not describe a generic import of all approval or workflow records from arbitrary external systems.

Copying and moving within SharePoint are not equivalent. Microsoft outlines differences regarding preserved version history and metadata conditions. Therefore, do not select solely based on speed. Evaluate the specific pathway using a small, representative dataset prior to scaling. Document settings, permissions, error logs, and retry behaviors. A subsequent run must neither generate undetected duplicates nor overwrite previously verified target information with an older version.

Sources: [4] [5]

Example: Reference package prior to first run

The example includes SOP-042 with three historical revisions and one current draft. Revision 3 is currently effective, while Revision 4 is still under review. A approval originates from a former employee; a training confirmation is maintained as a separate record. The reference package captures the content and interrelationships prior to migration and is evaluated independently of the subsequent import report.

Upon takeover, a reviewer must identify the revision valid as of the cut-off date and demonstrate understanding of its approval. The new draft must not appear to be effective. A technical upload timestamp shall be treated as such and shall not be issued as the original release date. The following matrix is an internal work aid. It is customized for document types, source, and target, and does not represent a legally mandated table format.

Example reference package to prepare before the first run
ComponentShould be performed prior to migrationAcceptance in target
Document identity SOP-042 unambiguously Obtain ID and relevant references
Effective Revision Revision 3 as of the cut-off date Correct content and status
Open Draft Revision 4 without efficacy No unintended use in production
History Three required old batches Retrievable and correctly identified
Approval Person, Time Point, Revision Related evidence
Training Regarding the significant status Historical context remains understandable

Sources: [1] [2]

Check completeness and meaning in the process separately

A file count is a good starting point: number of documents, versions, attachments, and relationships. Clearly define the counting unit. Identical file numbers do not rule out missing prior versions or incorrectly assigned releases. For files transferred without modification, appropriate integrity checks can assist. For files converted between formats or newly generated outputs, both content and meaning are assessed.

Targetedly assess documents with specific characteristics: special characters, long file names, missing user accounts, linked attachments, withdrawn revisions, and corrupted source files. Justify the selection based on actual differences. A generic sampling rate is not an acceptable substitute. Automated full document reviews are suitable for structured attributes; expert review cases evaluate the interrelationships. Findings are investigated for systemic root causes. A mapping error in one revision may impact numerous other documents.

Sources: [1] [3]

Assume permissions and historical identities

Assess permissions in the target system based on the intended use, not merely on the previous folder structure. Inherited authorizations, guest access, and group memberships may have changed. Test authors, reviewers, standard readers, and a user with no permissions. Specifically verify whether historical documents or drafts inadvertently become visible to all users. A technically successful migration may simultaneously result in excessive access.

Legacy identities require a traceable assignment. A former employee does not need to be reissued an active account merely to ensure their historical authorizations remain understandable. A suitable, preserved identity verification is required. Technical migration actions related to historical authorizations or approvals must be separated. Additionally, verify that references to training or quality records continue to function. A preserved string holds little value if it points to a data set that is no longer accessible.

Sources: [4] [1]

Cut-off, Delta, and Transition to the New Process

Set a binding take-over date and the treatment of subsequent changes. During a first test import, further permits can be obtained in the old system. These changes belong in a controlled delta or final run. Document the status that has been definitively taken over and how completeness has been proven. A successfully tested pilot migration does not automatically prove the later productive finish run.

Plan a failover with clear triggers and responsibilities. Avoid an ambiguous dual operation in which two locations claim leadership. Define where personnel search for documents after the transition and how legacy links are managed. Training and communication are integral to the process transition. Prior to decommissioning the source, verify that historical retrieval, retention, and restoration under the intended concept are actually feasible.

Sources: [1]

Acceptance Report and Future Operation

The report integrates inventory, mapping, implemented procedures, result comparisons, technical assessments, and outstanding items. Clearly define limitations. If approvals remain in a separate archive, access to that archive must be part of the solution. A mere statement "history remains available" is insufficient without a defined location, responsible party, and historical review capability. Critical gaps must not disappear behind the closure of a completed technical task.

Provide document linking, permissions, retention, recovery, and change rules to operations. A migration can establish a solid initial baseline, which may be undermined by incorrect library settings. Therefore, also evaluate the next standard workflow: create a new revision, approve it, implement it, and retrieve the prior state. Only through this workflow can it be determined whether the transferred information is effectively continued in the new process.

Sources: [1] [2]

Project experience and collaboration

Check whether users can access the required document history after migration

Your document owners choose a small, familiar set of records with several versions and approval states. Before migration, we establish which contents, identities and relationships must remain available in the target. A suitable tool can help transfer them. Historical functions unavailable there need a separately tested access route. In the rehearsal, future users open the required versions with their assigned roles as well as comparing file counts. Joint acceptance includes the final change between rehearsal and cutover.

Frequently asked questions about Migrating SOPs to SharePoint

Are all SOP versions uploaded during an upload?

Not automated. A simple upload typically includes only the selected file version. Migration tools have their own options and limitations regarding version histories. Review the specific transfer method and ensure the required versions are matched in the target system. Approval records require separate evaluation.

Sources: [4]

Can old releases be simply imported as SharePoint status?

A status value alone does not constitute adequate approval evidence. Verify the decision-maker, timing, affected revision, and, if applicable, the significance of the confirmation. If the objective does not adequately capture these information elements, a controlled linked archive may be required. Historical and new releases must remain distinguishable.

Must all historical SOPs be re-authorized?

Not blanket. A historically approved change can be retained if correctly implemented. However, changes to content, format, process, and credibility must be assessed. If the implementation alters the significant relationship or is not adequately supported, a proper evaluation and, if necessary, renewed approval is required.

Is a hash comparison sufficient as a migration validation?

It can provide evidence of unaltered file transfer, but does not address all questions. Metadata, versions, authorizations, rights, and relationships must also be consistent. For converted files, an identical hash is not expected. There, the content and required meaning are verified using appropriate procedures.

What happens to authorizations of decommissioned employees?

Obtain the necessary historical identity and its connection to the decision. A new active user account is not automatically required for this purpose. The mapping must not assign the previous authorization to the migration user. Verify that a subsequent reviewer still clearly understands the relationship.

When may the old document management system be decommissioned?

When the required information and retrieval pathways are demonstrated and duly assigned responsibility within the approved target concept, consideration must be given to residual accesses, delta changes, retention, and rollback. The mere availability of current SOP files in SharePoint does not constitute a complete validation evidence.

Sources: [1]

Sources and review date

As of October 14, 2026. Regulatory classification and manufacturer responsibilities are separately documented. Examples, test matrices, and templates are standalone reference tools; they are customized for actual usage purposes.

  1. European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
  2. European Commission: EU GMP Chapter 4, Documentation (2011)Document routing and records. Electronic documents, their control, and the required retention must be considered in conjunction.
  3. PIC/S: PI 041-1, Good Practices for Data Management and Integrity (2021)Inspection Guidance on Data Integrity; in particular electronic data, transmission, access, and review.
  4. Microsoft: SharePoint Migration Tool settingsVersion inheritance and user/permission assignment are separate settings, not a blanket retention of all workflow records. Reviewed on 14.10.2026.
  5. Microsoft: Move or copy files in SharePointMoving and copying differ in version history; adhere to metadata conditions. Reviewed on 14.10.2026.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

How we can support you

Daniel Herrmann Consulting combines professional assessment with hands-on work on the specific system. During the first meeting, we clarify your intended use, existing documentation, and the next most appropriate action step.

  • GxP system decommissioning →

    Retire legacy systems while preserving data, context and auditability. We plan and manage the decommissioning so that data, metadata and audit trails remain readable and retrievable after shutdown.

Send a project enquiry Customer testimonials →