03 · What You Need to Know
Your Reference Library Is More Than Its Citation Metadata
A mature reference library may contain years of accumulated research work. The visible citation record is only one part of it.
Before migrating, it helps to separate the library into layers.
| Library component |
What it contains |
Migration concern |
| Bibliographic metadata |
Authors, titles, dates, publication details, DOI, ISBN, and other fields |
Usually transferable, but field mappings and supported item types can differ |
| PDFs and other attachments |
The actual full-text files and supplementary documents |
May need separate file export or transfer |
| PDF annotations |
Highlights, underlining, comments, and other marks associated with a document |
May be embedded in the PDF or stored separately by the reference manager |
| Reference-manager notes |
Your summaries, interpretations, reading notes, and other text |
May not map cleanly into another application's note system |
| Tags |
Topics, methods, workflow states, or other labels |
Often transferable in some formats, but behavior can differ |
| Collections or folders |
Project and organizational structure |
May not survive generic bibliographic export exactly |
| Citation links in manuscripts |
Connections between inserted citations and the original reference-manager records |
Usually software-specific and should not be assumed to transfer to another citation system |
This is why a successful migration cannot be judged merely by comparing the number of references before and after import.
First identify where your annotations are stored
A highlighted PDF can look identical on screen even when the annotation is stored in fundamentally different ways.
Traditional PDF annotation software often writes highlights and comments directly into the PDF file. If you copy that file elsewhere and open it in compatible software, those embedded annotations generally travel with the PDF.
Other systems can store annotations separately.
Zotero's built-in PDF reader, for example, stores Zotero-created annotations in the Zotero database rather than writing them directly into the original PDF. Zotero explains that this design supports efficient syncing, group use, and integration with its note system. As a consequence, simply locating the underlying PDF file and copying it does not necessarily give you a PDF containing the visible Zotero annotations.
Zotero provides a supported solution: it can export a copy of the PDF with its Zotero annotations embedded into the exported file.
Embedded PDF annotation
The annotation is stored inside the PDF file and can generally travel with that file to software capable of reading standard PDF annotations.
Database-managed annotation
The reference manager stores annotation information separately and renders it with the PDF. The original PDF alone may not contain those annotations.
Knowing which model your current software uses is essential before you copy thousands of PDFs and assume the migration is finished.
Exporting annotated PDFs can provide a portable fallback
If annotations are stored separately from the PDF, exporting copies with annotations embedded can create a more portable representation of your reading work.
Zotero explicitly supports this. Its documentation states that PDFs can be exported with Zotero annotations embedded, and its library export options can include annotations in exported PDFs when files are included. Zotero presents this as part of its approach to data portability.
This does not guarantee that the destination reference manager will reconstruct those annotations as fully editable native annotations with exactly the same colors, tags, comments, links, or internal relationships. It does mean that the annotation can remain represented in a standard PDF rather than existing only inside the original application's database.
That distinction is important. Preserving what you can see is not always the same as preserving how the original software understands it.
Your notes may be separate from your annotations
A highlight and a research note are not necessarily the same object.
You may highlight a sentence in a PDF and then write a longer note explaining why the passage matters to your theoretical framework. Some reference managers also let you convert or incorporate annotations into notes.
Zotero, for example, supports child and standalone notes, and notes are stored and synchronized as library data. Its current PDF reader can add individual annotations to notes or create notes from all annotations associated with an item. Those notes can contain links back to the annotated PDF location and citation information.
If those notes contain substantive analysis, preserve them deliberately. Exporting annotated PDFs alone may retain highlights and comments while failing to preserve a separate note containing your synthesis of the paper.
Do not assume RIS or BibTeX represents your entire library
RIS, BibTeX, and other bibliographic exchange formats are valuable because many reference managers can read them. Their principal job, however, is bibliographic data exchange.
A reference library may contain richer application-specific information than a generic interchange format can represent. Notes, collections, attachment relationships, annotation objects, custom fields, and other structures may be transferred incompletely or differently depending on the source format and destination software.
Zotero itself cautions that exporting and reimporting a library can produce changes or missing fields depending on the format. For transfers between Zotero users, it recommends Zotero RDF with files and notes for the most complete transfer within its own ecosystem. It also warns that exported and reimported items will no longer retain their existing links to citations in word-processor documents.
When moving to another reference manager, choose the export format according to what the destination officially supports rather than assuming that one format preserves everything.
Bibliographic portability and annotation portability are different problems
You can migrate perfect citation metadata while losing your reading history. You can also preserve every annotated PDF while importing poor bibliographic records.
Treat those as separate verification tasks.
Bibliographic migration Verify that authors, titles, item types, publication details, identifiers, and other important fields survived correctly.
File migration Confirm that the expected PDFs and other attachments can actually be opened from the destination library.
Annotation migration Open representative annotated PDFs and verify that highlights, comments, and other annotations remain visible and usable.
Note migration Check whether your analytical notes survived, remain associated with the correct references, and preserve the content you need.
A migration can succeed in one layer and fail in another.
Your PDF strategy affects how difficult migration will be
If your reference manager stores the PDFs internally, the migration process may need to export or otherwise move those managed files. If your reference manager merely links to an external PDF directory, the files may already exist independently, but the destination software still needs to reconnect bibliographic records with them.
This is one reason the earlier decision about whether to attach PDFs to your reference manager has long-term consequences. A convenient reading workflow today can create either a straightforward or complicated migration later depending on how the platform stores files and annotations.
Neither model is inherently wrong. What matters is knowing what your current system actually does.
Do not move files before understanding their relationships
When preparing to migrate, it can be tempting to begin reorganizing folders immediately. That may be risky if your existing reference manager uses linked files.
A linked attachment may depend on the file remaining at a particular filesystem location. Moving the file first can break the relationship before you have completed the migration.
Similarly, manually copying a managed storage directory without understanding its structure may give you a folder full of PDFs with cryptic filenames or no obvious connection to their bibliographic records.
Use the reference manager's supported export or migration mechanisms wherever practical, and preserve the original library until the destination has been verified.
Notes deserve a migration strategy of their own
Researchers often devote more intellectual effort to notes than to highlights.
A note might contain a critique of a study's design, an explanation of how two theories connect, a draft paragraph, a methodological idea, or an interpretation that took considerable time to formulate. Losing that material can be more damaging than losing the highlight from which it originated.
Before migration, identify the notes that matter most and determine whether your destination reference manager can import them in a useful form.
If native note transfer is uncertain, consider creating an additional portable copy of important notes. Depending on the source software, this might involve supported note export, exporting the library in a format that includes notes, or preserving important analytical notes in another durable document system.
Zotero allows annotations to be turned into notes, including a note created from all annotations associated with a PDF. Its note system also supports export.
The objective is not to duplicate every scrap of text into several systems. It is to ensure that high-value intellectual work does not depend on one proprietary or application-specific representation that you have not tested outside the original software.
Annotations embedded in PDFs may preserve appearance better than structure
Embedding annotations in a PDF is useful precisely because PDF is widely supported. But portability has levels.
The destination application may display a highlight correctly while failing to import its associated annotation tags. A comment may remain visible but lose a connection to a reference-manager note. An annotation that once linked directly to a note or citation may become an ordinary PDF mark.
This is not necessarily migration failure. It reflects the difference between preserving the annotation itself and preserving the complete application-specific workflow surrounding it.
Before switching, decide what you actually need to preserve:
- the visual highlight;
- the text you highlighted;
- your comment on that highlight;
- annotation colors or categories;
- tags attached to annotations;
- links from annotations to notes;
- page locations;
- the ability to continue editing the annotation in the new software.
The more of that structure you require, the more important testing becomes.
Collections, tags, and notes may not map one-to-one
Reference managers use different organizational models. One application's collection may resemble another application's folder or group, but similar names do not guarantee identical behavior.
Tags are often more portable because they can be represented in several bibliographic formats, but even tags can change depending on import and export behavior. Nested collection structures may flatten. Saved searches may have no equivalent. Application-specific relationships can disappear.
This reinforces the value of a relatively understandable approach to organizing collections, tags, and notes. A system based on a few meaningful structures is usually easier to reconstruct than one dependent on dozens of software-specific features.
Check whether your notes depend on links back to the original library
Some reference-manager notes can contain links that open an annotation in its original PDF or connect text to a specific library item.
Zotero's annotation-to-note workflow, for example, can add links back to the PDF page as well as citation information. Those relationships are useful inside Zotero. A generic note export may preserve the text while not necessarily reproducing every interactive relationship in another application.
When testing migration, do not merely confirm that the note's words are visible. Check whether any relationships you rely on still work.
Existing manuscript citations are a separate migration problem
You may successfully move the reference library and still have manuscripts whose citations remain linked to the old reference manager.
Citation fields inserted by Word plugins or other writing integrations can contain application-specific data. Do not assume that importing the same references into a new manager automatically transfers control of those existing citations.
Zotero, for example, warns that items exported and reimported into a library receive new internal identities and are no longer linked to citations previously inserted into word-processor documents.
If you have active manuscripts, test them separately before uninstalling or abandoning the old citation software. You may decide to finish an existing manuscript with the old reference manager while using the new one for future projects.
Watch Out
Do not delete, uninstall, or irreversibly modify your original reference library as soon as the new application displays the expected number of references. Keep the source library and an appropriate backup until you have verified metadata, attachments, annotations, notes, organization, and any active manuscript citations that matter to you.
Migration is not the same as backup
Exporting a library can be part of a migration plan, but an export should not automatically be treated as a complete backup.
Zotero explicitly states that library export is not a proper backup. Its data directory contains the database holding most library data, including item metadata, notes, and tags, while a storage directory contains managed attachments.
Other reference managers have their own backup procedures. Before a major migration, follow the source application's current backup guidance in addition to creating whatever exports you need for transfer.
The difference is practical: migration prepares data for another system; backup preserves a recoverable state of the original system if the migration goes badly.
Test with difficult items, not just easy ones
A migration test containing ten ordinary journal articles with no attachments tells you very little about whether your real library will survive.
Build a representative sample containing the things most likely to fail:
- a journal article with a DOI and attached PDF;
- a book or book chapter;
- a paper with many annotations;
- a PDF containing comments as well as highlights;
- a source with a substantial research note;
- an item belonging to several collections;
- a heavily tagged item;
- a source with more than one attachment;
- an item already cited in an active manuscript.
Export that sample, import it into the proposed destination, and inspect it manually. Ten carefully chosen records can reveal more about migration quality than successfully importing ten thousand records and looking only at the final count.
The destination reference manager matters as much as the source
Migration is a translation between two systems. The source may export a particular kind of information perfectly, but the destination still needs to understand and import it.
Mendeley Reference Manager, for example, provides integrated PDF comments, highlights, annotations, and Notebook functionality. That establishes what the platform can do with research materials, but it does not by itself establish that every annotation or note structure exported from another reference manager will map into Mendeley's corresponding feature without loss.
The same caution applies when moving in the other direction or migrating to EndNote or another platform. Check the destination's current import documentation for the exact source and export format you intend to use.
If official documentation does not promise preservation of a particular feature, do not assume it will survive merely because both applications have a feature with the same name.