<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Small Teams on Sovereign Shift</title>
    <link>https://sovereignshift.eu/tags/small-teams/</link>
    <description>Recent content in Small Teams on Sovereign Shift</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://sovereignshift.eu/tags/small-teams/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A Realistic Migration Path Away from Google Workspace for a 10-Person Team</title>
      <link>https://sovereignshift.eu/blog/realistic-migration-google-workspace-10-person-team/</link>
      <pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate>
      <guid>https://sovereignshift.eu/blog/realistic-migration-google-workspace-10-person-team/</guid>
      <description>&lt;p&gt;A 10-person team is the size where Google Workspace feels most natural and where leaving it feels most daunting. You are small enough that Google&amp;rsquo;s pricing is cheap (€12 to €14 per user per month for Business Standard). You are small enough that you do not have a dedicated IT person. And you are large enough that Google has become the invisible foundation of how your company operates.&lt;/p&gt;&#xA;&lt;p&gt;This post walks through a realistic migration path for a company of this size. Not a theoretical framework, but specific steps with specific tools, timelines, and costs. The company we are describing is composited from several real engagements, anonymised and simplified.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
