I currently manage two corporate repos, one has 6000+ pages with about 300 slices the other has 1000+ pages with around 150 slices. All are legacy with slices block, and none of the slices are named like they need to be to use slice machine. Is there any migration steps we can do with this, or do …

Hi Rob Kristie, Thanks for reaching out. My name's Badr, I am working in the User Research team at Prismic. As per your question to migrate your assets to Slice Machine, you can migrate everything except the shared slices, more precisely the shared slices will be available but you will not be able…

Hi Badr, I'm interested in the same thing. But I have a question as to why it's not recommended for in-production projects yet? All the documentation is updated for SM. Migrating to SM would make managing the over 150 slices we have easier, lets room for mistakes and for creating duplicate slice…

Hi Badr Looking at the documentation for Nuxt, it seems it all is based around Slice Machine now and the small amount of documentation that used to exist is gone. So, it feels like we are being asked to move to Slice Machine, which is why I am asking this.

[image] badr.filali: As per your question to migrate your assets to Slice Machine, you can migrate everything except the shared slices. More precisely, the shared slices will be available, but you will not be able to migrate them in the sense of fetching them to your local project. This is also…

Hi Fares, How can you add slice machine to your existing Prismic Repo that is in a production environment? It seems like you'd have to make major code updates locally. Is this the only way to "migrate"? Also, if you have to recreate all the slices anything that is in a production environment wou…

Hi @rkristie and @jason.pike First, thanks for your enthusiasm and willingness to migrate large sites to the SliceMachine approach! Sorry if we haven't brought enough visibility on the progress of SliceMachine and specifically on the migration path. I've gathered updates internally and here is the…

Hi Nathaneal, Is it possible to request a status update on those two points, production readiness, and migration path? In essence, is the migration tool currently being worked on, and is there a prospective release date? I'm new to the community and not exactly sure where else to seek out updates…

Hi Dan, sorry for the delay. Sure let me check with the team.

Sorry for the delay on this one. I'm checking in with the team to get input and update that request.

@dan.parker , a quick update on the migration path: the team is planing to define a strategy for the transition path and the specs for migrating existing Legacy repositories to Slice Machine, but we don't expect to have any official guide yet. In the meantime, we're keen to connect with the communit…

Migrating a large site

Developing with Prismic

Topic		Replies	Views
Migrating to Slice Machine Developing with Prismic typescript , nextjs , slice-machine	22	2854	October 13, 2023
Slice machine clarity Developing with Prismic	3	905	January 16, 2023
Slice Machine migration plan preparation Developing with Prismic nuxtjs , slice-machine	7	131	January 24, 2026
Migrating Legacy Slices Developing with Prismic nextjs , slice-machine	3	148	November 21, 2024
Best practices for upgrading legacy Nuxt3 to slice machine Developing with Prismic typescript , nuxtjs	1	277	January 5, 2024

Migrating a large site

Related topics