Si vas a cambiar entre productos de GitHub, por ejemplo, de GitHub Enterprise Server a GitHub Enterprise Cloud, o desde otra plataforma de Hosting de código, como Bitbucket Server o GitLab, a GitHub, querrás traer tu trabajo contigo: tu código, el historial del código y todas las conversaciones y colaboraciones anteriores.
GitHub provides a variety of different tools to support these migrations. Different tools support different migration pathways and provide different levels of migration fidelity. To determine the best tool for your migration, understand what you can migrate, and learn how to make your migration successful, see Planeamiento de la migración a GitHub and Migrations to GHE.com.
The steps you will take to migrate to GitHub Enterprise Cloud include:
- Define the origin (source) for your migration. Your destination is GitHub Enterprise Cloud.
- Understand what data you will migrate, and build a basic inventory.
- Evaluate the size of your migration data, and recognize if you need to first move any repositories to Git.
- Decide on your migration type, based on your organization's needs and the tools available to you.
- Choose if you will perform the migration yourself (a "self-serve migration"), or if you will work with GitHub's Expert Services team or a GitHub Partner (an "expert-led migration").
In a later stage of setting up your trial, when you're ready to create your organization and teams, you will take additional steps to finish your migration, including:
- Design your organization structure for the migration to GitHub Enterprise Cloud.
- Plan a test of your migration, including performing a dry run migration of all your repositories.
- Establish your pre-migration and post-migration steps, and create a migration plan.
- Prepare your organization and schedule for the migration.
- Perform the migration, and execute any post-migration tasks.
About enterprise migrations to GitHub Actions
To migrate your enterprise to GitHub Actions from an existing system, you can plan the migration, complete the migration, and retire existing systems. To learn how to migrate your workflows to GitHub Actions, see Migrar tu empresa a GitHub Actions.
If you're planning to switch to GitHub Actions, we do not recommend doing so at the same time that you migrate your repositories. Instead, wait until a later date, and perform your CI/CD migration as a separate step. This makes the migration process more manageable. When you're ready to migrate, see Migrar a GitHub Actions.
Next steps
Next, learn about Securing your enterprise with Managed Users and Securing enterprise resources with single sign-on.