# Gitea-to-Gitea migration with issues, labels, etc

**URL:** <https://forum.gitea.com/t/gitea-to-gitea-migration-with-issues-labels-etc/1411>\
**Category:** Install/Maintain/Configure\
**Created:** [August 21, 2019, 9:24pm UTC](https://forum.gitea.com/t/gitea-to-gitea-migration-with-issues-labels-etc/1411 "2019-08-21T21:24:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![HenrikBengtsson](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/henrikbengtsson/32/108_2.png) [@HenrikBengtsson](https://forum.gitea.com/u/HenrikBengtsson)\
**Post date:** [August 21, 2019, 9:24pm UTC](https://forum.gitea.com/t/gitea-to-gitea-migration-with-issues-labels-etc/1411/1 "2019-08-21T21:24:45Z")

</div>

Hi, is there a known approach, similar to GitHub-to-Gitea migration, that does Gitea-to-Gitea migration where **issues, pull requests, labels, etc. are also migrated**? I have a repository living on one Gitea 1.9.0 server that I want to migrate to another Gitea 1.9.0 server.

---

<div class="post-metadata">

**Author:** ![anon74399538](https://avatars.discourse-cdn.com/v4/letter/a/c6cbf5/32.png) [@anon74399538](https://forum.gitea.com/u/anon74399538)\
**Post date:** [August 26, 2019, 12:49pm UTC](https://forum.gitea.com/t/gitea-to-gitea-migration-with-issues-labels-etc/1411/2 "2019-08-26T12:49:34Z")

</div>

Using Dump is all I know. But if you’re looking for some kind of replication using Kubernetes please check out my post and let me know your thoughts on the approach. 🙏🏻

> **[REVISTA HACKERS by habd.as](https://habd.as)**
>
> Últimas noticias sobre hackers y todas las novedades

And here’s Gitea containerized in prep:

> [@High Tea: Gitea with Traefik](https://forum.gitea.com/t/high-tea-gitea-with-traefik/393):
>
> Traefik - A reverse proxy / load balancer that’s easy, dynamic, automatic, fast, full-featured, open source, production proven, provides metrics, and integrates with every major cluster technologies… High Tea - Self-hosted git server using [Docker](https://www.docker.com/), [Gitea](https://gitea.io/), [Postgres](https://www.postgresql.org) and [Traefik](https://traefik.io) for: Simple, consistent and deterministic way to create Gitea. Extremely flexible, powerful and self-configuring solution. Automatic, production-ready SSL certificates that auto-renew. [View the source](https://git.habd.as/comfusion/high-tea)

---

<div class="post-metadata">

**Author:** ![lunny](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/lunny/32/4701_2.png) [@lunny](https://forum.gitea.com/u/lunny)\
**Post date:** [August 30, 2019, 2:13pm UTC](https://forum.gitea.com/t/gitea-to-gitea-migration-with-issues-labels-etc/1411/3 "2019-08-30T14:13:58Z")

</div>

Interesting request. I think it will not be too difficult since we have done it with github, next is Gogs / Gitlab and Gitea .
