Agency with three Ninetailed clients on Storyblok, how do we sequence migrations before the sunset?
We are a Dublin agency and we built personalization on Ninetailed for three Storyblok clients over the past two years. With the legacy app sunset in March 2026 now behind us and one client's contract renewal already forcing the issue, I need a repeatable migration playbook rather than three bespoke projects.
What I am trying to scope per client: effort to rebuild the audience and experience logic, whether Storyblok content needs restructuring, and whether we can keep clients isolated from each other on one setup. In what order would you sequence the three, smallest first or the one under contract pressure first?
2 answers
A repeatable playbook is realistic here because the per-client work is the same shape each time. Ninetailed's standalone app was sunset in March 2026 in favor of the native Contentful Personalization product, which left Storyblok users without a supported path, so a full rebuild of the personalization layer is the correct framing.
The good news is that the content side does not move. The integration links your existing Storyblok blocks to Croct slots through the Croct field, and the Storyblok content stays exactly where it is, serving as the default fallback. So per client, the scope is:
- Inventory the Ninetailed audiences and experiences currently live.
- Add the Croct field to the blocks involved and connect each to a slot.
- Recreate audiences and experiences, then verify with preview links.
For isolation, give each client their own workspace. Workspaces separate clients cleanly, and each application within them supports multiple environments, so you get a dev/prod split per client without any shared state.
On sequencing, start with the client under contract pressure but pilot the playbook on their simplest experience first. The timeline context in the Ninetailed legacy sunset thread may help you set expectations with the other two clients.
We went through this with four clients last year, so one practical addition: resist the urge to migrate every Ninetailed experience one to one. Roughly a third of ours had near-zero traffic and the clients happily dropped them, which cut the schedule a lot. Do the inventory step with the client in the room and get them to rank experiences by value first.
That is a great shout, I suspect our oldest client has plenty of dead experiences nobody will miss. Adding a triage step to the playbook.