Microsoft 365 to Google Workspace Migration: Fix the Links Before Users Find Them

A migration project can look finished on the cutover dashboard and still be broken in the places employees notice first. Someone opens a spreadsheet, clicks a link to a shared folder, and lands back in the old tenant. A presentation points to a colleague’s document that no longer exists. The file itself moved successfully; the working relationship between files did not.

That is a common blind spot in a Microsoft 365 to Google Workspace migration. Mailboxes and documents are only part of the job. The references people use to navigate that information need to move too.

Why link integrity deserves its own migration workstream

Enterprise documents are rarely isolated files. A workbook may link to a policy document, a presentation may reference a shared project folder, and a procedure may contain links to forms, diagrams or supporting spreadsheets. Those connections quietly become part of the organisation’s operating knowledge.

When content moves between tenants, the original URLs can remain embedded in the migrated files. If the source environment is retired, users encounter dead links, access errors or confusing routes back to a system they are no longer meant to use. The help desk then inherits a long tail of “the document is there, but the link doesn’t work” tickets.

What CloudM Migrate 5.2 adds

CloudM Migrate’s 5.2 release, dated 30 September 2026, introduced Link Remediation as a separate migration item type. It scans migrated documents for references to source content and rewrites supported links so they point to the corresponding destination copy. The release notes cover Google-to-Google and Microsoft 365-to-Google migrations.

For Google Docs, Sheets and Slides, supported links are rewritten in place through Google APIs while preserving formatting. For Office files such as DOCX, XLSX and PPTX, CloudM says it updates links inside the original file format. Its coverage includes hyperlinks, plain-text URLs, field codes, formulas, comments, PowerPoint notes and layouts, smart chips, footnotes and table cells. SharePoint and OneDrive sharing links are resolved through Microsoft Graph.

There is an important workflow detail: Link Remediation runs as its own pass after the documents have been migrated. It cannot be combined with other item types in the same migration row. CloudM uses the migration record to map source items to destination copies, then reports how many links were scanned, mapped, replaced or already correct. A document-mapping CSV is also produced for review.

Build the source-to-destination map before cutover

Link remediation works best when the migration team has a reliable picture of the source and target environments. Before moving content, inventory the tenants, shared drives, SharePoint sites, OneDrive accounts, file owners and collaboration groups in scope.

Pay particular attention to documents that are widely reused: operating procedures, finance templates, project workbooks, HR forms, engineering specifications and sales collateral. These are the files most likely to contain links that matter to people beyond the original author.

  • Identify high-value libraries and documents with many internal references.
  • Confirm that destination users, groups and shared locations are ready before files arrive.
  • Record which source locations are expected to map to which destination locations.
  • Agree how external sharing links and guest access will be handled after migration.
  • Keep a sample set of documents for post-migration validation.

Rewriting a link is not the same as granting access

A repaired URL can point to the right destination and still lead to an access-denied page. Link remediation should therefore sit alongside a separate permissions and ownership review. Confirm that the right people have access to the destination file, that shared-drive membership is appropriate and that external sharing follows the organisation’s policy.

This is also a good time to retire obsolete links deliberately. Not every source reference should be redirected. Some may point to superseded content, temporary project folders or documents that should no longer be shared. Migration owners should decide which references are worth preserving rather than treating every old URL as automatically valid.

A practical sequence for a cleaner cutover

  1. Assess: inventory content, users, sharing patterns and the document types in scope.
  2. Prepare: create destination users and groups, establish the target folder structure and validate permissions.
  3. Migrate: move the agreed mail, files and collaboration data, then review the migration reports.
  4. Remediate: run the dedicated Link Remediation pass over the migrated batch.
  5. Validate: open representative documents, test links to important destinations and review the mapping CSV and HTML reports.
  6. Cut over: communicate the new locations, keep the source available for the agreed transition period and monitor user-reported issues.

Check the prerequisites and version path

CloudM’s release notes state that CloudM Migrate 5.2 requires version 4.7.6 or later as the starting point for an upgrade. They also note that teams planning to use Link Remediation must add three scopes to the service account and enable three APIs in the Google Cloud project before the first run. Existing migrations are unaffected if the feature is not used, but the prerequisites should be checked during project preparation rather than discovered on cutover day.

Google’s 13 October 2026 Workspace announcement also matters to migration planning: its expanded data-import tooling covers Microsoft 365 mail, calendars, SharePoint Online libraries, OneDrive files and Teams content, with mappings for items such as Outlook rules, calendar permissions and shared mailboxes. Google described the expanded import capability for files as generally available. That makes it even more important to test the less visible details—links, access and collaboration context—rather than measuring success only by the volume of data copied.

Measure the migration users actually experience

Do not stop at a successful item count. Track the proportion of important links that were scanned and mapped, the number rewritten, the number already correct and the exceptions that need manual attention. Test a sample of high-value documents with the people who use them every week. Then watch the service desk queue for recurring problems around missing files, stale URLs and permissions.

A well-run cloud migration should leave employees with working documents, not merely documents that happen to exist in a new tenant. Treating link remediation as a planned workstream helps protect the connections between files, reduce post-cutover support noise and give users a more convincing day-one experience.

About CloudM
CloudM is an award-winning SaaS company whose humble beginnings in Manchester have grown into a global business in just a few short years.

Our team of tech-driven innovators have designed a SaaS data management platform for you to get the most from your digital workspace. Whether it’s Microsoft 365, Google Workspace or other SaaS applications, CloudM drives your business through a simple, easy-to-use interface, helping you to work smarter, not harder.

By automating time-consuming tasks like IT admin, onboarding & offboarding, archiving and migrations, the CloudM platform takes care of the day-to-day, allowing you to focus on the big picture.

With over 35,000 customers including the likes of Spotify, Netflix and Uber, our all-in-one platform is putting office life on auto-pilot, saving you time, stress and money.

About Version 2 Limited
Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.

Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.