Import a Rayyan export into Lumina: citations and migration limits
Move Rayyan citation exports into Lumina using RIS. Check what transfers and preserve decisions, notes and the original audit log separately.
Quick answer
Export your references from Rayyan, extract the articles RIS file from the export archive, and import it into Lumina. Citation metadata transfers; Rayyan decisions, labels, exclusion reasons and reviewer histories are not automatically recreated as Lumina screening decisions.
Export and retain the complete archive
Use Rayyan’s export workflow for the stage and articles you want to move. Retain the downloaded archive, articles file and customizations log before making changes. Check the selected scope and number of references.
Rayyan documents decisions, labels, exclusion reasons and user notes in its article exports and a separate action log. These fields are valuable for your records even when the destination importer does not use them.
Import citations into Lumina
Extract the archive first; upload the articles .ris file rather than the zip or action log. Create a review with the intended eligibility criteria and test a small selection before importing the remainder.
Lumina normalizes title, abstract, authors, publication date, journal, DOI and a source identifier when those fields are present. It does not replay Rayyan’s reviewer decisions or attach Rayyan customizations as native notes. PDFs and reviewer accounts do not transfer through RIS.
Check migration completeness
Compare source count with imported count and any duplicate removals. Inspect title, abstract and DOI on a sample of records. Keep a separate mapping and archive for earlier decisions if you must preserve a completed review.
The sample download is a synthetic RIS with Rayyan-style note tags, not a real Rayyan export. The import benchmark demonstrates that its citation parses while the notes are not mapped into decisions. Do not infer full migration support from a successful upload.
Restart independent review deliberately
If you need independent dual screening in Lumina, invite the second human reviewer into Duo or Team and agree how earlier work will be handled. Pixel-Bot supplies advisory recommendations and does not substitute for an independent human reviewer.
| Data | Citation import | What to retain separately |
|---|---|---|
| Title and abstract | Mapped when present | Original articles export |
| DOI and authors | Mapped when present | Raw bibliographic identifiers |
| Reviewer decisions | Not recreated | Articles export and action log |
| Labels and exclusion reasons | Not recreated | Original archive |
| Reviewer notes and histories | Not recreated | Original archive and customizations log |
| Attached PDFs | Not transferred by RIS | Original files and access permissions |
Download and inspect the examples
These CC0 examples are synthetic. Their identifiers do not refer to real publications. Use them to check an import, not as research evidence.
Read the benchmark method and limitations →Sources and editorial review
Maintained by the Lumina Editorial Team. Product mappings and examples were checked against Lumina’s implementation on October 7, 2026. External interfaces can change; consult the primary documentation below. This is an independent product guide, without a claim of independent scientific review.
Suggest a correctionInspect the screening workflow
Explore the public demo with sample papers. AI recommendations remain advisory; reviewers make the screening decisions.