Answer: Migrating HR files between cloud storage platforms — Google Drive, SharePoint, Nextcloud, Dropbox — is a routine IT task that carries serious compliance risk when handled carelessly. A governance-first migration preserves permissions, maintains audit trails, and ensures sensitive employee records land in the right place with the right access controls.

Key Takeaways

• HR file migrations require a pre-migration access audit to avoid exposing restricted records
• Make.com automates the transfer and logs every file moved — creating your audit trail
• Never migrate personnel files and general HR files in the same batch — permissions differ
• Verify file integrity (hash check) before decommissioning the source system
• Document the migration in your data map — regulators expect it

Cloud file migrations are one of the highest-risk moments in HR data governance. Securing HR data workflows must extend to how you move files between systems — not just how you store them. Here is a step-by-step governance approach for any HR cloud migration.

Before You Start

You need: an inventory of every folder and file to be migrated, a classification of each file type (personnel record, payroll, general HR policy, etc.), the permission matrix for the destination system, and a rollback plan. Do not start moving files until all four are documented.

Step 1: Audit the Source Folder Structure

Run a folder listing of your source cloud storage and export it to a Google Sheet. For Google Drive, use the Drive MCP or a Google Apps Script to export file ID, name, folder path, owner, and last-modified date. This inventory is the baseline for your migration audit trail.

Step 2: Classify Every File Before Moving It

Tag each file in your inventory spreadsheet with its classification: Personnel Record (restricted), Payroll (restricted), Benefits (restricted), Policy (internal), or General (unrestricted). Files in the first three categories require tighter destination permissions and separate migration batches.

Step 3: Build the Destination Folder Structure First

Create the full destination folder hierarchy in your target system before moving a single file. Apply correct permissions to each folder at creation time — not after migration. This prevents a window where files exist in the destination without correct access controls.

Step 4: Automate the Transfer with Make.com

Use Make.com with Google Drive or Nextcloud modules (or HTTP calls for other platforms) to transfer files folder by folder. Build your scenario to: read each file from source, upload to destination, log the transfer (source path, destination path, file ID, timestamp) to a Google Sheet, and mark the source file as migrated. Never delete from source during migration — only after verification.

Step 5: Verify Integrity Before Cutover

After all files transfer, run a count comparison: source folder file count vs. destination count. For personnel records, do a name-by-name spot check on a 10% random sample. If counts match and spot check passes, proceed to cutover. If not, investigate before proceeding.

Step 6: Update Your Data Map and Notify Stakeholders

Update your data inventory/map to reflect the new storage location for every file type. Send a brief notification to all HR staff with the new folder paths and access instructions. Archive the migration log in a compliance folder — you may need it for an audit.

How to Know It Worked

Every file in your source inventory exists in the destination with correct permissions. The migration log in your Google Sheet has an entry for every file. A sample of restricted files shows only authorized users in the destination permissions list. Source system is archived, not deleted, for 30 days post-cutover.

Common Mistakes

The biggest mistake is migrating in bulk without separating restricted from unrestricted files — personnel records end up in a folder visible to the whole company. The second is deleting the source during migration rather than after verification, leaving no rollback option if the destination turns out to be misconfigured.

Frequently Asked Questions

Do I need to notify employees when migrating their personnel files?

Under GDPR and some state privacy laws, you do not need to notify employees of storage location changes for existing data, provided your privacy notice already discloses the categories of systems used. Check your notice and consult legal counsel if uncertain.

How long should I keep the migration log?

Retain migration logs for the same period as the underlying records — typically the length of employment plus 7 years for personnel records in the US. Match your jurisdiction’s requirements.

Can Make.com handle large file migrations (GB-scale)?

Make.com handles individual file transfers well but has module execution time limits. For very large files (500MB+), use direct API calls with chunked uploads rather than Make.com’s native file modules. For bulk volume, process overnight in scheduled batches.