Git Transfer

The Problem

You’ve been coding for years. You have repos on GitHub — personal, work, forks, experiments. You have repos on GitLab — CI pipelines, self-hosted projects, client work. Some exist on both platforms with diverging histories. Some are abandoned. Some are critical and you’re not sure which copy is the latest.

There’s no single view. No single backup. No clean inventory. Just sprawl.

Git Transfer exists to fix that. It’s a tool built for developers who want to take back control of their repository footprint — consolidate, mirror, back up, and actually know what they have and where it lives.

Features

Repository Merge

Consolidate repositories from GitHub and GitLab into a single, clean target account. Git Transfer scans both platforms, matches repos by name, and presents a unified view of everything you own. Duplicates — the same repo existing on both GitHub and GitLab — are detected automatically via name-matching and configurable mapping rules. You choose the target, review the plan, and execute. No manual cloning, no forgotten repos left behind.

Conflict Resolution

When the same repository exists on multiple platforms, the versions often diverge. Git Transfer detects which copy is newer, compares branch structures, and surfaces the differences in a clear mapping UI. You decide which version is canonical. No guessing, no silent overwrites — just an informed decision with full visibility before any merge happens.

One-Way Pull Mirror (GitLab)

Set up GitLab as a read-only pull mirror of your GitHub repositories. GitLab periodically pulls the latest state from GitHub — no push access required, no write risk to your primary repos. This is ideal for disaster recovery (if GitHub goes down, your code is already on GitLab), automated backups without custom scripting, and CI/CD pipelines that need read access to GitHub repos without storing credentials with write permissions.

BYO S3 Backup

Back up your repositories to your own S3-compatible storage bucket — AWS S3, MinIO, Backblaze B2, or any provider that speaks the S3 protocol. You own the backup destination. No vendor lock-in, no trusting a third party with your source code archives. Schedule backups, set retention policies, and sleep well knowing your code exists somewhere you fully control.

Run Logs

Every operation — scheduled or manual — is fully logged. See exactly what ran, when it ran, whether it succeeded or failed, and what changed. Run logs give you a complete audit trail: which repos were synced, which mirrors were refreshed, which backups completed. When something goes wrong, you don’t have to guess. When everything goes right, you have the receipts.

Who It’s For

• Solo developers with years of repos scattered across platforms who want a clean inventory and reliable backups.
• Small teams that use both GitHub and GitLab and need a single source of truth without manual syncing.
• DevOps engineers who want automated mirroring and backup without building and maintaining custom scripts.
• Consultants and freelancers who accumulate client repos across multiple accounts and need to consolidate when projects end.
• Anyone who’s ever thought “I should really back up my repos” but never got around to building the automation.

Current Status

Git Transfer is currently in active development. The core repository scanning, merge planning, and conflict detection features are being built and tested.

Want early access? We’re assembling a waitlist of developers who want to try Git Transfer before the public launch. Drop us a line at contact@mandraketech.in and we’ll keep you in the loop.