logo
search
Google Workspace Migration

How to Fix Google Drive Migration Scan Failures Due to Shortcuts

Maira MehtabMaira Mehtab Sep 22, 2026 868 views

Question details

The user needs to successfully complete a Google Drive migration scan, but the process is failing because the target drive contains shortcut files.

Product
Microsoft 365 Migration Tool
Device & OS
not provided
Scenario
Migrating files from Google Workspace (Google Drive) to Microsoft 365.
Observed behavior
The migration scan fails for large drives containing shortcuts, whereas drives without shortcut files scan successfully. There is no visible option to ignore these shortcuts.
Before you start

Before proceeding, ensure you have administrative access to the Microsoft 365 admin center and have collected the specific scan logs and details of the affected Google Drive.

Solution 1Recommended

Raise a Service Request in Microsoft 365 Admin Center

Since the migration tool does not offer a native setting to skip shortcut errors, escalating the issue to Microsoft support is required for the development team to investigate.

Currently, the standard migration tool lacks a built-in feature to automatically bypass or process Google Drive shortcuts. Reaching out directly to the Microsoft support team allows them to investigate your tenant's specific backend errors and provide a custom fix or workaround.

1
Log into Admin Center

Sign in to the Microsoft 365 admin center using an account with Global Administrator or Support Administrator privileges.

2
Navigate to Support

Click on 'Support' in the left-hand navigation menu, then select 'Help & support'.

3
Describe the Issue

Type a brief description of the issue, specifically mentioning that your Google Drive migration scan fails due to shortcut files.

4
Submit the Request

Follow the prompts to open a new service request. Be sure to include the affected drive details and attach the migration scan logs for the development team to review.

Contact Your Administrator: If you do not have administrative privileges for your organization, please share these instructions with your IT department or Microsoft 365 administrator.
Free Microsoft Office alternative

Experience a Seamless Workflow with WPS Office

While waiting for Microsoft support to resolve complex migration tool issues, you can continue your daily work without interruption. WPS Office is a highly compatible, lightweight, and completely free alternative that handles all your document needs effortlessly.

  1. 1. Download and Install: Visit the official WPS website to download the free installation package for your operating system.
  2. 2. Launch the Application: Open WPS Office and sign in to access cloud features and additional productivity tools.
  3. 3. Open Your Documents: Drag and drop your existing Microsoft Office or Google Workspace files directly into WPS Office to view and edit them with perfect formatting retention.
Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx).Lightweight design ensures fast installation and smooth operation, even on older devices.Familiar tabbed user interface minimizes the learning curve, keeping your team productive.Built-in cloud integration allows for easy file management across multiple platforms.
microsoft office alternative - wps office

Frequently Asked Questions

Why do Google Drive shortcuts cause the Microsoft 365 migration scan to fail?

Shortcuts in Google Drive act as pointers to other files or folders rather than physical files. The Microsoft 365 migration tool sometimes struggles to resolve these link paths during the scanning phase, leading to a failure for that specific drive.

Is there a setting in the migration tool to ignore shortcuts?

Currently, there is no built-in checkbox or setting within the standard Microsoft 365 migration tool interface to automatically skip or ignore Google Drive shortcut files.

Can I manually remove shortcuts before running the migration scan?

Yes. As a temporary workaround, you can manually locate and delete the shortcut files, or move them to a different folder outside the migration scope, before attempting the migration scan again.