Skip to main content
Private preview. fremforge is in private preview — invited customers only. Content is still subject to change. Request access →

Migration guides

Step-by-step migration paths from the three most common source platforms. Each guide covers repository and history migration, secrets and environment variables, CI workflow adaptation, SSH key re-registration, and third-party integration reconnection. Read the pre-migration checklist first to surface oversized repos, heavy LFS pools, Marketplace action dependencies, and pipeline complexity before you start.

Pre-migration checklist

Read-only scanner for GitHub, GitLab, or Azure DevOps. Run before you start to find blockers and warnings up front.

From GitHub

.com, GHEC, or GHES. Native importer + mirror-clone path, Actions adaptation, top-20 Marketplace pre-launch review.

From GitLab

.com, self-managed, or Dedicated. Subgroup flattening, GitLab CI → Forgejo Actions conversion patterns.

From Azure DevOps

Repos + Pipelines + Boards. Classic-pipeline-to-YAML gate, Service Connections to OIDC federation, Work Items to Issues.

Where to start

Run the pre-migration checklist against your current tenant. The script is read-only and surfaces conditions that cause mid-migration surprises before you commit any time. If you need help interpreting the output, email support@frem.sh.

What the migration always preserves

  • Git history, branches, and tags, exactly.
  • Issues with metadata (labels, milestones, assignees where mapped by email).
  • Pull / merge requests with comments and merge state.
  • Releases including binary attachments.
  • Wiki content.

What the migration does not preserve automatically

  • CI workflow run history, historical runs stay on the source platform; new runs start fresh on fremforge.
  • Secret values, must be re-entered (rotation strongly recommended at migration time).
  • Third-party integrations configured at the source, webhooks, Slack/Teams notifications, deploy hooks all need reconnecting.
  • Source-specific advisory/security databases (GitHub Dependabot alerts, GitLab Security Dashboard), fremforge runs its own dependency scanning and produces its own findings independently.
  • Source-specific Pages deployments and custom domains, see the per-platform guide.

Top-20 Marketplace compatibility

The compatibility matrix for the most-used GitHub Marketplace actions ships at /marketplace-compat/ at launch. The page is being verified action-by-action against real fremforge runners; the four migration guides cite specific actions inline where they matter, so you can migrate without waiting for the full matrix.

Get help

If you are partway through a migration and stuck, email support@frem.sh with subject line starting MIGRATION - and the platform name. Early-adopter customers have direct access to the fremforge build team for migration assistance at no additional charge.