I guess lots of teams have already taken the leap from legacy tool to slice machine, and I would be curious to get your feedback and advice on how to lead the charge here. In particular, how did you plan ahead for it, listed the various steps to go through and ensured there was no blind spot left behind.
Happy to take any feedback and thank you in advance for your help and advice
Hey @josselin.milon, iIn practice, teams that made the move found that it’s less about following a strict checklist and more about communication, consistency, and testing.
A good first step is for you and everyone else on your team is to get familiar with Slice Machine so you understand how the equivalent features work compared to the legacy builder. And from there, it’s really about planning the transition in a way that works for your team. There’s no single “right” way to do it, but moving to Slice Machine is the right move, it’s recommended, since the legacy builder won’t support newer features like the Tables field, Slice previews, and more.
We have an unofficial migration guide for moving over, but it’s a bit dated and may need some updates.