<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vendor Lock-In on Sovereign Shift</title>
    <link>https://sovereignshift.eu/tags/vendor-lock-in/</link>
    <description>Recent content in Vendor Lock-In on Sovereign Shift</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://sovereignshift.eu/tags/vendor-lock-in/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Anatomy of a Google Workspace Dependency: What Keeps You Locked to Google</title>
      <link>https://sovereignshift.eu/blog/google-workspace-dependency-audit/</link>
      <pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>
      <guid>https://sovereignshift.eu/blog/google-workspace-dependency-audit/</guid>
      <description>&lt;p&gt;Google Workspace is often seen as the lighter-weight alternative to Microsoft 365. Fewer products, simpler licensing, less enterprise complexity. Organisations that chose Google early tend to believe they could switch to something else in a few weeks if they needed to.&lt;/p&gt;&#xA;&lt;p&gt;That belief rarely survives contact with reality. Google Workspace creates dependencies that are structurally different from Microsoft&amp;rsquo;s, but just as deep. Some are harder to escape because they are less visible.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Anatomy of a Microsoft 365 Dependency: What Actually Locks You In</title>
      <link>https://sovereignshift.eu/blog/microsoft-365-dependency-anatomy/</link>
      <pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate>
      <guid>https://sovereignshift.eu/blog/microsoft-365-dependency-anatomy/</guid>
      <description>&lt;p&gt;When organisations talk about replacing Microsoft 365, the conversation usually starts with email and ends with &amp;ldquo;it&amp;rsquo;s too hard.&amp;rdquo; But the difficulty is rarely about email. The real lock-in lives in layers most teams never think about until they try to leave.&lt;/p&gt;&#xA;&lt;p&gt;This post maps the actual anatomy of a Microsoft 365 dependency: the layers that make migration hard, the ones that make it easy, and the ones nobody documents until it is too late.&lt;/p&gt;</description>
    </item>
    <item>
      <title>What Happens If Your US Cloud Provider Cuts Access Tomorrow: A 72-Hour Scenario for European Businesses</title>
      <link>https://sovereignshift.eu/blog/what-happens-if-us-cloud-cuts-access/</link>
      <pubDate>Wed, 08 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://sovereignshift.eu/blog/what-happens-if-us-cloud-cuts-access/</guid>
      <description>&lt;p&gt;This is not a prediction. It is a scenario exercise. We describe what would happen, hour by hour, if a typical 30-person European professional services firm lost access to its US cloud provider overnight. The firm runs on Microsoft 365 with Azure AD, Exchange Online, SharePoint, Teams, and OneDrive. It has no documented exit strategy.&lt;/p&gt;&#xA;&lt;p&gt;The purpose is not to cause alarm. It is to make the dependency concrete, because most organisations cannot articulate what would actually break until they walk through it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How SaaS Vendor Lock-in Actually Works: Seven Structural Layers That Keep European Organisations Stuck</title>
      <link>https://sovereignshift.eu/blog/building-resilient-organizations/</link>
      <pubDate>Fri, 06 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://sovereignshift.eu/blog/building-resilient-organizations/</guid>
      <description>&lt;p&gt;Most organisations think of vendor lock-in as a contractual problem: long-term agreements, steep renewal prices, early termination fees. That is the surface layer. The real lock-in operates through at least seven distinct structural mechanisms, most of which are invisible until someone tries to leave.&lt;/p&gt;&#xA;&lt;p&gt;Understanding these layers matters because each one requires a different approach to undo. Treating lock-in as a single problem leads to migration plans that fail at the first unexpected obstacle.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
