Why File Licenses Are Needed for Google Sites Migration
Understanding license requirements for migrating embedded Google Drive documents within Google Sites.
The Challenge with Embedded Documents
Overview
When migrating Google Sites to SharePoint, embedded Google Drive documents present a unique challenge. Google Sites stores only the file ID of embedded documents without any information about who owns them. This creates a significant technical hurdle that requires file migration licenses to overcome.
The Problem
Core Issue
Google Sites stores only the file ID of Google Drive documents embedded in the site without any information about the owner.
This means that when Cloudiway encounters an embedded document, it only has a file ID— a unique identifier that doesn't reveal which user's Drive contains the file. Without knowing the owner, Cloudiway cannot:
- Access the document for migration
- Impersonate the correct user to retrieve the file
- Map permissions correctly in the target environment
Cloudiway's Solution
To migrate embedded Drive documents, Cloudiway must build a cartography of all files per user. This involves:
Audit All User Drives
Cloudiway audits every user's Google Drive to collect file IDs and ownership information.
Build File ID Database
Store file IDs mapped to their respective owners to create a lookup table.
Impersonate Owner
When migrating a site, look up each embedded file's owner and impersonate them to access the document.
Migrate Document
Transfer the document to SharePoint with appropriate permissions.
Licensing Requirements
Two licensing options exist depending on your migration scope:
Option 1: Migrating Google Drives
If you're already migrating Google Drives with Cloudiway:
- • Purchase only Google Sites migration licenses
- • No additional CAL needed
- • Drive audit is included
Option 2: Not Migrating Drives
If you're NOT migrating Google Drives:
- • Purchase a Client Access License (CAL)
- • CAL enables file migration access
- • Required to audit file owners
License Purpose
Why Every User Needs Coverage
A common question is whether you can purchase licenses for only some users. Unfortunately, this isn't possible due to how Google Sites stores embedded files.
The Challenge
A file ID does not permit determination of which Drive the document is stored in. Since any user might have embedded their Drive documents in Google Sites, you must audit all users—requiring licenses for every single one.
Without comprehensive user coverage:
- You cannot audit file owners
- Embedded drives cannot be migrated
- Sites may have broken or missing content after migration