<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Microsoft 365 on Danno Projects</title><link>https://www.dannoprojects.com/posts/m365/</link><description>Recent content in Microsoft 365 on Danno Projects</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 24 Oct 2025 09:00:00 -0700</lastBuildDate><atom:link href="https://www.dannoprojects.com/posts/m365/index.xml" rel="self" type="application/rss+xml"/><item><title>Moving 70 Mailboxes from Google Workspace to Exchange Online Without Losing a Message</title><link>https://www.dannoprojects.com/posts/m365/google-workspace-to-exo/</link><pubDate>Fri, 24 Oct 2025 09:00:00 -0700</pubDate><guid>https://www.dannoprojects.com/posts/m365/google-workspace-to-exo/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;Email is the one system nobody notices until it stops working. When we moved a 70-person company from Google Workspace to Exchange Online, the goal wasn&amp;rsquo;t just &amp;ldquo;move the mail.&amp;rdquo; It was to move the mail &lt;strong&gt;without anyone missing a message, a calendar invite, or an automated workflow&lt;/strong&gt; that quietly depended on a Gmail inbox.&lt;/p&gt;
&lt;p&gt;This post is the checklist I wish I&amp;rsquo;d had at the start. It&amp;rsquo;s written for small IT teams (often a team of one) doing a cutover without a migration partner.&lt;/p&gt;</description></item></channel></rss>