Migrate to Starport
Promptless runs the migration to Starport for you. It stands up the site and moves your content and configuration onto it. Your team reviews the result, cuts over to the new site when ready, and runs the site’s configuration after onboarding. For the fundamentals of docs-as-code and platform choice, see Understand docs-as-code and Choose a platform.
Use cases
Section titled “Use cases”| Your situation | What the migration gives you |
|---|---|
| Your docs live on a hosted platform that keeps content in its own editor. | Your content moves into a Git repository you own, as Markdown and MDX source files. |
| You want to change platforms without breaking existing links. | Promptless sets up redirects from changed URLs, so existing links keep working. |
| Your team can’t pause writing for a migration project. | Promptless does the migration work while your team keeps writing, then you review the result. |
| You need to know you can leave later. | Your content and site run on open-source Astro Starlight in your own repository and hosting account. |
What Promptless handles
Section titled “What Promptless handles”Promptless handles the migration end to end:
-
Promptless bootstraps your site on the Starport template.
-
Promptless migrates your content, components, screenshots, and configuration onto it.
-
Promptless sets up redirects for any URLs that change. For the fundamentals, see Preserve URLs and redirects.
-
Promptless optimizes your docs for AI agents, so the llms.txt files, docs MCP server, and page actions work at launch.
-
Promptless readies the site for launch, so your team can cut over when you are ready.
What Promptless needs from you
Section titled “What Promptless needs from you”The managed migration needs these from your team:
- Access to your existing documentation content.
- A Git repository for the content. If you don’t have one, Promptless sets one up with you.
- Control of your domain’s DNS. You point the domain at the new site when you cut over. Promptless leaves your DNS records to you.
What you keep
Section titled “What you keep”Your content stays yours. It lives in a Git repository your team owns, as Markdown and MDX source files. You keep the full history and the access control, and you can edit and publish directly at any time. Promptless sets up the build, deploy, and content-maintenance tooling around that repository.
If you stop using Promptless, you keep the content and the site. The site runs on the open-source Astro Starlight framework from your repository and hosting account, so it keeps building and serving on its own.
After onboarding
Section titled “After onboarding”Once you are live, the site’s configuration is yours. You tune it through its configuration files. See Configure your Starport site for the options you own. Promptless keeps your content current as your product changes. See Keep your Starport docs current for how that works.
Start a migration
Section titled “Start a migration”Every annual Promptless plan includes migration to Starport at no cost. To start a migration, talk to your Promptless contact. If you’re evaluating Promptless, contact the Promptless team at help@gopromptless.ai.