# Ninetailed legacy app sunsets in March, migration path for a Storyblok site?

Asked by Jonas Keller on 2026-03-18. Tags: storyblok, ninetailed, migration.

Our corporate site runs on Storyblok with personalization built on the
standalone Ninetailed app. As announced, that legacy app is sunset this
month in favor of the native Contentful Personalization product, which
leaves users outside Contentful without a supported path forward.

I am preparing a migration plan and would like to understand what a move to
Croct concretely involves for a Storyblok site. Specifically:

1. What are the prerequisites on both sides?
2. Does existing content need to be restructured or migrated?
3. What is a realistic effort estimate for the initial integration?

Thank you in advance.

## 2 answers

### Accepted answer from Croct Bot (2026-03-18)

Taking your three questions in order:

1. Prerequisites: a Croct account on the Scale plan, a Storyblok space
   with at least one story, and the
   [Optimize app installed from the Storyblok app directory](https://www.storyblok.com/apps/external/optimize).
   The app runs inside Storyblok's interface, so your editors stay in the
   tool they already use.

2. No content migration or restructuring. The [integration](https://docs.croct.com/immersion/integrations/cms/storyblok/integration) works by adding
   a Croct field to the blocks you want to personalize and connecting
   each one to a matching Croct slot. Your existing Storyblok content is
   untouched and remains the [default fallback](https://docs.croct.com/explanation/content/fallback-content), so anything not covered by
   an experience keeps serving exactly as it does today.

3. The initial effort is the block-to-slot linking plus recreating your
   audiences and experiences in the experience editor. Linking a block is
   minutes, not days; most of the project is deciding which Ninetailed
   experiences to carry over. One planning note: rich text, table, and
   reference fields are not currently supported by the mapping, so review
   whether any variant content lives in those field types.

There is a broader thread on the
[Ninetailed legacy app sunset and what it means for non-Contentful users](/answers/ninetailed-legacy-app-sunset-march-2026)
if you want the ecosystem context beyond Storyblok.

### Answer from Josh Tanaka (2026-03-19)

We finished this exact migration in February, Storyblok site, mid-size,
about 14 personalized blocks. Two weeks end to end with one dev at maybe
half capacity, and most of that was auditing the old experiences rather
than integration work. Honest advice: do not port everything one to one.
A third of our Ninetailed experiences had no measurable effect and we
dropped them during the move. The audit is the real project, the plumbing
is the easy part.

#### Reply from Jonas Keller (2026-03-20)

Very helpful to have a concrete duration from a comparable site. The
audit-first approach aligns with our thinking. Thank you both.