We recommend you follow these best practices for running a trial migration, to help uncover problems that might be unique to your enterprise during and after the migration.
Review these high-level steps to plan and guide your migration trial run.
What repositories and data do you want to migrate? Are these supported by the beta version of Importer? Do you need to plan any manual migrations, such as for Git LFS resources?
To ensure you understand the known support limitations of the Importer, review "About GitHub Enterprise Importer."
We recommend you perform a trial run migration to test the result and help you understand how long your production migration might take. To start the trial run, you can follow the more detailed steps in "About GitHub Enterprise Importer" or "Migrating organizations from GitHub.com to GitHub Enterprise Cloud."
We recommend you note how long your trial run migration takes to complete to plan your production migration and any downtime.
While not required, we recommend halting work during your production migration. The Importer doesn't support delta migrations, so any changes that happen during the migration will not migrate. If you choose not to halt work during your production migration, you'll need to manually migrate these changes.
Review the results of the dry run migration to ensure their accuracy and completeness. You can also review the log file, which will share any errors.
After completing the trial run and validating the results, you can delete the migrated repository or organization. You can repeat this trial run process as many times as you want. In some cases, you may decide to just keep this migration as your production migration.
Using all you've learned from the trial run, plan your production migration and any custom steps you'll need. We recommend starting your production migration shortly after the trial run.