简体中文
EnglishCan I import my existing worldbuilding content into Chronicler?
Updated
Yes. Chronicler has built-in importers for Word, Google Docs, and Fandom/MediaWiki sites, and it works natively with Obsidian vaults. The site describes migration as taking "minutes" rather than requiring you to rebuild your world by hand. Because everything is stored locally as plain-text Markdown files, imported content stays portable after it lands in Chronicler.
What you can bring in
| Source | How it works | What to expect |
|---|---|---|
| Obsidian vault | Native compatibility | Your vault structure carries over, since both tools work with Markdown |
| Word documents | Built-in importer | Text content moves into Chronicler's wiki format |
| Google Docs | Built-in importer | Same as Word — your writing transfers without retyping |
| Fandom / MediaWiki sites | Built-in importer | Wiki pages come across instead of being recreated page by page |
If your world currently lives in any of these, you don't need to start from zero.
Why migration is quick
The reason import is practical rather than painful comes down to storage format. Chronicler keeps all data locally as plain-text Markdown files. Markdown is a common denominator across Obsidian, many note tools, and wiki exports, so there's less to translate.
That also means the migration isn't one-way in a locked sense. Once your content is in Chronicler, it's still plain text on your machine — you own the files, and there's no data lock-in described.
Step-by-step: importing your content
- Download and install Chronicler for Windows, macOS, or Linux. It's free and offline, so no account or cloud step is required.
- Identify your source type — Obsidian vault, Word file, Google Doc, or a Fandom/MediaWiki site.
- Use the matching importer. For Obsidian, point Chronicler at your vault. For Word, Google Docs, or MediaWiki, use the built-in importer for that format.
- Verify the result. Check that your pages, links, and structure arrived as expected. Because content is Markdown, you can open the files directly to confirm.
- Reconnect your world. Use Chronicler's linking and tagging to rebuild relationships between characters, places, and factions — the importer moves content, but you'll want to confirm your cross-references read the way you intend.
Expected result: your existing writing appears as linked wiki pages inside Chronicler, editable in the live split-screen editor, without manual retyping.
Common snags to plan for
- Cross-links may need a pass. Importers move content; internal wiki-style links between pages are worth checking after import, especially from Word or Google Docs where linking conventions differ.
- Formatting isn't always 1:1. Headings and basic structure usually survive Markdown-friendly sources well. Complex layouts from Word or Docs may need light cleanup.
- MediaWiki imports vary by site. Fandom/MediaWiki structures aren't uniform, so expect to review page organization rather than assume a perfect match.
- Obsidian is the smoothest path. If you're choosing where to consolidate first, an Obsidian vault is the closest fit because both tools are Markdown-native.
Who this is for
Chronicler is built for writers, novelists, and tabletop RPG game masters who want a private worldbuilding wiki. If you already have years of lore in Word, Google Docs, Obsidian, or a Fandom wiki and you're wary of subscriptions or cloud lock-in, the importers exist specifically so you don't lose that work. The site reports 17,080+ unique installations and a 98.7% Reddit upvote ratio, suggesting the migration path is working for a real community of users.
If your content lives somewhere none of these importers cover, you'd be looking at a manual copy-paste into Markdown — still workable, just slower.