If you have docs somewhere else, you can move them. The shortest path: get your existing content out as Markdown, then paste it into a new page in the Dokly editor — Markdown converts to blocks automatically.
This page covers the common sources. If yours isn't listed, the general approach at the bottom applies.
The shape of every migration#
Get your content out as Markdown
Most platforms have an export option. Aim for one Markdown file per page.
Create a new page in Dokly
In your project's page tree, click New page and pick a title and slug.
Paste your Markdown
Paste the body into the editor. Markdown — headings, lists, links, code blocks, blockquotes — converts to blocks as it lands.
Replace platform-specific blocks
Anything your old platform did with custom syntax (admonitions, tabs, callouts) won't auto-convert. Insert the Dokly equivalent from the slash menu — see the mappings below for each source.
Set page settings
Open the page settings panel and fill in description, parent, and SEO fields. See Page settings.
From Mintlify#
Mintlify stores pages as Markdown files in a Git repo. Migration is mostly copy-paste plus a few component swaps.
| Mintlify | Dokly equivalent |
|---|---|
<Note> | Info Callout |
<Warning> | Warning Callout |
<Tip> | Tip Callout |
<Info> | Info Callout |
<CodeGroup> | Tabs |
<Frame> | Plain image (Dokly auto-frames images) |
<Card>, <CardGroup> | Card, Card Group (same names) |
<Steps>, <Tabs> | Steps, Tabs (same names) |
For Mintlify-specific frontmatter (mode: wide, sidebarTitle, iconType):
sidebarTitle→ set the sidebar title field in page settings.mode: wide→ not yet supported (pages are responsive by default).iconon a card → keep it; Dokly accepts the same icon names.
From GitBook#
GitBook exports Markdown via Settings → Export. The output is a zip of .md files mirroring your sidebar tree.
Replace these GitBook constructs:
| GitBook | Dokly equivalent |
|---|---|
{% hint style="info" %} | Info Callout |
{% hint style="warning" %} | Warning Callout |
{% tabs %} | Tabs |
{% code-group %} | Tabs |
GitBook exports don't include slugs. Generate one per page based on its path and set it in page settings.
From Docusaurus#
Docusaurus pages are Markdown in a docs/ folder.
| Docusaurus | Dokly equivalent |
|---|---|
:::tip ... ::: | Tip Callout |
:::warning ... ::: | Warning Callout |
<Tabs> with <TabItem> | Tabs |
| Custom imported components | Pick the closest Dokly block; complex widgets may need a rewrite |
Docusaurus's sidebar_position becomes the Order field in page settings. sidebar_label becomes Sidebar title. slug works the same way.
If your Docusaurus pages have import statements at the top, drop them — Dokly's blocks are available everywhere.
From ReadMe#
ReadMe doesn't expose Markdown directly. Two options:
- Manual rewrite. For small docs (under ~30 pages), the fastest path is to read each ReadMe page and rewrite it in Dokly. You'll improve a lot of pages along the way.
- HTML scrape + cleanup. For larger docs, scrape the rendered HTML and convert to Markdown with a tool like Pandoc, then paste each page in. Plan for significant cleanup — automated conversion produces ugly Markdown.
ReadMe Recipes don't have a direct equivalent — convert them to a Steps block with code blocks inside.
From Notion#
Notion exports as Markdown via Workspace Settings → Export. The output is messy — Notion's blocks don't map cleanly.
The realistic path:
- Export to Markdown.
- Use the export as a raw source you'll edit heavily.
- Or use Generate with AI in Dokly with the exported text as the brief, and let it produce a cleaner first draft you can refine.
You'll spend less time on a half-broken automated conversion than on a clean rewrite.
General approach#
For any source not listed:
- Get your content out as Markdown or HTML (one file per page).
- Convert HTML to Markdown if needed (Pandoc, Turndown).
- Paste each page into a new Dokly page.
- Replace platform-specific syntax with Dokly blocks via the slash menu.
- Set title, slug, description, and sidebar placement in page settings.
For 50+ page migrations, talk to us — we can sometimes provide a one-off importer or do the migration as a paid service.
After migration#
Run through the SEO checklist to make sure:
- Slugs match the URL patterns from your old site (preserves SEO rankings).
- Set up redirects from old paths to new paths if slugs changed.
- Submit the new sitemap to Google Search Console.
- Update any external links pointing at the old docs.