Moving from Contentstack to Storyblok, planning personalization from day one
We are migrating from Contentstack to Storyblok next quarter, and our CMO wants personalization included in the project scope rather than added later.
Since we are remodeling all our content anyway, I would rather sequence this correctly now. Two things I want to confirm before we lock the migration plan:
- Should we model our Storyblok blocks with Croct in mind from the start, or is that something that can safely come after the content migration?
- What are the actual prerequisites on both sides before the integration works?
Any constraints on field types would also be good to know now, while the block schemas are still on the whiteboard.
1 answer
There is one constraint worth knowing while your block schemas are still being designed, so let me start with the prerequisites and get to it.
Prerequisites
- A Croct account on the Scale plan.
- A Storyblok space with at least one story.
- The Optimize app installed from the Storyblok app directory.
Sequencing
You can safely complete the content migration first. The integration works by linking your existing Storyblok blocks to Croct slots after the fact, and your Storyblok content stays in place as the default fallback. Nothing about the migration itself needs to change for Croct.
The one modeling decision to make now
Rich text, table, and reference fields are not currently supported for personalization. So while you are designing block schemas, keep the copy you expect to vary (headlines, CTAs, short descriptions) in supported field types like text fields, rather than embedding it inside a rich text body. That is the only decision that is much cheaper to make now than to refactor later.
Everything else, linking blocks to slots and building experiences, happens after the migration lands and does not require touching the content again.