How to Migrate Google Gemini Chat History to Microsoft Copilot

The "Knowledge Base" Method

Switching from Google Workspace to M365? Learn how to migrate your Gemini AI context and chat history to Microsoft Copilot using the Document Grounding method for seamless continuity.

As organisations migrate from Google Workspace to Microsoft 365, one of the biggest hurdles isn't just moving emails -- it's moving AI intelligence.

If your team has spent months "training" Gemini on project specifics, coding standards, or brand voices, losing that chat history feels like losing a teammate. While there is no direct "Sync" button between Google and Microsoft, there is a better way: The Knowledge Base Migration.

Instead of moving messy chat logs, we are going to turn Gemini's best work into Microsoft Graph-ready assets.

Why "Grounding" Beats "Copy-Pasting"

Simply copying and pasting old chats into Copilot is tedious and loses context. By following the Knowledge Base method, you save your Gemini history as structured documents in OneDrive or SharePoint.

Because Microsoft Copilot is "grounded" in your M365 data, it can "read" those migrated Gemini files and answer questions about them immediately.

Step 1: Use Gemini to Summarise Itself

Don't export raw data; export intelligence. Ask Gemini to summarise its own long-running threads.

The Prompt to use in Gemini:

"I am migrating to Microsoft Copilot. Please summarise our entire conversation regarding [Project Name] into a structured 'Project Intelligence Brief.' Include key decisions made, technical specifications discussed, and the preferred tone of voice we established. Format this as a clean document."

Step 2: Export to Google Docs (and then to Word)

Gemini has a built-in "Export to Docs" button at the bottom of its responses.

1. Click the Share icon > Export to Docs.
2. Once the Doc is open, go to File > Download > Microsoft Word (.docx).

Step 3: Seed the Microsoft 365 Environment

Now, move those files into the heart of the new ecosystem.

• For Personal AI: Upload the Word files to the user's new OneDrive.
• For Team AI: Upload the files to a specific SharePoint library or a Teams Channel.

Step 4: Reference the History in Copilot

Once the files are uploaded (allow 5--10 minutes for indexing), your users can "talk" to their old Gemini history.

The Prompt to use in Copilot:

"Looking at the 'Project Intelligence Brief' in my OneDrive, what were the main risks we identified for the Q3 launch?"

Pro Tip: Migrating "Gems" to Copilot "Notebook"

If your users have created Gems (custom AI personas) in Gemini, they should move the "System Instructions" manually.

1. Open the Gemini Gem and copy the instructions.
2. Open Microsoft Copilot and navigate to the Notebook tab.
3. Paste the instructions there. The Notebook allows for up to 18,000 characters, making it perfect for maintaining a specific "AI personality" during the move.

Summary Checklist for IT Admins

• Identify "Power Users" with high Gemini usage.
• Provide a template for "Project Intelligence Briefs."
• Ensure OneDrive sync is active so Copilot can "see" the migrated files.
• Train users on the / command in Copilot to reference specific migrated files.

Conclusion

Migrating from Google Gemini to Microsoft Copilot doesn't have to mean starting from scratch. By turning your AI history into a structured Knowledge Base, you ensure that your team's collective intelligence survives the move.

Need help with your M365 Migration? Reach out and talk to our technical team today for a seamless transition.

Matt Wilkinson | Founder & CEO