Complete Guide to Git Repository Migration: Seamless Transfer from Old to New Server

Core Concepts of Git Repository Migration

Git repository migration is a common requirement in development operations, particularly during server decommissioning or infrastructure upgrades. The core objective is to preserve complete version history, branch structure, and metadata integrity. Git's distributed architecture offers multiple solutions for this, each with specific use cases and advantages.

Detailed Standard Migration Method

Based on the best answer from the Q&A data, the standard migration process involves three key steps. First, use git remote add new_repo_name new_repo_url to add the new remote repository address. This command establishes a connection point to the new server in the local repository's configuration.

Next, execute git push new_repo_name master to push the main branch content to the new location. In practice, if the repository contains multiple important branches, it is advisable to use git push new_repo_name --all to ensure complete migration of all branches.

After migration, use git remote rm origin to remove the old remote repository configuration. At this point, you can edit the .git/config file to rename new_repo_name to origin, or maintain the current configuration based on team collaboration needs.

Mirror Clone Alternative

For scenarios requiring complete replication of the entire repository, git clone --mirror offers a more comprehensive solution. This command creates an exact mirror of a bare repository, including all references, tags, and configuration information. The specific operation flow is:

git clone --mirror <Old Repository URL>
cd <Clone Directory>
git remote set-url origin <New Repository URL>
git push --mirror origin

This method is particularly suitable for large repositories or migration scenarios requiring absolute consistency, but attention should be paid to network transmission time and storage space requirements.

Branch and Tag Handling Strategy

During migration, the integrity of branches and tags is crucial. Use git branch -a to view all remote branches and git tag to list all tags. For the standard migration method, manually ensure that all important branches are pushed to the new repository.

The method mentioned in the reference article involves checking out branches one by one using git checkout branch-name, then fetching all tags with git fetch --tags. Although this method involves more steps, it provides better control granularity.

Practical Operation Considerations

Before migration, it is recommended to perform a complete repository backup; using git bundle to create a snapshot is a good option. Ensure stable network connectivity during migration, especially for large repositories, as interruptions may require starting over.

When verifying migration results, not only check the integrity of the commit history but also confirm the correct transfer of ancillary information such as branch protection rules and Webhook configurations. In team collaboration scenarios, promptly notify all developers to update the remote repository address.

Solution Comparison and Selection Advice

The standard migration method is suitable for most daily scenarios, with simple operations and controllable risks. The mirror clone method is better for overall repository relocation or creating exact copies. When choosing a solution, consider factors such as repository size, network conditions, and team workflow.

Regardless of the method chosen, post-migration verification is essential. Compare commit histories with git log --oneline and check remote branches with git branch -r to ensure migration completeness and accuracy.