Studio/project structure needs an export inventory.
Provider migration
Migrate from Stoplight to Sourced
Stoplight migrations often start as docs cleanup, but API teams also need to preserve examples, linting rules, mocks, and SDK release behavior. On this page: what to scan in your Stoplight setup, the migration checks Sourced runs, and a preview of the generated SDK and docs you would get.
Unlimited previews. No credit card required.
01Checks
What to check
Mock server behavior may hide schema drift.
Docs URLs and anchors need redirects.
Generated SDKs need compatibility checks outside the docs tool.
02Checks
Migration checklist
Export Stoplight Studio projects to raw OpenAPI + Markdown — Sourced does not consume the Studio project format directly.
Audit any Prism mock-server usage — Sourced does not host mocks; you keep Prism in CI or move to a hosted mock provider separately.
Capture every Spectral rule (Stoplight's linter) you extend; Sourced's spec scanner covers most overlapping rules but custom rules may need a Spectral pass alongside.
List every Hub URL and anchor (/docs/{project}/{branch}/...) — redirect coverage is the largest URL-mapping job.
For published SDKs, run the Sourced compatibility report against the previously-generated Stoplight output before any package swap.
03Details
Why Sourced fits
Sourced emits SDKs + docs from one OpenAPI workflow; Stoplight handles docs + mocks but SDKs are typically a third tool.
Compatibility report makes the SDK-side cutover safer than 'regenerate and pray'.
Per-API-project pricing replaces Stoplight's per-user / per-project pricing.
Honest trade-off: if mock servers are core to your dev workflow, Sourced does not currently replace Prism — keep Prism alongside.