Export your files or roll back a migration

Keep a complete independent copy and verify the destination before removing source data.

Export the required history

With LFSPush still configured as the source and a token that can read the repository, fetch all required Git refs and LFS objects. A Git bundle preserves Git history but does not include LFS file contents; back up both.

git fetch origin --tags
git lfs fetch --all origin
git bundle create repository.bundle --all

Include refs outside the normal fetch refspec if your project uses them. Preserve the downloaded .git/lfs/objects directory separately from the Git bundle, and test restoration in an isolated directory.

Copy to another LFS host

Configure the destination using a local lfs.url override, resolving any explicit push URL overrides. Authenticate with that host's credentials and push all LFS objects. This changes where file data is sent; it does not move the code repository.

git config --local lfs.url YOUR_DESTINATION_LFS_URL
git lfs push --all origin

Verify a fresh clone against the destination, including older revisions. Only then update shared .lfsconfig and CI configuration. Keep the source copy until everyone has confirmed the switch.

Roll back a migration

Pause new writes while you reconcile the copies.
Fetch any files written only to the new host and upload them to the original host before switching back.
Restore the original endpoint in local configuration, .lfsconfig, and CI. Resolve any lfs.pushurl or remote-specific overrides.
Use a clean clone to verify the restored endpoint and required historical revisions.
Recreate lock coordination separately and resume writes after the team confirms the rollback.

Open your workspace