Data management across various personal knowledge systems can be a complex task. Many developers and knowledge workers find themselves with valuable information spread across multiple tools, making a consolidated view challenging. Omni Apps introduces an AI agent skill designed to address this: migrate. This skill facilitates universal data migration from any wiki, note tool, or brain system directly into the brain. Its purpose is clear: to transfer data from external knowledge systems while meticulously preserving cross-references and metadata. This ensures that the context and connections within your original data remain intact after the transfer.
How migrate Works: The Five
Phases of Data Transfer The process of transferring your knowledge with the migrate skill is structured into five distinct phases, ensuring a controlled and verifiable import.
First, the system will assess the source format. This initial step involves understanding the structure and specific characteristics of your current data repository, whether it's an Obsidian vault, Notion export, or a directory of plain markdown files. This assessment is crucial for accurate interpretation.
Second, you plan field mapping. Here, you define how elements from your source system, such as titles, content blocks, or tags, will correspond to the fields within the destination brain. This mapping ensures that data lands in the correct place.
Third, a test with 5-10 sample files is conducted. This phase is critical for validating the planned mapping and ensuring that the data migration behaves as expected on a small scale. This prevents issues from propagating across a large dataset. Importantly, the skill employs round-trip verification: pages written during this test are immediately read back and spot-checked. This step is a critical constraint, designed to avoid the need to clean up hundreds of bad pages if an error is detected. Only if these spot-checks pass does the process move forward.
Fourth, the skill proceeds to execute the bulk import. Once the sample tests and verification are successful, the full dataset is transferred.
Finally, verify via health checks and spot-reading. After the bulk import is complete, a final verification step involves running health checks and performing spot-reading on a larger selection of imported data. This confirms the integrity and accuracy of the entire migration.
A key design principle of the migrate skill is its non-destructive nature. Your source data is never touched or modified during any part of this process. This means your original information remains completely safe and undisturbed in its native system.
Supported
Systems and Practical Usage The migrate skill supports a variety of common knowledge management systems, enabling broad applicability for many users. It can handle data from Obsidian, including sophisticated wikilink conversion, which translates internal Obsidian links into the brain's linking structure. For users migrating from Notion, the skill processes exported markdown and CSV files. Logseq users will find their block references are accurately maintained, preserving the intricate web of connections within their notes. Beyond these, the skill also supports plain markdown directories, generic CSV files, JSON data, and Roam exports.
To initiate a migration, the skill responds to specific triggers. You can use phrases like 'migrate from', 'import from obsidian', or 'import from notion' to start the process. For instance, if you have a collection of notes in a plain markdown directory, you might issue a command like: migrate from my_markdown_notes_folder. The agent would then guide you through the five phases, ensuring your files are correctly parsed, mapped, and imported into your brain, with all internal links respected. This provides a direct path for consolidating dispersed knowledge.
Core
Functionality and Constraints
The migrate skill focuses on a specific set of operations, primarily data transfer and structural preservation. Internally, it uses tools like put_page to write content, search to locate existing information, add_link to establish connections between pages, add_tag to categorize imported content, and sync_brain to ensure the new data is integrated.
It deliberately avoids destructive operations; as mentioned, source data is never touched. This provides peace of mind that your original information sources are always preserved. The round-trip verification, where pages written are read back and spot-checked before bulk execution, is a critical safeguard. This prevents the large-scale creation of bad pages, which would be time-consuming to correct.
It is important to understand the scope of the migrate skill. It is not designed for selective imports, meaning it handles comprehensive data transfers rather than picking individual notes. Furthermore, it does not perform data transformation beyond field mapping. If complex data manipulation or cleaning is required, that would need to be handled prior to using this skill. Its strength lies in its ability to move existing, structured knowledge efficiently.
FAQ
Q1: What kind of data can I migrate with this skill? A: You can migrate data from any wiki, note tool, or brain system. Specifically, it supports Obsidian (with wikilink conversion), Notion (exported markdown/CSV), Logseq (block references), plain markdown directories, CSV, JSON, and Roam exports.
Q2: Is my original data safe during migration? A: Yes, absolutely. The migrate skill deliberately avoids destructive operations; your source data is never touched or modified during the entire transfer process.
Q3: Can I pick and choose specific notes or sections to migrate? A: No, this skill is not designed for selective imports. It performs comprehensive data transfers from a specified source system or directory.
Conclusion
The migrate skill offers a robust method for bringing your existing knowledge into the Omni Apps brain. It provides a structured, verifiable approach to data migration, respecting the integrity of your original information while establishing new connections within your unified knowledge base.
