# Ideas for migrating a local repo

**URL:** <https://kopia.discourse.group/t/ideas-for-migrating-a-local-repo/3024>\
**Category:** General Topics\
**Created:** [June 20, 2024, 1:19pm UTC](https://kopia.discourse.group/t/ideas-for-migrating-a-local-repo/3024 "2024-06-20T13:19:54Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![bigsub](https://avatars.discourse-cdn.com/v4/letter/b/e480ec/32.png) [@bigsub](https://kopia.discourse.group/u/bigsub)\
**Post date:** [June 20, 2024, 1:19pm UTC](https://kopia.discourse.group/t/ideas-for-migrating-a-local-repo/3024/1 "2024-06-20T13:19:54Z")

</div>

I have a local repository where I save an entire workstation’s disk. This workstation is under a 4G network (so with limited GB for months).  
I’d like to migrate this local repo to a cubbit ds3 repo.

I can use a notebook connected sometime in office, where I’ve a flat fiber connection.  
What could be a convenient way to migrate the local repo, using the other connection?  
May I copy the entire kopia folder from workstation to the notebook and then sync from notebook to cubbit under flat adsl?

---

<div class="post-metadata">

**Author:** ![budy](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/budy/32/38_2.png) [@budy](https://kopia.discourse.group/u/budy)\
**Post date:** [June 20, 2024, 2:13pm UTC](https://kopia.discourse.group/t/ideas-for-migrating-a-local-repo/3024/2 "2024-06-20T14:13:35Z")

</div>

That’s what kopia repo sync-to is for… it will sync any kopia repo type to any other, local fs to remote s3 and vice versa. You need to create the S3 bucket and then have your local kopia sync the repo to the new S3 bucket.

---

<div class="post-metadata">

**Author:** ![bigsub](https://avatars.discourse-cdn.com/v4/letter/b/e480ec/32.png) [@bigsub](https://kopia.discourse.group/u/bigsub)\
**Post date:** [June 21, 2024, 7:32am UTC](https://kopia.discourse.group/t/ideas-for-migrating-a-local-repo/3024/3 "2024-06-21T07:32:31Z")

</div>

The sync-to behaviour was clear to me, but can I copy entire local repo folder to another place and then start a sync-to?

---

<div class="post-metadata">

**Author:** ![kapitainsky](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/kapitainsky/32/535_2.png) [@kapitainsky](https://kopia.discourse.group/u/kapitainsky)\
**Post date:** [June 21, 2024, 8:22am UTC](https://kopia.discourse.group/t/ideas-for-migrating-a-local-repo/3024/4 "2024-06-21T08:22:53Z")

</div>

I do not think so:

1. Source and destination might use different [sharding](https://kopia.io/docs/advanced/sharding/)
2. Not sure how kopia behaves with two repos with the same snapshots IDs etc. Maybe it will work - but why to push your luck when sync-to can do all job for you.

---

<div class="post-metadata">

**Author:** ![budy](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/budy/32/38_2.png) [@budy](https://kopia.discourse.group/u/budy)\
**Post date:** [June 21, 2024, 8:34am UTC](https://kopia.discourse.group/t/ideas-for-migrating-a-local-repo/3024/5 "2024-06-21T08:34:16Z")

</div>

You can alter the sharding any time you want - I did that when it became clear that my repo, which was then on a ZFS, needed some tweaking. However, there are other issues as well. E.g. on a S3 bucket, the repo files have a different naming scheme and repos sync-to will take care of that, of course. As long, as you’re staying on a “local filesystem” based setup, you should be able to copy your repo anywhere you want though.