Schema Analysis
Paste your Strapi v3 content-type schema JSON to get a full migration report.
No schema handy? Click to try it with a sample v3 project.
Finding Your Strapi v3 Schema
Your v3 content-type schemas live in your Strapi project's api/ directory:
your-strapi-v3-project/
└── api/
├── article/
│ └── models/article.settings.json ← this file
├── category/
│ └── models/category.settings.json
└── ...
Open each .settings.json file — it contains the attributes and kind fields StrapiShift needs.
Multiple content types? Paste them as a JSON object keyed by name:
{"article": {"kind": "collectionType", "attributes": {...}},
"category": {"kind": "collectionType", "attributes": {...}}}
Or use the CLI: strapishift analyze ./api/ to scan the entire directory.
Finding Your Strapi v5 Schema
In Strapi v5, content-type schemas are in src/api/:
your-strapi-v5-project/
└── src/api/
├── article/
│ └── content-types/
│ └── article/schema.json ← this file
├── category/
│ └── content-types/
│ └── category/schema.json
└── ...
You need v5 schemas for parity verification — comparing what you have in v5 against the original v3 source.
Go to the Verify page to compare v3 and v5 schemas side by side.
Don't have a v5 instance yet? Start with analysis here — StrapiShift tells you everything that needs to change before you create one.
Connect to a running Strapi v3 instance to automatically pull all content-type schemas. Requires admin panel credentials (not an API token).
Security: Credentials are sent directly from your browser to your Strapi instance. Nothing is stored or sent to StrapiShift servers. This page runs entirely client-side.