A Microsoft 365 to Google Workspace migration usually has a solid plan for email, calendars, contacts and OneDrive files. OneNote tends to show up late, often when an employee asks, a week before cutover, where their notebooks are going.
It matters more than it looks. OneNote is where people keep meeting notes, client history, project decisions and how-to knowledge that exists nowhere else. Losing it, or turning it into an unsearchable pile of PDFs, is a real cost even if nobody puts it in the migration budget.
What a good OneNote migration has to preserve
Whatever approach you choose, judge it against these:
- Structure: notebooks, section groups, sections and pages should arrive as a folder hierarchy people recognize.
- Editability: notes should become documents people can keep working in, not frozen archives.
- Content: formatting, lists, tables and images should survive the move.
- Security: employee data shouldn't be stored by a third party, and access should be scoped and temporary.
- Visibility: IT should be able to see who has migrated and who hasn't, without seeing anyone's notes.
Your options
Ask employees to move their notes by hand
The default when nobody plans for OneNote. In practice, most people won't do it, the ones who do lose formatting and images, and it's impossible to track. It's fine for a handful of people with small notebooks.
Export notebooks to PDF
Easy to explain and it keeps how notes look, but the result is a read-only archive: one large file per notebook, not editable, and hard to search. It works for compliance retention, not for people who need to keep using their notes.
A self-service migration tool, sponsored by IT
Each employee runs the migration for their own account, so nobody needs admin access to everyone's notes, and IT approves the tool once and tracks progress centrally. This is how NotePorter for organizations works.
How NotePorter for organizations works
- We enable your domain. Anyone signing in with a work account on your domain gets unlimited migrations, with no payment step.
- Employees start at enterprise.noteporter.com. They sign in with their Microsoft work account, then the Google account their notes should go to.
- Notes land in Google Drive. Each employee gets a NotePorter folder organized as notebook, section group and section, with every page as an editable Google Doc.
- IT follows progress on a dashboard. Admins see each employee's status, pages copied and completion date, and can export it as a CSV.
A rollout plan that works
- Approve the app. Many tenants block users from consenting to third-party apps. Grant consent for NotePorter once in the Microsoft Entra admin center (Enterprise applications). On the Google side, allow it under Security > API controls if you restrict third-party apps.
- Run a pilot. Start with five to ten people, ideally including your heaviest OneNote users, and check the results in Drive with them.
- Roll out team by team. Microsoft limits how quickly data can be read from OneNote, per user and per organization. Large, image-heavy notebooks can take several hours, and staggering teams keeps everyone's migration moving.
- Track and follow up. Use the dashboard to see who hasn't started, and nudge them before cutover. Migrations run in the background, so employees don't need to keep anything open.
- Keep OneNote until you're done. Nothing in OneNote is changed or deleted, so leave licenses active until everyone has migrated.
Security and privacy
These are the questions your security review will ask, so here are the answers up front:
- Sign-in: standard OAuth with Microsoft and Google. NotePorter never sees passwords.
- Permissions: read-only access to OneNote, and access in Google Drive limited to the files NotePorter creates.
- Data handling: notes are copied from Microsoft to Google and not kept; page images are held only briefly in transit. Access tokens are encrypted and deleted when each migration finishes.
- Admin visibility: the dashboard shows progress only, never note content or page titles.
Current limitations
Text formatting, lists, tables and images are migrated, and files attached inside pages (and audio recordings) are copied to Drive next to each page with a link in the doc, up to 100 MB per file. Handwriting and drawings (ink) aren't supported yet. Complex free-form page layouts are converted into a regular document flow, so side-by-side content may end up stacked. If your teams rely heavily on any of these, include them in your pilot so you know what to expect.
Plan your OneNote migration
We can enable your domain for a trial so your pilot group can test with their real notebooks.
Talk to usFrequently asked questions
Does IT need access to every employee's notebooks?
No. Each employee signs in and runs their own migration, so nobody needs admin access to everyone's notes. IT approves the app once and follows progress on the dashboard.
Can employees send notes to a personal Google account?
Employees choose the Google account during sign-in. If notes should stay in your Workspace, ask employees to sign in with their work Google account. The admin dashboard shows which Google account each employee used, so you can check.
How long does a company-wide migration take?
Each employee's migration runs in parallel. Small notebooks finish in minutes, large image-heavy ones can take several hours because of Microsoft's rate limits. Staggering teams over a few days works well for larger organizations.
What happens to OneNote afterwards?
Nothing. NotePorter only reads from OneNote, so the original notebooks stay intact until you decommission Microsoft 365.