wiz-migration

What This Skill Does

The wiz-migration skill acts as an intelligent migration assistant specifically engineered for users transitioning away from the WizNote (为知笔记) platform. It streamlines the complex task of data extraction and structured migration by automating the discovery of local data stores, providing a standardized roadmap for exporting notes in HTML format, and handling the tedious batch migration of attachment folders. By leveraging a structured command-line interface and supporting batch scripts, it ensures that your knowledge base remains intact—preserving directory structures and avoiding common pitfalls like data loss or broken image references.

Installation

To install this skill, use the OpenClaw CLI tool to pull from the official repository:

clawhub install openclaw/skills/skills/awamwang/wiz-migration

Once installed, you can trigger the interactive assistant via openclaw skill wiz-migration start or import it directly into your Python automation workflows using the provided library functions.

Use Cases

• Knowledge Base Consolidation: Efficiently move years of archived WizNote research into modern tools like Obsidian, Notion, or local file systems.
• Backup Automation: Create periodic, structured exports of your WizNote content for long-term storage or offline archival.
• Developer Workflows: Integrate document retrieval into broader data analysis pipelines by transforming proprietary WizNote blobs into standard, portable HTML files with correctly mapped assets.

Example Prompts

• "OpenClaw, start the wiz-migration wizard to help me find my local notebook files and begin the export process."
• "I have finished exporting my notes to the 'Wiz_Export' folder. Can you run the attachment migration script to sync the _Attachments directories?"
• "Help me generate the export guidelines for migrating my notes and explain why I shouldn't select 'Single HTML file' during the process."

Tips & Limitations

• Critical Export Step: Always choose 'Export as multiple web files' in WizNote. Opting for 'Single HTML' will base64-encode your attachments, making them difficult to extract or search later.
• Permissions: The migration script performs file operations on your machine. Ensure your terminal has appropriate write permissions to the destination folder before execution.
• Scalability: While the included script handles large volumes of attachments by skipping existing files, extremely large databases (over 50GB) may take significant time to index; please be patient during the 'detect_wiz_data_dir' phase.
• Validation: After migration, perform a spot check on your HTML files to verify that internal relative links to '_files' directories are correctly resolved.