# Moving from self-hosted Strapi to Strapi Cloud, anything to redo on the Croct side?

Asked by brunoc on 2025-05-21. Tags: strapi, strapi-cloud, migration.

We are done maintaining our own Strapi instance (backups, upgrades, the usual)
and moving to Strapi Cloud next sprint.

My migration checklist so far:

- [ ] export/import content to Strapi Cloud
- [ ] point frontend STRAPI_URL at the new instance
- [ ] update webhooks
- [ ] Croct: ???

Frontend URL and domain stay exactly the same, only the CMS host changes. What
changes on the Croct side and what does not? I want the checklist complete before
we schedule the cutover.

## 1 answer

### Answer from Lucas Ferreira (2025-05-22)

Your Croct line item is essentially "nothing". The SDK runs in your app, not in
the CMS, so it works the same for self-hosted Strapi and Strapi Cloud. The
integration maps your components and dynamic zones to slots in the frontend,
and Croct never calls the Strapi API, so the CMS host is invisible to it.

Nothing changes in the Croct dashboard, nothing in the SDK config, nothing in
the slot mappings.

What to verify anyway, since you like checklists:

- [ ] after cutover, load the mapped pages and confirm the Strapi Cloud content
      renders as the default in each slot
- [ ] open the dashboard Integration page and confirm it still shows received
      traffic, which tells you the SDK is running fine post-move

That second check is quick and gives you a concrete signal instead of assuming.

#### Reply from brunoc (2025-05-22)

Checklist updated with both verification items. Exactly the kind of answer
I needed, obrigado.