# Finished moving off Ninetailed after the sunset, sanity-checking our new setup

Asked by mara_leon on 2026-08-21. Tags: contentful, ninetailed, migration.

ok we are finally live and I can breathe again. we ran Contentful with
Ninetailed for personalization and had to move once the legacy standalone
app got sunset earlier this year. we kept Contentful as the content source
and wired Croct in on the frontend instead of touching the CMS.

now that it is actually serving traffic I want a gut check from anyone who
made the same move. does this shape look right to you, Contentful staying as
the source of content and the personalization layer sitting on top of it? I
keep expecting to have missed something.

## 2 answers

### Accepted answer from steffi_r (2026-08-23)

That is exactly the shape it is meant to be. Croct works alongside the
existing CMS rather than replacing it, so Contentful staying as your
content source is the intended setup, not a compromise you made.

The part worth confirming is the fallback: your existing Contentful content
serves as the default whenever no experience matches a slot. So a visitor
who fits none of your audiences still sees the base entry, and any slot you
have not wired yet just keeps rendering Contentful as before. If that is how
yours behaves you are done, nothing missing.

For context on why the move was forced in the first place, there is a good
rundown in [the thread on the Ninetailed legacy app sunset](/answers/ninetailed-legacy-app-sunset-march-2026).

### Answer from devraj (2026-08-23)

We migrated the same way, Contentful kept as the content source and Croct
added on the frontend. Nothing to add to steffi's answer on the mechanics,
just confirming the pattern is common and holds up. Ours has been in
production a few months now with no surprises.

#### Reply from mara_leon (2026-08-24)

thanks both, that settles it. honestly the thing that surprised me was
the flicker just disappeared once content resolved server-side, we had
quietly accepted that swap as normal and now it is gone.