Migrating Evernote Notes to Obsidian for Research

By Dr. Zubair Khalid, DVM, MS, PhD · 2026-08-27

Quick Answer

• Export Evernote notes as ENEX files, then convert them to Markdown for Obsidian using a conversion tool that preserves attachments and note links.
• Verify metadata such as creation dates, tags, and source URLs survive the conversion before deleting any Evernote data.
• Evernote's proprietary formatting and embedded images can break during conversion, so inspect a sample of notes after migration and keep your ENEX backups until you confirm everything works.

Understanding the Migration Problem

Researchers accumulate thousands of notes in Evernote over years of literature reading, lab work, and project planning. The proprietary ENEX format locks that intellectual work inside a single platform. Moving to Obsidian requires converting notes into plain Markdown files that Obsidian can read, while preserving the connections between notes, the attachments that support them, and the metadata that makes them searchable.

The core challenge is not copying text. It is maintaining the relational structure of your research notes. Evernote uses internal note links, tags, and notebook hierarchies. Obsidian uses a flat folder structure with wiki-style links and YAML frontmatter for metadata. A direct copy produces broken links, orphaned attachments, and lost timestamps.

Your migration plan must address five distinct elements: note content, note links, attachments, metadata, and notebook organization. Each element requires a different handling strategy, and each has specific failure modes you need to anticipate.

At a Glance

Preparing Your Evernote Data for Export

Before you export anything, audit what you actually have. Open Evernote and review your notebook list. Count your notes, identify which notebooks contain active research versus archived material, and note any notes that contain large attachments such as PDFs, audio files, or embedded images.

Clean your data before migration, not after. Delete duplicate notes, merge fragmented notes that belong together, and remove notes that no longer have research value. This reduces conversion time and limits the number of broken references you need to repair.

Check for notes that use Evernote-specific features that do not translate well. Encryption, audio recordings, and handwritten ink notes require special handling. Encrypted text may not convert cleanly to Markdown. Audio and ink notes become attachment files instead of searchable text. Decide whether you need these elements in Obsidian or whether you can archive them separately.

Verify that your Evernote application is updated and that you have sufficient disk space for the export files. ENEX files can be large when they contain attachments. A notebook with hundreds of PDFs can produce a multi-gigabyte export file.

Exporting Notes from Evernote

Evernote provides a native export function that creates ENEX files. The exact menu path depends on your operating system and Evernote version, but the general workflow is consistent across platforms.

Select the notebooks you want to migrate. Export each notebook separately instead of exporting your entire account at once. Separate exports give you manageable file sizes and let you verify each notebook independently after conversion.

Choose the ENEX format in the export dialog. Evernote also offers an HTML export option, but ENEX is the preferred format because it preserves more metadata and attachment structure. The ENEX file is an XML document that contains the note content, tags, creation dates, and embedded attachments.

Keep your original Evernote data intact after export. Do not delete notebooks or close your account until you have verified that the Obsidian conversion worked correctly. Your ENEX files are your backup during the migration process. Store them in a location outside Evernote, such as an external drive or cloud storage folder.

Converting ENEX Files to Markdown

The ENEX format is not directly readable by Obsidian. You need a conversion tool that parses the XML structure and outputs Markdown files. Several open-source tools exist for this purpose, and they vary in their handling of attachments, links, and metadata.

Select a conversion tool that matches your technical comfort level. Command-line tools give you more control over the output but require familiarity with terminal operations. Graphical tools are easier to use but may offer fewer customization options.

Run the conversion on a single test notebook first. This lets you inspect the output quality before committing your entire library. Check how the tool handles code blocks, tables, images, and internal links. Look at the generated YAML frontmatter to confirm that tags and dates transferred correctly.

Review the tool's documentation for known limitations. Some converters do not preserve note creation dates. Others flatten tag hierarchies or fail to convert certain attachment types. Understanding these limitations before you run a full migration helps you plan remediation steps.

After conversion, inspect the output folder structure. Obsidian uses a vault, which is simply a folder that contains your Markdown files and attachments. Your converter may create a flat folder with all notes, or it may preserve notebook structure as subfolders. Decide which organization method works for your research workflow.

Handling Attachments and Embedded Files

Attachments are the most fragile part of an Evernote migration. Evernote embeds images, PDFs, and other files directly in the ENEX XML. Conversion tools extract these files and save them to a folder, then reference them from the Markdown notes.

Verify that image references in your converted notes point to the correct file paths. A common failure is relative path mismatches, where the Markdown note references an image location that does not match where the converter placed the file. Open several converted notes in Obsidian and confirm that images display correctly.

Check the file types of your extracted attachments. Evernote stores some content as proprietary formats that Obsidian cannot display natively. Audio notes and ink notes fall into this category. You may need to export these separately or convert them to standard formats before adding them to your vault.

Consider how you want to organize attachments in your Obsidian vault. Some researchers prefer a single attachments folder for all files. Others keep attachments in subfolders that mirror their note organization. Obsidian supports both approaches, but you need to configure your attachment folder settings before you import your converted files.

Preserving Note Links and References

Evernote internal links use a URL scheme that Obsidian does not understand. When you click an Evernote link in a converted note, it will not open the target note. You need to convert these links to Obsidian wiki links.

The conversion process for links depends on your tool. Some converters automatically rewrite internal links to wiki format. Others leave the original URLs intact, requiring manual repair. Test this behavior in your trial conversion before processing your full library.

Wiki links in Obsidian use the note filename as the link target. This means your note filenames must be unique and descriptive. If two notes share the same name, Obsidian cannot determine which note a link should point to. Review your converted filenames and rename any duplicates before you start linking notes.

External links to websites and DOI links should survive conversion without modification. Verify that URLs in your converted notes still point to the correct destinations. Some converters may mangle URLs that contain special characters or query strings.

Managing Metadata and Tags

Evernote tags and metadata need explicit handling during migration. The ENEX format stores tags as a flat list per note. Obsidian stores tags in YAML frontmatter or inline in the note body. Your converter should transfer tags to the frontmatter, but you need to verify this happened.

Check that creation dates and modification dates transferred correctly. These timestamps matter for research records because they document when you captured a finding or developed an idea. If your converter does not preserve dates, you may need to extract them from the ENEX file manually or accept the loss.

Source URLs are critical metadata for research notes. If you clipped web pages into Evernote, the source URL is stored in the note metadata. Verify that these URLs appear in your converted frontmatter. Losing source attribution undermines the research value of your notes.

Tag hierarchies do not transfer cleanly. Evernote allows nested tags, while Obsidian treats tags as flat strings. A tag like Research/Methods in Evernote becomes a single tag in Obsidian unless you configure your converter to split it. Decide whether you need tag hierarchy or whether flat tags suffice for your workflow.

Organizing Your Obsidian Vault

After conversion, you have a folder of Markdown files and attachments. Before you start using the vault, establish an organization structure that supports your research workflow.

Create a folder structure that mirrors your research projects or topics. Obsidian does not require folders, but they help you navigate large vaults. Some researchers prefer a flat structure with heavy tag use. Others need project-based folders. Choose the approach that matches how you actually work.

Set up your Obsidian settings before importing notes. Configure the default attachment folder, new note location, and template settings. These choices affect how Obsidian behaves when you create new notes and insert images.

Install plugins that support research workflows. The core plugins include backlinks, graph view, and search. Community plugins add citation management, Zotero integration, and advanced tables. Install only what you need and verify each plugin works with your converted notes.

Verifying Migration Completeness

Verification is not optional. You need to confirm that every note, attachment, and link survived the migration before you retire Evernote.

Create a verification checklist and work through it systematically. Count the notes in your Evernote account and compare that number to the Markdown files in your vault. Check that every notebook has a corresponding folder or tag set. Spot-check notes from each notebook to confirm content integrity.

Test links by opening notes in Obsidian and clicking internal links. Verify that images display and that attachment files exist at the referenced paths. Search for common conversion artifacts such as raw HTML tags, broken image references, or garbled code blocks.

Check your metadata by sorting notes by creation date and confirming the dates look correct. Review your tag list in Obsidian and compare it to your Evernote tag list. Identify any tags that did not transfer.

Keep your ENEX files until you complete verification. Do not delete your Evernote account or notebooks until you have used the Obsidian vault for several weeks and confirmed it meets your needs.

Common Failure Patterns and Solutions

Several failure patterns recur across Evernote to Obsidian migrations. Knowing these patterns helps you diagnose problems quickly.

Broken image paths are the most common issue. The converter places images in one folder while the Markdown references another location. Fix this by moving images to match the references or by updating the references to match the actual file locations.

Lost formatting occurs when Evernote's rich text does not convert cleanly to Markdown. Bold, italics, and headings usually survive, but complex formatting such as nested tables, colored text, and custom fonts may not. Accept that some formatting loss is inevitable and focus on preserving content.

Code blocks often break during conversion. Evernote stores code with language hints that may not transfer. Check your code blocks and reapply language tags where needed.

Encrypted notes convert to unreadable content. Evernote encryption does not translate to Obsidian. If you have encrypted notes, decrypt them before export or plan to handle them separately.

Large attachments may fail to extract. Some converters time out on very large files or skip them entirely. Check your attachment folder against your Evernote attachment list to identify missing files.

Limitations of the Migration Process

The migration process has inherent limitations that you should understand before you start.

Evernote's search functionality does not transfer to Obsidian. Obsidian uses a different search engine with different syntax and capabilities. You will need to learn Obsidian's search operators and may need to reorganize your notes to make them findable.

Evernote's web clipper integration does not have a direct Obsidian equivalent. You will need to configure a new clipping workflow using Obsidian's web clipper or a third-party tool. This changes how you capture web content for your research.

Collaborative features differ between platforms. Evernote supports shared notebooks and real-time collaboration. Obsidian's collaboration options require additional setup and may not match Evernote's simplicity. If you share notes with colleagues, plan for this workflow change.

Mobile access works differently. Evernote's mobile app is mature and feature-rich. Obsidian's mobile app is functional but has limitations. Test the mobile experience with your converted notes before committing to the migration.

Professional Escalation Criteria

Some migration situations require professional assistance. Recognize when your technical skills or time constraints warrant outside help.

If you have more than 10,000 notes, the migration will take significant time and careful planning. A professional data migration specialist can build custom conversion scripts and verify the output at scale.

If your notes contain sensitive research data subject to institutional policies, consult your institution's IT or data stewardship office before migrating. Your institution may have specific requirements for handling research data across platforms.

If you use Evernote for regulatory or compliance purposes, verify that the migration preserves the records you need. Some regulated research environments require audit trails and specific metadata that may not survive conversion.

If your conversion produces systematic errors that you cannot diagnose, seek help from the conversion tool's support community or a consultant familiar with Obsidian migrations. Do not spend days troubleshooting a problem that an expert can solve in hours.

Building a Migration Decision Framework for Research Note Integrity

A successful Evernote to Obsidian migration depends on decisions you make before you export a single note. Researchers often start converting files without a structured framework, then discover that their literature review notes, lab observations, and project plans require different handling. A decision framework helps you classify each notebook by its research function, data sensitivity, and long-term value before you choose conversion settings.

Classifying Notes by Research Function

Start by sorting your notebooks into three functional categories. Active research notebooks contain notes you consult weekly for ongoing projects, manuscript preparation, or grant applications. Reference notebooks hold literature summaries, method protocols, and background material you access periodically. Archive notebooks contain completed project records, old course notes, or material you keep for compliance reasons.

Each category demands different migration priorities. Active research notes need working internal links, preserved source URLs, and searchable full text because you depend on them daily. Reference notes require accurate metadata and attachment integrity because you may cite them in future publications. Archive notes need faithful content preservation but tolerate some formatting loss because you rarely open them.

Apply this classification to every notebook before export. Create a simple inventory table listing notebook name, functional category, note count, attachment size, and migration priority. This inventory becomes your verification baseline after conversion.

Assessing Data Sensitivity and Institutional Requirements

Research notes often contain data governed by institutional policies, funding agreements, or publication ethics standards. Before migrating, identify which notebooks contain unpublished findings, personal participant data, proprietary methods, or materials under embargo for journal submission.

The NIH Grants and Funding portal describes expectations for managing research records across the award lifecycle. If your Evernote library supports NIH-funded work, check whether your migration plan aligns with the Data Management and Sharing Policy expectations for preserving and documenting research data. The Committee on Publication Ethics Core Practices address data integrity and record-keeping expectations that apply to research notes supporting future publications.

For notebooks containing sensitive data, document your migration steps in a written plan. Record which notebooks you converted, which conversion tool you used, and how you verified data integrity. This documentation supports future audits and demonstrates responsible data stewardship.

Selecting Conversion Settings by Note Type

Your functional classification determines which conversion settings matter most. For active research notes with heavy internal linking, prioritize a converter that rewrites Evernote URLs to Obsidian wiki links. For reference notebooks with many PDF attachments, prioritize attachment extraction reliability over link conversion. For archive notebooks, accept default settings because content preservation matters more than formatting fidelity.

Create a conversion matrix that maps each notebook category to specific tool settings. Include fields for link handling, attachment folder structure, metadata preservation, and tag hierarchy treatment. Test each configuration on a sample of notes from that category before running the full conversion.

Establishing a Verification Hierarchy

Verification should follow the same priority order as your migration. Check active research notes first because they carry your current intellectual work. Verify that internal links resolve, source URLs appear in frontmatter, and recent edits transferred with correct timestamps.

For reference notes, verify attachment integrity and citation metadata. Open sample PDFs and confirm they are not corrupted. Check that DOIs and publication details survived conversion.

For archive notes, perform a sampling check instead of exhaustive verification. Confirm that note counts match your inventory and spot-check content from each archive notebook.

Recording Migration Decisions and Outcomes

Maintain a migration log that documents every decision you make. Record the tool version, conversion date, settings used for each notebook category, and verification results. Note any anomalies you discovered and how you resolved them.

This log serves multiple purposes. It provides evidence of due diligence if you need to explain your data management practices to collaborators or institutional reviewers. It helps you troubleshoot problems that surface weeks after migration. It also documents your workflow for future migrations as your research library grows.

The EQUATOR Network emphasizes transparent reporting of research methods. While designed for scientific publications, the same principle applies to research data management. A documented migration process strengthens the integrity of your research records.

Handling Researcher Identity and Attribution

Research notes often connect to your scholarly identity through author names, ORCID identifiers, and publication records. Before migrating, check whether your notes contain references to your published work or collaborative projects that require accurate attribution.

The ORCID for Researchers resource explains how persistent researcher identifiers support accurate attribution across platforms. If your Evernote notes contain publication lists or collaboration records, verify that author names and affiliations transfer correctly to Obsidian. This matters for grant applications and promotion reviews that draw on your research records.

Building a Rollback Plan

Every migration needs a defined rollback path. Your ENEX files serve as the primary backup, but you should also document how to restore your Evernote data if the Obsidian vault proves unusable.

Store ENEX files in two locations. Keep one copy on an external drive and another in cloud storage. Record the Evernote version that created the exports so you can reinstall a compatible version if needed.

Set a rollback trigger date. Decide in advance how long you will test the Obsidian vault before declaring the migration successful. A typical evaluation period is four to six weeks of active research use. If critical workflows remain broken after that period, restore from ENEX and reassess your conversion approach.

Common Decision Errors

Researchers make predictable mistakes when deciding how to migrate. The most common error is treating all notebooks identically. A literature review notebook with 500 web clippings requires different handling than a lab notebook with embedded experimental images.

Another error is skipping the inventory step. Without a baseline count of notes and attachments, you cannot verify migration completeness. Create the inventory before export and compare it against your converted vault.

A third error is ignoring institutional requirements until after migration. Check your funding agreements and institutional data policies before you convert anything. Retrofitting compliance after migration is more difficult than planning for it from the start.

Professional Escalation Criteria

Escalate to professional assistance when your decision framework reveals gaps you cannot address. If you cannot classify your notebooks because your Evernote library is disorganized, consider a data cleanup project before migration. If your institutional policies require specific metadata preservation that your chosen converter cannot provide, consult your IT office or data steward.

If your research involves regulated data or clinical information, involve your institution's compliance office before migrating. The Research Methods Resources gateway provides access to authoritative references on research data management that can inform your decisions.

Seek help when your verification reveals systematic data loss that you cannot diagnose. A consultant familiar with Obsidian migrations can identify conversion patterns that cause recurring problems and build custom solutions. The cost of professional assistance is justified when it prevents the loss of years of research notes.

Frequently Asked Questions

Will my Evernote notebooks become Obsidian folders?

Not automatically. Your converter may create folders that mirror your notebook structure, or it may produce a flat file list. You can reorganize the files after conversion to match your preferred structure. Obsidian does not require folders, so you can also use tags to replicate notebook organization.

Can I keep my Evernote account after migrating to Obsidian?

Yes. Keep your Evernote account and ENEX backups until you have verified the Obsidian migration and used the vault for several weeks. This gives you a fallback if you discover missing data or broken content.

How long does a migration take?

The time depends on your note count, attachment sizes, and your familiarity with the tools. A small notebook can convert in minutes. A large library with thousands of notes and large attachments can take several hours of conversion time plus additional hours of verification and cleanup.

Will my Evernote tags transfer to Obsidian?

Most converters transfer tags to YAML frontmatter in the Markdown files. Verify this happened by comparing your tag lists. Nested tags may flatten to single strings, and you may need to adjust tag names after conversion.

What happens to my Evernote web clipper notes?

Web clipper notes convert like any other note. The source URL should appear in your frontmatter if the converter preserves metadata. You will need to set up a new web clipping workflow for Obsidian, since the Evernote clipper does not work with Obsidian.

Can I migrate only some notebooks instead of everything?

Yes. Export only the notebooks you want to migrate. This is often the best approach for large accounts. Migrate active research notebooks first, verify the process works, then migrate archived notebooks or leave them in Evernote.

Will my note links work after conversion?

Internal Evernote links will not work in Obsidian unless your converter rewrites them to wiki format. Test this in a trial conversion. External URLs and DOIs should transfer without modification.

Do I need to install plugins for Obsidian to use my converted notes?

No. The core Obsidian features handle Markdown notes, links, and attachments. Plugins add functionality such as citation management and advanced tables, but they are optional. Start with core features and add plugins as you identify needs.

Using the Evidence

Related Articles

• Data Management Plan Template: A Practical Guide for Researchers
• The Role of the Research Ethics Committee: What Researchers Need to Know
• Git for Research Projects: Version Control for Code, Data, and Analysis Notes
• Research Data Management Plan: From File Naming to Long-Term Sharing
• Protein Synthesis Step By Step

References and Further Reading

• Research Methods Resources. National Library of Medicine.
• EQUATOR Network. EQUATOR Network.
• Core Practices. Committee on Publication Ethics.
• NIH Grants and Funding. National Institutes of Health.
• ORCID for Researchers. ORCID.
• Data Management and Sharing Policy. National Institutes of Health.
• NCBI Literature Resources. National Center for Biotechnology Information.
• PubMed. National Library of Medicine.

This article is educational and does not replace institutional policy, professional advice, or applicable safety and regulatory requirements.