Importing migration data to GitHub Enterprise Server
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.
After every step of a migration you can review the state of the migration data. You'll be able to ensure records are being mapped or renamed properly, get the new urls for records after the import step, as well as list out any records that failed to migrate.
After your migration is applied to your target instance and you have reviewed the migration, you'll unlock the repositories and delete them off the source. Before deleting your source data we recommend waiting around two weeks to ensure that everything is functioning as expected.