Migrate from Strapi
Editions: Open Source · Free Cloud · Pro
Strapi content-types map cleanly to Apito models, but lifecycle differs: Apito stages schema drafts and requires Console publish.
Mapping
| Strapi | Apito |
|---|---|
| Content-Types | Models |
| Components / dynamic zones | Nested / list fields (reshape as needed) |
| Relations | Apito relations |
| Roles & permissions | RBAC |
| Media library | Files |
| GraphQL plugin | Built-in secured GraphQL |
| REST | REST shim where Engine supports it |
Suggested path
- List content-types → create Apito models (UI, MCP, or Blueprint).
- Publish schema; verify in API Explorer.
- Write a migrator: Strapi REST/GraphQL → Apito Admin SDK creates (preserve slugs/ids if you need redirects).
- Re-point frontends from Strapi GraphQL to Apito; prefer JS Admin SDK over hand-rolled queries when possible.
- Rebuild deploy hooks — Webhooks.
CMS Blueprint
For newspaper/blog shapes, start from newspaper-cms (Chikly-derived) instead of an empty project.