Home › Knowledgebase › KB-1534

Move Ndis Participant Records To Sharepoint With Access Controls

Summary

This guide helps you troubleshoot and resolve: Move Ndis Participant Records To Sharepoint With Access Controls. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Move NDIS Participant Records to SharePoint with Access Controls

NDIS providers manage sensitive participant files that require strict privacy controls and auditability. This article outlines the process of migrating legacy network drive data to SharePoint Online while meeting Australian Privacy Act obligations and NDIS compliance requirements. It covers pre-migration cleanup, access control mapping, sharing restrictions, and secure decommissioning of legacy hardware.

Compliance and Security Context

Participant records are classified as sensitive information under the Australian Privacy Act 1988 and the Australian Privacy Principles (APPs). NDIS providers must also consider obligations under the Notifiable Data Breaches (NDB) scheme. Before migrating data, confirm that your Microsoft 365 tenant is configured to store data in an Australian data centre to satisfy data residency requirements.

Security requirements before migration:
  • Enable multi-factor authentication (MFA) for all administrator and staff accounts accessing SharePoint Online.
  • Configure Conditional Access policies in Microsoft Entra ID to restrict access from unmanaged devices or high-risk locations.
  • Disable external sharing at the organisation level unless specifically required, and restrict sharing links to People in your organisation or Specific people only.
  • Never use Anyone links for NDIS participant records, as these can be forwarded and accessed by unauthorised individuals outside your organisation.

Planning Your Migration

Review your current network drive structure and identify folders containing participant records, staff files, and operational documents. Map each folder to a Microsoft 365 group or security group that should have access to the corresponding SharePoint library. This ensures only authorised personnel can view sensitive participant information.

Pre-migration cleanup:
  • Delete redundant, obsolete, or trivial (ROT) files before migration.
  • Rename files containing invalid SharePoint characters such as ", *, :, <, >, ?, /, \, and |.
  • Shorten deeply nested folder paths to avoid SharePoint path length limits.
  • Close all open files and ensure no participant records are locked by other applications before starting the transfer.

Migration Steps

Step 1: Create the SharePoint Site

  1. Sign in to the Microsoft 365 admin centre using your administrator account.
  2. Select the App launcher, then choose SharePoint.
  3. In the SharePoint admin centre, select Active sites from the left-hand menu.
  4. Click Create and choose Team site or Communication site based on your needs.
  5. Enter a site name, such as NDIS Participant Records, and complete the creation wizard.

Step 2: Create Document Libraries

  1. Navigate to your new SharePoint site.
  2. Select New, then choose Document library.
  3. Give the library a name that matches your existing folder, for example Participant Files.
  4. Repeat this process for each major folder you plan to migrate.

Use clear, consistent naming conventions for libraries so staff can locate records quickly after the migration.

Step 3: Map Permissions to Microsoft 365 Groups

  1. In SharePoint, open the document library you want to secure.
  2. Select the Settings gear icon in the top-right corner, then choose Library settings.
  3. Under Permissions and Management, select Permissions for this document library.
  4. Click Stop Inheriting Permissions if you need unique access rules for this library.
  5. Select Grant Permissions and enter the name of the relevant Microsoft 365 group or security group.
  6. Choose the appropriate permission level, such as Read, Edit, or Full Control.
  7. Click Grant to apply the permissions.

Do not assign permissions to individual users where possible. Use Microsoft 365 groups so access can be managed centrally when staff join or leave your organisation.

Step 4: Migrate Data to SharePoint

  1. Download and install the SharePoint Migration Tool from Microsoft.
  2. Sign in with your global administrator or SharePoint administrator credentials.
  3. Select Upload to move files from a file share or local path.
  4. Specify the source path on your network drive, for example \\Server\NDIS\ParticipantRecords.
  5. Select the destination SharePoint site and document library.
  6. Review the migration settings and start the transfer.
  7. Monitor the migration report for any failed files and resolve permission errors before proceeding.

If a file is open or locked during migration, the tool will skip it. Close the file, then run a delta migration to transfer only the changed or missed items.

Step 5: Configure Sharing Links and Version History

  1. Go to the document library in SharePoint.
  2. Select the Settings gear icon, then choose Library settings.
  3. Choose Versioning settings.
  4. Under Document Version History, select Create major versions.
  5. Optionally enable Create minor versions if you need draft tracking for participant care plans.
  6. Set a limit on the number of versions to retain, such as 50 major versions.
  7. Click OK to save.

To configure sharing links:

  1. Select the file or folder in SharePoint.
  2. Click Share.
  3. Choose People in your organisation or Specific people rather than Anyone.
  4. Set the link to Can view or Can edit as required.
  5. Click Apply and copy the link to share with authorised staff.

Ransomware Protection and Data Recovery

Version history protects against accidental deletion and ransomware by allowing you to restore previous versions of files. Configure the SharePoint recycle bin and retention policies to ensure deleted participant records can be recovered within an appropriate timeframe.

  • Items deleted from a SharePoint library go to the site recycle bin for 93 days by default.
  • After 93 days, items move to the site collection recycle bin for a further period before permanent deletion.
  • Use Microsoft Purview retention policies to retain participant records for the period required by NDIS and privacy obligations.
  • In the event of ransomware, restore files from version history or use the recycle bin to recover unencrypted copies.

Decommissioning and Secure Disposal

  1. Ask a sample of staff members to access the SharePoint libraries from their usual workstations.
  2. Confirm they can open, edit, and save participant records without errors.
  3. Verify that staff who should not have access are unable to view restricted libraries.
  4. Run a final synchronisation of any remaining changed files from the network drive.
  5. Once verified, power down the physical server and arrange for secure disposal of hard drives.

Hard drives containing sensitive participant data must be sanitised in accordance with NIST 800-88 or an equivalent recognised standard. Obtain a certificate of destruction from your disposal vendor and retain it as evidence of compliant asset disposal.

Troubleshooting

Permission Errors After Migration

If users cannot access folders they previously could, check that the corresponding Microsoft 365 group has been granted permissions in SharePoint. NTFS permissions do not automatically transfer; they must be recreated using SharePoint groups or Microsoft 365 security groups.

Files Fail to Upload

SharePoint has restrictions on certain file types and path lengths. Rename files that contain invalid characters and shorten deeply nested folder paths before retrying the migration.

Version History Not Working

Ensure versioning is enabled at the library level, not just the site level. If files were uploaded via sync client, confirm the sync completed fully before relying on version history.

Locked or Open Files

If the migration tool reports a file is in use, close the application holding the file open, then run the migration again to transfer the missed items.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket