Knowledge-base content needs to be separated from API reference content.
Provider migration
Migrate from DeveloperHub to Sourced
DeveloperHub is a broad documentation platform. Sourced is focused on API docs and SDKs for teams that want the developer experience to come from OpenAPI. On this page: what to scan in your DeveloperHub 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
Custom docs routes and redirects need inventory.
OpenAPI examples and schemas need cleanup before generation.
SDK publishing is a new workflow to add.
02Checks
Migration checklist
Export public docs content and identify which pages are API-specific.
Validate the OpenAPI source that should generate the new reference.
Generate Sourced docs and SDK previews and review high-value endpoints.
Map DeveloperHub routes to Sourced docs or retained content pages.
Plan DNS and redirects only after the preview and release report are accepted.
03Details
Why Sourced fits
Sourced is narrower and more API-native than a general docs CMS.
SDK previews are first-class outputs.
Reports show what needs review before launch.
Honest trade-off: if you need a full knowledge-base CMS, keep DeveloperHub or another docs CMS for non-API content.