A file migration is not the same thing as a finished document handoff. The file may arrive in its new workspace, but the version that a customer, colleague or regulator receives still needs a human check. That matters most when a Word, Excel or PowerPoint document is opened in a different editor and then exported as a PDF.
What Google announced
On 13 October 2026, Google announced new Microsoft 365 migration and interoperability updates for Google Workspace. Its Data import tool can now bring SharePoint Online document libraries, OneDrive user files, Teams channels and chat messages into Drive and Chat; Google says the file-import capability is generally available. The announcement also says Workspace users can already view and edit Office files in Docs, Sheets and Slides without first converting the file.
Some features are not available yet. Google describes preservation of Microsoft Information Protection (MIP) sensitivity labels, handling of MIP-protected files and client-side re-encryption as planned for general availability by the end of the year. Office Editing Mode in Gmail is described as coming later this quarter. Those timelines matter: do not assume an encrypted or labelled source file will receive the same treatment in a migration started today.
A practical PDF handoff checklist
1. Choose a representative set before the bulk move. Include a document with tracked layout, a spreadsheet with a chart, a presentation, an image-heavy file and a file carrying any sensitive classification. Keep the originals unchanged. 2. Record what the source contains. Note the page count, filenames, links, embedded images, comments, form controls, signatures, security labels and sharing restrictions. This is your comparison point—not a promise that every item will transfer. 3. Open the migrated version in its new workflow. If the file will be edited in Workspace, make a small test edit in a copy. If it will be sent as a PDF, export the exact copy you would share rather than reviewing only the editable source. 4. Review the exported PDF page by page. Look for changed fonts, shifted tables, clipped charts, altered page breaks, missing comments or unexpected blank pages. Use PDF Reader to zoom into dense sections and compare the first, a complex middle and final page. 5. Handle the PDF as a separate distribution copy. Use Organize PDF if you need to reorder, rotate or remove pages, then reopen the downloaded result. Do not use a page-organising step on a signed or protected document unless the owner confirms that the change is allowed.
What this does—and does not—prove
A successful import proves that the destination service accepted a file; it does not prove that every layout detail, protection setting, accessibility property or digital signature is preserved. Likewise, a visual PDF check can catch obvious handoff mistakes, but it is not a legal compliance audit or a substitute for your organisation’s migration, retention and data-protection procedures.
Teams should also check access separately. Migrated folder structure, file ownership, external sharing and sensitive-data labels are administrative controls, not visual features of a PDF. Test the permissions with an appropriate non-admin account before inviting users to work from the new library.
For the final document-review stage, FileStation can provide a simple browser workspace to inspect a PDF and organise its page sequence. It does not migrate Microsoft 365 data, transfer security labels or certify fidelity; keep the original and get approval from the document owner for any material change.
Primary source: Google Workspace Blog: Experience easier migration and collaboration between Google Workspace and Microsoft 365, 13 October 2026.