# New tool: dvc-to-lakefs (zero-copy import from DVC to lakeFS)

**URL:** <https://discuss.dvc.org/t/new-tool-dvc-to-lakefs-zero-copy-import-from-dvc-to-lakefs/2702>\
**Category:** Announcements\
**Created:** [June 30, 2026, 12:21pm UTC](https://discuss.dvc.org/t/new-tool-dvc-to-lakefs-zero-copy-import-from-dvc-to-lakefs/2702 "2026-06-30T12:21:46Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jenydefig](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@jenydefig](https://discuss.dvc.org/u/jenydefig)\
**Post date:** [June 30, 2026, 12:21pm UTC](https://discuss.dvc.org/t/new-tool-dvc-to-lakefs-zero-copy-import-from-dvc-to-lakefs/2702/1 "2026-06-30T12:21:46Z")

</div>

We just released **dvc-to-lakefs** , a tool that imports DVC-tracked data into lakeFS with a zero-copy, one-command migration, no re-uploading, just the objects you already pushed, now with branches, commits, and merges at scale.

DVC’s still the right tool for the single-project, fits-on-disk workflow. This is for when you’ve outgrown that, bigger datasets, more people and pipelines on the same data, CI/CD gates, and want to move up without re-shuffling your data.

We’d love to hear how it goes!

Blog post: [https://dvc.org/blog/migrate-dvc-to-lakefs](https://dvc.org/blog/migrate-dvc-to-lakefs)

Repo + docs: [GitHub - treeverse/dvc-to-lakefs: Zero-copy import of DVC-tracked data into lakeFS · GitHub](https://github.com/treeverse/dvc-to-lakefs)
