Migrate from GitHub to European Git Hosting

Move your repositories to Gitoro with Git, then let your AI agent carry over the work around the code: issues, pull requests, comments, labels and CI configuration.

Workspace dashboard with repositories, usage and activity charts

A guided migration, step by step

Gitoro's migrate-to-gitoro MCP prompt takes your agent through it in this order.

  1. 1

    Create your workspace

    Create a workspace and an empty repository for each project.

  2. 2

    Push your code

    Push branches and tags, or a full mirror. Git history stays intact.

  3. 3

    Connect your agent

    Add the GitHub and Gitoro MCP servers to Claude Code, Codex or another MCP client.

  4. 4

    Review the inventory

    The agent shows what it found and what can't be carried over, before migrating anything.

  5. 5

    Migrate the records

    Issues move oldest first, with labels, comments and original dates where supported.

  6. 6

    Convert CI and switch

    GitHub Actions become .gitoro-ci.yml. Once the pipeline passes, switch your remote.

What moves, and how

Anything that can't be fully imported is reported, never silently dropped.

On GitHubOn Gitoro
Commits, branches and tagsPushed with Git; history is preserved exactly
Issues and commentsRecreated through the API or MCP, with status, metadata and links back to the source
AssigneesAssigned to people who already exist in your workspace; the rest are listed for review
Pull requestsBranches are pushed, then pull requests are created with links to the originals
GitHub ActionsConverted to .gitoro-ci.yml and validated with a pipeline
Releases and binary assetsExported and uploaded separately
.gitoro-ci.yml
stages: [build, test, deploy]

test:
  stage: test
  image: node:20
  script:
    - npm ci
    - npm test
  rules:
    - if: '$CI_PIPELINE_SOURCE == "merge_request_event"'

deploy:
  stage: deploy
  needs: [test]
  environment: production
  when: manual
  script:
    - ./deploy.sh $ENVIRONMENT
CI/CD

From GitHub Actions to .gitoro-ci.yml

Gitoro pipelines use GitLab-compatible .gitoro-ci.yml, so the first pass from GitHub Actions is mostly mechanical.

runs-on becomes image, or a self-hosted runner
steps become script, if becomes rules
actions/cache becomes cache
Environment reviewers become required approvals

Move to Europe, out of reach of the CLOUD Act

The US CLOUD Act can compel US-based companies to hand over data under their control, even when it's stored in Europe. Gitoro is Danish, with EU-only hosting for your code, pipelines, and AI.

GDPR by design

Export or delete your data anytime.

EU-only infrastructure

Your code and data stay in Europe.

European AI

AI features run on models hosted in Europe.

Bring your repositories to Europe.

Create a free workspace, push your first repository and let your agent migrate the rest.