# Migrate GitLab projects to Gitea with repository check via API
This workflow automates the transfer of projects from GitLab to Gitea, preventing duplication by verifying repository existence. Ideal for organizations and teams migrating to a self-hosted Git server.
## Who it´s for
- Git server administrators migrating from GitLab to Gitea
- DevOps engineers managing multiple repositories
- Teams moving to self-hosted Git hosting
- IT specialists automating infrastructure tasks
## What the automation does
- Manually triggered via execute_workflow_trigger
- Fetches a list of projects from GitLab using REST API
- Checks whether each repository already exists in Gitea
- If not present, initiates the migration process
- Stops execution with error message on failure (e.g., 404)
- Supports pagination and partial failure handling
## What´s included
- Ready-to-use n8n workflow
- Trigger and conditional logic setup
- Integrations with GitLab and Gitea via HTTP API
- Basic text instructions for launch and adaptation
## Requirements for setup
- Access to an n8n instance
- API tokens with read access (GitLab) and write access (Gitea)
- URL of internal Gitea server or access to GitLab.com
- Permissions to create repositories in the target Gitea system
## Benefits and outcomes
- Prevents repository duplication during migration
- Accelerates bulk project transfers without manual oversight
- Allows safe resumption after interruptions
- Centralizes migration in a single manageable workflow
- Reduces risk of errors across dozens of projects
- Ensures repeatability and auditability of actions
## Important: template only
Important: you are purchasing a ready-made automation workflow template only. Rollout into your infrastructure, connecting specific accounts and services, 1:1 setup help, custom adjustments for non-standard stacks and any consulting support are provided as a separate paid service at an individual rate. To discuss custom work or 1:1 help, contact via chat
No feedback yet