Gitoro's migrate-to-gitoro MCP prompt takes your agent through it in this order.
Create a workspace and an empty repository for each project.
Push branches and tags, or a full mirror. Git history stays intact.
Add the GitHub and Gitoro MCP servers to Claude Code, Codex or another MCP client.
The agent shows what it found and what can't be carried over, before migrating anything.
Issues move oldest first, with labels, comments and original dates where supported.
GitHub Actions become .gitoro-ci.yml. Once the pipeline passes, switch your remote.
Anything that can't be fully imported is reported, never silently dropped.
| On GitHub | On Gitoro |
|---|---|
| Commits, branches and tags | Pushed with Git; history is preserved exactly |
| Issues and comments | Recreated through the API or MCP, with status, metadata and links back to the source |
| Assignees | Assigned to people who already exist in your workspace; the rest are listed for review |
| Pull requests | Branches are pushed, then pull requests are created with links to the originals |
| GitHub Actions | Converted to .gitoro-ci.yml and validated with a pipeline |
| Releases and binary assets | Exported and uploaded separately |
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 $ENVIRONMENTGitoro pipelines use GitLab-compatible .gitoro-ci.yml, so the first pass from GitHub Actions is mostly mechanical.
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.