Import a Repository from Another Host

Bring an existing Git repository onto UnityFreak by URL — full history included.

TL;DR — The Short Version

Git history migrates in full. Issues, pull/merge requests, and branch rules do not migrate — they stay on your old host.
Generate a read-only token on your source host, then paste the repository's clone URL and that token into Import Repository.
Your credentials are used once, to clone, and are never stored.
LFS objects back-fill automatically after the import completes — track progress in the repository's Settings → LFS tab.

1. What Migrates

Importing a repository mirror-clones its full Git history — every commit, branch, and tag — directly from the source URL you provide. That history is exactly what you get: a complete, working clone you can push and pull from immediately.

What does not come across is anything that lives outside the Git history itself: issues, pull or merge requests, and branch protection rules all stay on your old host. If you rely on any of those, plan to recreate the ones you still need on UnityFreak — there is no automated migration for them today.

2. Generate a Read-Only Token

Even for a public repository, generating a token avoids the source host's anonymous rate limits during the clone. For a private repository, it's required. A token scoped to read-only access is all the import needs.

From GitHub

GitHub → Settings → Developer settings → Personal access tokens. A token scoped to read the repository is enough.

From GitLab

GitLab → User Settings → Access Tokens, with the read_repository scope.

From Bitbucket

Bitbucket → Personal settings → App passwords, with Repositories: Read permission.

3. Run the Import

From Repositories → Import Repository, fill in:

Repository URL — the source's clone URL (e.g. https://host/owner/repo.git).
Repository Name — pre-filled from the URL; edit it if you want a different name on UnityFreak.
Owner and Visibility — your personal account or an organization you administer, and whether the imported repository is Private, Internal, or Public.

If the source is private, check "This is a private source (requires credentials)" and enter the username and the token you generated above as the password. Those credentials are used once, to perform the clone, and are never stored — only the repository's URL (with credentials stripped) is kept on the import record.

4. After the Import

Point your local clone at the new remote and keep working exactly as before:

git remote set-url origin https://unityfreak.com/{owner}/{repo}.git

Push and pull continue working exactly as they did against the old host — nothing else about your local workflow changes.

The import only carries over Git history synchronously — the initial clone contains LFS pointer files, not the LFS bytes themselves. A backfill job kicks off automatically right after the import completes to fetch those objects from the original source. You can watch its status — not started, pending, running, completed, or failed — from the repository's Settings → LFS tab, which also lets an admin manually retry the fetch with a "Fetch LFS objects" button if it ever needs a nudge.