On this page
Start with the inherited Word draft, not the library export
The first question is which citation tool created the active fields. Mendeley Reference Manager is the library application; Mendeley Cite is the Word add-in. The older Mendeley Desktop application used a different citation plugin. A familiar-looking bibliography does not tell you which document structure remains underneath it.
Zotero’s current importer documentation explicitly distinguishes these structures. Its Word and LibreOffice plugins can read legacy Mendeley Desktop citations and relink them to imported Mendeley items. Citations created with Mendeley Cite are not readable by Zotero. That is a document-level boundary, not a statement that the reference library cannot be imported.
Elsevier documents converting legacy-plugin citations to Cite, but warns that the conversion is irreversible and recommends a duplicate first. Coauthors then need Cite; the legacy plugin cannot add citations to the converted document. Preserve the working original and agree the team’s destination before changing the fields. No Word document or library was converted for this source-based comparison.
Compare four starting records
These cells describe documented routes rather than a formatting, speed or reliability ranking. Choose the row that matches the document you actually have. An unresolved route should remain unresolved instead of being filled with an assumed export-and-import shortcut.
| Starting record | Moving to Zotero | Using Mendeley Cite |
|---|---|---|
| A Word draft with legacy Mendeley Desktop fields | Use the documented Mendeley import and Desktop-field relinking route on a retained copy; inspect the imported records and citations. This is not a promise for arbitrary interchange files or every old software version. [1] | Duplicate first, then use the documented legacy-to-Cite conversion only if the team chooses Cite. Conversion is irreversible and coauthors need the add-in. [2] |
| A Word draft already using Mendeley Cite | The current Zotero importer says Cite fields are not readable. Importing references does not establish an automatic editable-document conversion. [1] | Continue in the chosen Word/Cite workflow with the intended library and coauthors. Do not expect the old Desktop plugin to edit converted citations. [2] |
| A Mendeley library and its attached files | Direct online import requires synced data/files. Group libraries need a separate copy-to-personal-library step before import. [1] | Cite loads reference metadata from the cloud library; that library availability is separate from converting fields already in the draft. [2] |
| A team that must move between writing programs | Zotero documents explicit conversion between Word, LibreOffice and Google Docs on a copy, followed by Refresh in the destination. A format change alone is insufficient. [3] | The migration guide scopes Cite to Microsoft Word, including a Word Online route. It does not support LibreOffice or Google Docs. Check institutional add-in access. [2] |
Try the decision before converting either draft
Constructed decision case: Draft A was created with the legacy Mendeley Desktop plugin; Draft B uses Mendeley Cite. Both refer to the same correctly identified source, but no publication or research finding is invented here. A coauthor wants to continue editing active citations in LibreOffice using Zotero.
Try first: assess this proposed plan: “Convert both drafts to Cite, export the library as RIS, then import it into Zotero so both documents relink.” Identify the unsupported steps. List which untouched documents and library records you would retain before attempting any permitted migration.
Next, choose one documented route for Draft A and explain what remains unresolved for Draft B. State why finding the source in a new library does not prove that the existing citation field points to it. This is an original reasoning exercise, not an observed conversion, a product trial or evidence that one manager performs better.
Compare the proposed conversion plan with the documented boundaries
The plan is unsupported. Draft A has a documented Zotero route for legacy Desktop fields after the appropriate Mendeley import. Converting A to Cite first is irreversible and replaces that starting condition with fields Zotero explicitly cannot read. Draft B already has that unreadable Cite structure. A generic RIS import supplies records, not proof of field relinking. Keep untouched draft copies, use the documented online import and Desktop relinking where applicable, and make a separate document-level decision for B. No Cite-to-Desktop reverse conversion or automatic Cite-to-Zotero conversion is established here.
Retain references, annotated PDFs and authored notes separately
Mendeley’s Reference Manager export guide describes File > Export All as BibTeX, EndNote XML or RIS in the installed application and says only reference information is exported. It does not describe a full PDF, annotation or Word-field recovery package. The guide is undated; check current controls if the application differs.
An annotated PDF has a separate Mendeley route: Info panel, Files, the file menu, then Export PDF with annotations. In Zotero, built-in annotations are stored in the database rather than automatically embedded in the original PDF. Export PDF or the reader’s Save As creates an annotated copy. Copying the original attachment alone can therefore omit the visible reading annotations.
Keep your authored interpretation and source locator deliberately, too. A bibliography record, an embedded PDF highlight and a prose note serve different purposes. The direct Zotero Mendeley importer is a different route from a generic RIS transfer; inspect the actual destination records, files and notes before treating any migration as complete. None of these files determines whether a source supports your claim.
Rebuild group access without confusing separate records
Zotero’s importer cannot directly import Mendeley group libraries. Its documented workaround is to copy needed group items to a collection in the personal Mendeley library before importing, then create a Zotero group and add the imported items. That moves records through another library; it does not establish preservation of the original group’s membership or permissions.
Zotero group libraries are separate from My Library. Dragging an item into a group creates a separate copy, so later personal-record corrections are not automatically a shared-record correction. Library reading, library editing and file editing are different settings, and group file storage uses the owner’s quota. Public open-membership groups cannot share files.
The Mendeley guide documents invite-only private groups for references, PDFs and shared annotations, marking group PDFs as Shared in the reader. It does not establish an equivalent current owner-role matrix or a live personal-to-group update rule. Choose who maintains the destination record and verify the actual group settings rather than inventing symmetry between the products.
Separate offline availability from recovery of an earlier state
Zotero stores data locally by default, with separate data and attachment sync. A visible library entry on another device is not proof that its PDF has downloaded. Its backup guidance also distinguishes the latest server state from a version history: an unwanted change can synchronize, so sync does not replace an independent incremental backup.
For a local Zotero backup, follow the official closed-application data-directory procedure and check whether on-demand attachments actually exist locally. Export and reimport are not a proper backup: they can break links to citations in working documents. Avoid turning a migration exercise into a replacement for your only recoverable library.
Mendeley documents offline reading and annotation for downloaded Reference Manager files, followed by sync after reconnection. Cite needs internet to launch and load metadata, then can continue offline within that open session; reopening needs connectivity. The cited documentation does not establish a complete Mendeley library version-history restore. Verify that recovery requirement separately; this is not evidence that the feature is absent.
Agree the next collaborator action before migrating
Write down the existing citation tool, required word processor, intended maintained library and who can use the destination plugin. Retain untouched documents and inspect a disposable copy through the documented route before changing an active manuscript near a deadline. Check one editable citation, its locator and bibliography entry after any conversion you actually perform.
If the destination is Zotero, distinguish legacy Desktop-field relinking from importing a library and from switching word processors. If it is Cite, confirm every coauthor’s add-in access before converting. These are proposed checks, not completed software tests, and no universal compatibility or lossless-migration guarantee is made.
Optional Mendeley AI is a separate reading and entitlement decision covered in its current profile. It does not make Cite fields readable by Zotero or grant additional article access. For a choice centered on Docs and shared-library ownership rather than inherited Mendeley fields, use the distinct Zotero vs Paperpile comparison.
Questions about this topic
Can Zotero edit citations made with Mendeley Cite?
The current official Zotero importer documentation says Mendeley Cite citations are not readable. Importing the reference library does not establish an automatic conversion of those document fields.
Can Zotero relink older Mendeley Desktop citations?
Zotero documents reading Desktop-plugin citations in Word and LibreOffice and relinking them to imported Mendeley items through its Mendeley import route. This does not promise relinking from every arbitrary RIS file or historical software version.
Can I reverse a legacy-to-Cite document conversion?
Elsevier says the conversion is not reversible and recommends retaining a duplicate first. No reverse-conversion route is established here. Preserve an untouched working original before changing the citation system.
Does importing my library preserve group access and annotations?
Do not assume that from a successful record import. Zotero cannot import Mendeley group libraries directly; its workaround moves items through the personal library. Recreate the intended group and check files, annotations and permissions separately.
Is a reference export a full backup?
No complete recovery guarantee follows from a reference export. Mendeley’s export guide describes reference information only. Zotero explicitly warns that export/reimport is not a proper backup and can break existing document-citation links.
Can Mendeley Cite and Zotero both work offline in the same way?
No. Zotero data is local by default, with downloaded-file availability checked separately. Mendeley Cite needs internet to launch and load metadata; it can then continue offline only within that session. Downloaded Reference Manager PDFs have a separate offline-reading workflow.
Sources and editorial notes
The supporting reading below informs our editorial guidance. Exercises and scenarios illustrate a method; they do not report a completed product test or measured learning outcome. Read our editorial policy or send a correction with a supporting source to info@ai-essay.com.
- Zotero: Mendeley online import and Desktop-versus-Cite citation support
- Elsevier: legacy migration, irreversible Cite conversion, coauthors and offline sessions
- Zotero: explicit Word, LibreOffice and Google Docs transfer procedure
- Mendeley: Reference Manager export formats and reference-only scope
- Elsevier: separate annotated PDF export
- Zotero: database annotations and embedded-PDF export
- Zotero: separate group records, permissions and file storage
- Mendeley: private groups and shared PDFs/annotations
- Zotero: data-directory backup, latest-state sync and lost links on reimport
- Zotero: local data and separate attachment sync
- Elsevier: Mendeley AI entitlement is separate from additional article reading rights