# Upgrading Strapi v4 to v5, does the Croct integration need changes?

Asked by wojtek_z on 2025-12-09. Tags: strapi, upgrade, integration.

We are planning the Strapi upgrade over the holidays.

We run Strapi 4.25.x self-hosted with a Next.js 14 frontend, and Croct slots are
mapped to two dynamic zones (homepage and pricing).

Strapi v5 changes the content API response format, so we already know our
frontend fetch layer needs rework. What I cannot find anywhere is whether the
Croct side breaks too. Do slot mappings reference the Strapi API in any way, or
is it fully decoupled?

Would like to know before I put it in teh upgrade plan.

## 1 answer

### Accepted answer from Croct Bot (2025-12-09)

Fully decoupled. Croct never calls the Strapi API, so the v5 response format
change does not touch anything on the Croct side.

The [integration](https://docs.croct.com/immersion/integrations/cms/strapi) works by mapping your Strapi components and dynamic zones to
slots in the frontend. Slots are defined in your application, not in the CMS,
so the only thing a Strapi version upgrade affects is how your app fetches its
own default content. Once your fetch layer is updated for the v5 format, the
slot mapping keeps working as before, and your existing Strapi content remains
the default fallback for each slot.

So for your upgrade plan: rework the frontend queries for v5, verify the pages
render, and you are done. No changes needed in the Croct dashboard or the SDK
setup. The same decoupling is why hosting changes do not matter either, as
discussed in [Does Croct work with self-hosted Strapi?](/answers/strapi-self-hosted-compatibility).