MDX components and custom snippets need an export plan.
Provider migration
Migrate from Mintlify to Sourced
Mintlify is a strong docs surface, but teams outgrow docs-only workflows when SDKs, examples, OpenAPI changes, and agent-readable docs need to move together. On this page: what to scan in your Mintlify 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
API reference examples can drift from OpenAPI.
AI/search features may not preserve the source-of-truth model your SDKs need.
Redirects and custom domains need a clean launch plan.
02Checks
Migration checklist
Inventory every MDX file with custom components — Mintlify's <ParamField>, <CodeGroup>, <Card> need replacement.
Export the docs.json navigation tree (or upgrade from legacy mint.json via Mintlify's CLI first) so Sourced can preserve it under docs previews.
Capture the AI search index settings — Sourced emits llms.txt plus generated operation pages from the OpenAPI source.
Map the API Playground configuration (Mintlify's interactive request widget) to the generated reference Sourced emits from OpenAPI.
Plan redirects for /api-reference/{slug} and any custom docs paths before the DNS swap.
03Details
Why Sourced fits
Sourced emits SDKs alongside docs, so the Mintlify-shaped 'docs only, SDKs handled elsewhere' problem goes away.
Custom MDX components become spec-driven examples that stay in sync with the OpenAPI source.
llms.txt is a first-class output tied to the generated OpenAPI reference.
Honest trade-off: if your team needs Mintlify's visual polish, AI Chat product, or non-API knowledge-base content, Mintlify stays the better pick. Sourced narrows to OpenAPI-first docs + SDKs.