All the files may be copied over to the cloud, successfully opened, and the legacy systems decommissioned.
Regulated firms must also be able to prove that transferred records still meet their recordkeeping obligations
All elements of the document could be transferred successfully, but associated details may be missing or inaccurate, such as key dates, permissions or applicable retention periods. All of these factors may be relevant to establish the provenance of a record.
Careful planning can reduce these risks.
What you’ll learn:
- Why Moving Every File Is Not Enough
- Know What Is on the Network Drive
- Four Recordkeeping Risks to Watch For
- Build Compliance Checks Into the Plan
- Test the Records Before Switching Off the Server
- Wrapping It Up
Why Moving Every File Is Not Enough
Being able to successfully open a file will not be sufficient in all circumstances.
Additional information may be required, such as creation and amendment dates, identity of the amending user, identification of an agreed final version or appropriate security controls. All may be lost as a result of moving records, potentially calling into question the reliability of the record itself.
As highlighted above, the integrity of records following conversion has been flagged by regulators, with the FINRA 2026 Annual Regulatory Oversight Report referring to inadequate procedures to ensure converted paper records were an accurate, complete and readable representation of the original. Whilst this is related specifically to converting paper records, similar considerations would apply.
In January 2025, the SEC announced $63.1 million in combined civil penalties against nine investment advisers and three broker-dealers for failing to preserve required electronic communications sent through unapproved channels. The cases did not involve cloud migration.
Know What Is on the Network Drive
It will first be necessary to establish what information is currently held on the relevant network share or shares.
It is likely that various types of information will be co-mingled, including records relating to live matters, historic drafts and redundant information, some of which may still need to be retained. Alternatively, staff may store non-business related material or information that could be disposed of.
As a first step, it would be beneficial to categorise the broad types of information, allocate an owner to each and ascertain whether any applicable retention requirements or holds apply. This should allow live records to be distinguished from information potentially available for disposal.
It can then be determined where each type of information should be located post-migration. A SharePoint migration tool, such as the MacroView Migrator, can facilitate the migration to an appropriate SharePoint architecture. However, decisions would need to be taken over the desired layout and associated metadata and permissions.
Input from relevant staff, including those with records management responsibilities, would be beneficial at this stage to ensure appropriate considerations are made over specific types of records, and amendments made ahead of implementation.
Four Recordkeeping Risks to Watch For
Migration can affect several important parts of a record:
- Associated information. Various aspects may be useful or necessary to evidence in relation to a record. Failure to appropriately transfer and populate associated information may therefore impede users’ ability to locate relevant information. An example, the date a record was last amended may overwrite the original date following migration. It would be prudent to understand the nature of each relevant data point pre- and post-migration.
- Versions. Where records are maintained within an application with version control functionality, all prior iterations may be available. Alternatively, records on a network drive may have multiple drafts available. If migrating from SharePoint, various options are available as to the extent of versions to be migrated. However, this functionality would likely be unavailable if migrating from a generic network drive.
- Appropriate permissions applied. Folders containing sensitive client information may be accessible to too many people, while other users may be unable to retrieve records needed for a regulatory information request. Accordingly, existing permissions should be assessed to ensure they align with user roles and requirements.
- Applicable retention requirements. Records may attract specific minimum retention periods or be subject to holds. Conversely, personal data may need to be deleted once it is no longer needed, subject to any applicable legal basis for longer retention. As an example, the ICO expects that personal data should only be retained for as long as necessary to fulfill the relevant purpose, save for certain circumstances. These requirements would continue to apply once migrated to an alternative location.
Each would require an appropriate protocol and verification.
Build Compliance Checks Into the Plan
Accordingly, the project plan should set out relevant actions and responsibilities for each function involved, such as IT, records management, information security and compliance. In particular, it should be clear as to the scope of information to be migrated, approach for any outliers and who would sign off completion.
Actions may include:
- Agree protocols to apply to categories of records, including owner, location following migration, retention period and appropriate access;
- Identify key data points to ensure are appropriately carried over, or otherwise addressed;
- Log any files failing to migrate, excluded or otherwise manually adjusted, with an assigned individual to complete outstanding actions;
- Maintain appropriate controls over original records pending completion of testing and sign-off; and
- Agree communications to users as to the new locations and contacts for raising queries.
Care should be taken not to presume all requirements are satisfied as a consequence of storing records on the cloud.
For broker-dealers that preserve required records electronically, SEC Rule 17a-4(f) permits either a compliant audit-trail system or preservation in a non-rewriteable, non-erasable (WORM) format. It would therefore be necessary to consider how records on SharePoint would meet these expectations.
Appropriate use of Microsoft 365 retention policies and labels may be helpful, subject to suitable application and verification.
Test the Records Before Switching Off the Server
Completion of all migrations should prompt further review and verification. This would include reconciling the number of files expected against those actually migrated and addressing discrepancies. Users with permission to access key records should be asked to locate and retrieve examples, including exporting.
A pilot should be undertaken prior to wider implementation to test samples of records attracting each consideration highlighted above.
FINRA’s 2026 report describes testing recordkeeping providers by simulating regulator requests for records. Firms should also check that they can retrieve the required records and supporting details.
Appropriate records should be maintained of tests undertaken and remedial action taken, and existing locations only decommissioned following sign-off by key users and in accordance with any applicable procedures.
Wrapping It Up
Appropriate steps should be taken to facilitate ease of access to records following migration, but avoid compromising information useful to evidence key aspects of a record.
With suitable advance consideration of information held and protocols to apply, and testing performed, this can be achieved to aid future compliance with record retention obligations.