Migrating to lfs.gg

This guide will help you migrate your Git LFS setup from your current provider (GitHub, GitLab, or Bitbucket) to lfs.gg. The process is straightforward and requires minimal downtime.

Prerequisites

Before starting the migration:

1. Ensure you have Git LFS installed (git lfs install)
2. Have a lfs.gg account and an active subscription
3. Have admin access to your repository

Getting Your lfs.gg Endpoint

1. Log in to your lfs.gg dashboard
2. Navigate to the "Repositories" section
3. Copy your unique LFS endpoint URL (it should look like: https://lfs.gg/<your-org>/<repo-name>)

Migration Steps

GitHub Migration

# View current LFS URL
git lfs env

# Update LFS URL to lfs.gg
git config lfs.url "https://lfs.gg/<your-org>/<repo-name>"

# Verify the change
git lfs env

GitLab Migration

# Remove existing GitLab LFS config
git config --unset lfs.url

# Set new lfs.gg endpoint
git config lfs.url "https://lfs.gg/<your-org>/<repo-name>"

# Verify the change
git lfs env

Bitbucket Migration

# Remove Bitbucket LFS config
git config --unset lfs.url

# Configure lfs.gg endpoint
git config lfs.url "https://lfs.gg/<your-org>/<repo-name>"

# Verify the change
git lfs env

Verifying the Migration

After updating your LFS URL:

1. Try pushing a new LFS file:

   # Track a new large file
   git lfs track "*.psd"
   
   # Add and commit the file
   git add your-file.psd
   git commit -m "Test lfs.gg migration"
   
   # Push to verify
   git push
   

2. Check your lfs.gg dashboard to confirm the file was uploaded successfully

Common Issues

• Authentication Errors: Ensure you're logged in to lfs.gg and have the correct permissions
• Push Failures: Verify your endpoint URL is correct and your subscription is active
• Missing Files: If files are missing after migration, contact our support

Need Help?

If you encounter any issues during migration, our support team is here to help. Contact us at support@lfs.gg or open a ticket in your dashboard.