Migrating data to and from your enterprise

You can export user, organization, and repository data from GitHub Enterprise Server or GitHub.com, then import that data into your GitHub Enterprise Server instance.

About migrations→

A migration is the process of transferring data from a source location (either a GitHub.com organization or a GitHub Enterprise Server instance) to a target GitHub Enterprise Server instance. Migrations can be used to transfer your data when changing platforms or upgrading hardware on your instance.

Exporting migration data from your enterprise→

To change platforms or move from a trial instance to a production instance, you can export migration data from a GitHub Enterprise Server instance by preparing the instance, locking the repositories, and generating a migration archive.

Exporting migration data from GitHub.com→

You can export migration data from an organization on GitHub.com by using the API to select repositories to migrate, then generating a migration archive that you can import into a GitHub Enterprise Server instance.

Preparing to migrate data to your enterprise→

After generating a migration archive, you can import the data to your target GitHub Enterprise Server instance. You'll be able to review changes for potential conflicts before permanently applying the changes to your target instance.

Migrating data to your enterprise→

Importing data from third-party version control systems→

Using the git-import suite of tools, you can import from Subversion, Mercurial and Team Foundation Version Control to Git repositories on GitHub Enterprise Server.

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.

Still need help?

Ask the GitHub community

Contact support