MDX components and custom snippets need an export plan.
Provider migration
Migrate from Mintlify to Bloom
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.
Checks
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.
Checks
Migration checklist
Export source docs, OpenAPI files, theme settings, redirects, and custom domains.
Decide which content remains hand-authored and which references are generated.
Generate a preview before touching production DNS.
Run SDK and docs checks before publishing packages or indexing new pages.
Details
Why Bloom fits
Bloom is OpenAPI-first.
The migration report shows the SDK, docs, and launch work before anything goes live.
SDKs, docs preview, sitemap, and llms.txt live in the same workflow.
The dashboard shows what is generated, ready, and waiting on review.
Related pages