Migrated data for live migrations from GitHub Enterprise Server to GHE.com

Data that is migrated

ELM migrates almost all repository-level data. Organization-level resources, such as teams, projects, and organizations settings and webhooks, are excluded from the migration and must be configured manually on the target.

The only organization-level action supported by ELM is the creation of a target organization account if this does not already exist.

Repository settings and configuration

Resource	Notes
Repository metadata and settings	Visibility, description, default branch, and enabled features
Repository webhooks	Webhook configurations for the repository
Repository topics	Tags for categorizing the repository
Repository PR settings	Pull request merge and review settings
Actions settings	Repository-level GitHub Actions configuration, including allowed actions and permissions
Autolinks	Custom autolink references
Branch protections	Branch protection rules are partially migrated, with the limitations described below
Pages	GitHub Pages configuration

Warning

Branch protection migration is partially supported. ELM preserves whether actor restrictions are enabled for dismissing pull request reviews and pushing to protected branches, but it does not preserve the permitted users, teams, or apps. A push restriction can therefore be recreated on the destination with an empty allowlist. It also does not migrate pull request bypass actors, force-push actors, status check app bindings, matching-branch creation restrictions, merge queue settings, deployment requirements, or branch locking. Review and update migrated branch protection rules before allowing users to work in the destination repository.

Git data, LFS, and wikis

Resource	Notes
Git repository (refs, objects, history)	Includes all refs, objects, and commit history. The repository is kept up to date on the destination throughout the migration.
LFS objects	Git Large File Storage objects. Requires LFS to be enabled on the source GitHub Enterprise Server instance.
Wiki	The wiki Git repository

Issues, comments, and reactions

Resource	Notes
Issues	Includes state, assignees, and body
Issue comments	All comments on issues
Issue reactions	Reactions on issues
Issue comment reactions	Reactions on issue comments
Issue labels	Label associations on issues
Issue events	Timeline events (assigned, labeled, closed, etc.)
Close issue references	Cross-references that close issues (e.g. "fixes #123")

Pull requests, reviews, and threads

Resource	Notes
Pull requests	Includes state, reviewers, body, and draft status
PR reviews	Submitted reviews, including approved, changes-requested, and commented states
PR review comments	Inline code review comments
PR review threads	Threaded discussions, including resolved and unresolved state
PR comment reactions	Reactions on pull request review comments
PR labels	Label associations on pull requests

Labels, milestones, releases, and CI

Resource	Notes
Labels	Label definitions, including name, color, and description
Milestones	Milestone definitions and state
Releases	Release metadata, including tag, name, body, and prerelease or draft status
Release reactions	Reactions on releases
Commit comments	Comments on individual commits
Commit status checks	CI/CD status checks on commits
Check runs	Check run results
Check suites	Check suite groupings
Team repository permissions	Team-to-repository permission associations

Binary assets and file attachments

Resource	Notes
Release assets	Binary assets attached to releases, up to 2 GB per asset
Attachments	Image and video file attachments embedded in issue and pull request bodies
Repository files (non-media attachments)	Non-media file attachments, such as PDFs and text files, associated with issues and pull requests

Users and mannequins

Resource	Notes
Mannequins	Every GitHub Enterprise Server user referenced in migrated data is represented as a mannequin: a placeholder identity with no organization membership or repository access. After your migration is complete, you can reclaim mannequins by associating them with real user accounts.

Data that is not migrated

Repository data

Data	Notes
Repository defaults	N/A
Repository rulesets	Repository rulesets are not migrated. Branch protection rules are partially migrated.
Pull requests from forks	N/A
Pending pull request reviews	Only submitted reviews are migrated.

Organization data

Organization-level data such as the following is not migrated:

Settings
Teams
Projects
Webhooks

Events included in live updates

After the initial backfill completes, the exporter's event listener monitors webhooks on GitHub Enterprise Server to capture ongoing changes and forward them to the migration service on the target enterprise.

The following tables document which resource types support live updates and which webhook actions are handled.

Resource type	Supported events	Unsupported events
Repository	`edited`	`archived`, `deleted`, `privatized`, `publicized`, `renamed`, `transferred`, `unarchived`
Issues	`assigned`, `closed`, `edited`, `labeled`, `opened`, `reopened`, `unassigned`, `unlabeled`, `milestoned`, `demilestoned`	`deleted`, `locked`, `pinned`, `transferred`, `unlocked`, `unpinned`
Issue comment	`created`, `edited`	`deleted`
Pull request	`assigned`, `closed`, `converted_to_draft`, `edited`, `labeled`, `opened`, `ready_for_review`, `reopened`, `unassigned`, `unlabeled`, `milestoned`, `demilestoned`	`auto_merge_disabled`, `auto_merge_enabled`, `dequeued`, `enqueued`, `locked`, `review_request_removed`, `review_requested`, `synchronize`, `unlocked`
Pull request review	`edited`, `submitted`	`dismissed`
Pull request review comment	`edited`

Migrated data for live migrations from GitHub Enterprise Server to GHE.com

In this article