Which Path Should I Use?
There are several ways to get content into a Moxn knowledge base. Pick based on where it lives today and how much you’re moving.
The in-app Notion integration and the CLI use the same migration engine, so the resulting documents, databases, tags, and cross-references are identical — they just differ in where the job runs and how you trigger it.
Import
Bring existing documentation into Moxn from external sources.Notion (in-app)
Connect once in Settings > Integrations — Moxn runs the import for you
OneNote (in-app)
Sign in with Microsoft and bring a notebook into Moxn
Notion (CLI)
Run the same import from your terminal or CI with full flag control
Local Files (CLI)
Markdown, text, and CSV files from your filesystem — CLI only
Export
Get your docs back out of Moxn in the format you need.Notion (in-app)
Push KB docs back to Notion from Settings > Integrations
Notion (CLI)
Push pages back to Notion from the command line
Local Files (CLI)
Download as markdown with images, PDFs, and CSVs
CLI: Two Install Flavors
The CLI is published under two names. Both wrap the same migration engine — pick whichever is most convenient:
Use
@moxn/context-cli if you already have it installed for other Moxn commands. Use npx @moxn/kb-migrate for one-off runs without a global install.
Date Filtering
All CLI commands (and the in-app integration) support date filters to narrow the scope of your import or export:YYYY-MM-DD or full datetime). In the in-app integration, set the same range under Date filter in the Configure step.