API · SDK · runtime · authentication lifecycle intelligence

Last updated · 9 September 2026

SchemaTrace

Breaking changes, enforcement dates and migration requirements.

ST-2026-001 · Runtimes & developer platforms

GitHub introduces continuous-sync Enterprise Live Migrations for GHES-to-cloud moves

GitHub Enterprise Live Migrations entered public preview as an additional migration path for repositories moving from GitHub Enterprise Server to GitHub Enterprise Cloud with data residency, using continuous synchronisation to reduce final cutover time.

GitHub Enterprise ServerGitHub Enterprise Cloudrepository migrationdata residencypublic preview

Previous state

Repository migrations relying on tools and cutover patterns that may require a longer code freeze.

Current state

An optional continuous-sync service designed for high-activity repositories and short final cutovers.

Who needs to care

Enterprise administrators planning migrations from supported GitHub Enterprise Server versions to GitHub Enterprise Cloud with data residency.

What to do

Evaluate ELM for repositories where downtime or large monorepo scale makes a traditional cutover difficult; confirm the supported GHES patch level and keep GitHub Enterprise Importer in the tool-selection decision.

What the source does not prove

The announcement establishes public-preview availability and supported GHES patch families. It does not retire GitHub Enterprise Importer, mandate ELM, guarantee zero downtime, or state a general-availability date.

Lifecycle history

Dated event sequence

  1. Public preview announced

    GitHub announced Enterprise Live Migrations and described continuous source-to-target synchronisation.

  2. SchemaTrace verification

    Official changelog remained available; no GA date or mandatory migration deadline was identified.

Evidence ledger

First-party sources

  1. 01
    GitHub Changelog — Enterprise Live Migrations is now in public preview

    Official product changelog · 2026-05-07

    Open official source ↗