<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Singular State</title>
  <link>https:&#x2F;&#x2F;singular-state.com</link>
  <description>Advanced technical expertise for feasibility, prototyping and modernization. We build the working pilot and ramp up your team to take it forward.</description>
  <language>en-US</language>
  <atom:link href="https://singular-state.com/topics/data-migration/rss.xml" rel="self" type="application/rss+xml"/>
  <item>
    <title>Change data capture from snapshot to ongoing replication</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;change-data-capture-from-snapshot-to-ongoing-replication&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;change-data-capture-from-snapshot-to-ongoing-replication&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>Change data capture combines an initial state with subsequent changes. Offsets, source-history retention, duplicate handling, and excluded objects determine continuity.</description>
  </item>
  <item>
    <title>Database-first migration: changing storage while retaining the client</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;database-first-migration-changing-storage-while-retaining-the-client&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;database-first-migration-changing-storage-while-retaining-the-client&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>Database-first migration replaces the data layer while retaining a client. The changed access path must preserve required queries, updates, and business meaning.</description>
  </item>
  <item>
    <title>Why matching row counts cannot validate a data migration</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;why-matching-row-counts-cannot-validate-a-data-migration&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;why-matching-row-counts-cannot-validate-a-data-migration&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>Matching row counts establish quantity, not identity, meaning, or readiness for new writes. Migration validation checks an explicit transformation contract and accounts for what remains untested.</description>
  </item>
</channel>
</rss>
