# Migrating a large site

**URL:** <https://community.prismic.io/t/migrating-a-large-site/4865>\
**Category:** Developing with Prismic\
**Tags:** slice-machine\
**Created:** [April 7, 2021, 9:05pm UTC](https://community.prismic.io/t/migrating-a-large-site/4865 "2021-04-07T21:05:25Z")\
**Posts on this page:** 1\
**Showing post:** 33

<div class="post-metadata">

**Author:** ![yaay](https://avatars.discourse-cdn.com/v4/letter/y/958977/32.png) [@yaay](https://community.prismic.io/u/yaay)\
**Post date:** [February 9, 2023, 11:29am UTC](https://community.prismic.io/t/migrating-a-large-site/4865/33 "2023-02-09T11:29:06Z")

</div>

Hi, I asked this question in a similar thread, so I'd like to share it here, too.

> [@Migrating to Slice Machine](https://community.prismic.io/t/migrating-to-slice-machine/11130/5):
>
> Hi Pau and Prismic Team It has been 5 months since the last post in this thread. I run a design agencies's website as inhouse developer and would like to migrate from the legacy builder to slice machine. The reason i want to migrate is A. because the prismic documentation is all based on slice machine and B. because i love the shared slices aspect and that slices and custom types can be managed in the code. Can you make a statement/estimate when a migration guide from legacy to slice machine w…

---

_[View the full topic](https://community.prismic.io/t/migrating-a-large-site/4865)._