Imagine returning from an archive with three photographs of a letter and a fourth of its envelope. The filenames record the order in which the camera fired. The useful research object is the correspondence: pages, address, postmark, and the collection reference that will let someone find it again. Tropy, an open-source application for organizing research photographs, provides a place to assemble that object.[1]

Adopting it involves two decisions that are easy to conflate: how photographs belong together, and where their files will live. A successful move from folders into Tropy preserves both the document's identity and a working route to its images. The following is a proposed migration rehearsal for an individual researcher or a small team that can take turns editing.

Give the document its own identity

Begin with one recognizable archival folder. Preserve the original files and a separate backup, then import a small working batch. Include the awkward material: a document spanning several frames, an envelope, and a close-up whose relationship to a page might be forgotten.

Tropy distinguishes an item from its photographs. Multiple images can belong to one item, allowing the letter and its envelope to be described together. Rice University's library guide explains the corresponding metadata distinction: camera information describes the photograph, while item fields describe the document in it. A photograph's capture date and a letter's written date answer different questions.[3]

Establish the grouping before investing heavily in individual descriptions. When fields conflict, dragging one item onto another retains the target item's metadata; merging selected items through the menu retains the top item's metadata. Rice's guide explains these two routes. Check the surviving record after a merge.[3] For our imagined letter, verify the page sequence and keep the envelope recognizable as an envelope.

Then fill in the archive, collection, box, and folder. Shared fields can be entered across selected items in one operation.[3] Choose a batch whose provenance is actually shared: a camera folder containing an entire day's work may span several archival boxes. A topical tag such as “housing” can help later analysis, but it cannot supply a missing collection reference.

Decide who manages the photographs

Tropy's Standard project type, introduced in version 1.13 in March 2023, copies imported images into a managed .tropy folder on Windows and Linux, or a bundle on macOS. An Advanced .tpy project instead links to photographs at their existing locations. Those links may be absolute or relative paths.[4]

For a researcher starting a manageable collection on one computer, Standard offers a straightforward unit to carry between machines. Budget disk space for the imported copies as well as the retained originals. Advanced makes sense when there is an established image directory to preserve, or photographs must remain across several drives. That flexibility gives the researcher responsibility for keeping paths resolvable.[4][5]

The interior of a Standard project explains the practical difference. It contains project.tpy and an assets directory; Tropy copies and renames imported photos into that directory. A maintainer explicitly warns against treating the managed assets folder as a place to drop incoming files manually. Import through Tropy; if using a watch folder, keep the incoming folder outside the managed assets directory.[5]

Copying only the inner database therefore leaves the photographs behind. When transferring a Standard project, carry the entire outer .tropy folder or bundle. If the project uses a custom metadata template, export and install that template separately on the receiving computer.[4][5]

Try the move before expanding the collection

The rehearsal should have a written expectation. Record which photographs went into the batch and which document each belongs to. After grouping, the number of items will be smaller than the number of photographs; matching an item count to the original file count would be the wrong completeness test.

Open every photograph in this small sample. Check that the last page is present, that the envelope has stayed with the right letter, and that fine handwriting remains readable at a useful zoom. Add a short transcription and an identifying tag. Put the item in a named list, so the trial also tests organization beyond the image files.

Now quit Tropy and copy the complete Standard project to another computer, using the same Tropy version for this first trial. Leave the original source drive disconnected from the receiving machine. Open the copied project and repeat the checks: full images, page sequence, archival identifiers, transcription, tag, and list membership.

This is a recommended acceptance test, not a claim that every collection has been tested. Its purpose is concrete: the receiving computer should recover the research object from the delivered project. Keep the untouched source photographs and the first successful project backup while bringing in further batches.

Distinguish an exchange package from the working project

Tropy's Archive plugin packages selected items into a ZIP containing their metadata and photo files. That is useful when a colleague needs a particular set of documents.[6] Give the recipient an explanation of what was selected and check the imported result together.

Whole-project continuity requires a broader test. In a February 2026 support exchange about Tropy 1.17, a maintainer explained that JSON data import did not restore lists. The discussion distinguishes upgrading the original project database from exporting items and importing them into a new project.[7] An export can carry valuable material while leaving some of its organization outside the transfer. Preserve the native project when that organization matters.

A shared folder introduces another boundary. The documented collaboration workflow requires users to avoid simultaneous editing, wait for synchronization before opening, and close the project and finish syncing before handing it over. Concurrent changes can produce database conflicts.[8] A small team with an explicit handoff can work within that constraint. A team needing several researchers to edit the same collection at once should resolve that requirement before moving its main archive into this arrangement.

The destination is reached when another working copy opens the whole letter: its pages, envelope, description, and place in the research. The camera filenames can remain ordinary. The relationships surrounding them are what make the collection usable.

Sources

1. Tropy, official source repository — research-photo management, installation, and open-source project.
2. Library of Congress, photograph of book digitization with wedge supports — image published in “Review of Imaging Equipment,” Preservation Actions for Collection Digitization.
3. Rice University, Fondren Library, “Add Metadata and Notes” — independent library guidance on item/photo metadata, bulk description, and merging photographs; updated June 2026.
4. Anita Lucchesi and Douglas McRae, “New Project Types in Tropy 1.13,” March 31, 2023 — Standard and Advanced storage models and custom-template transfer.
5. Tropy support forum, “‘Watch folder’ not always imported,” May 2024 — maintainer explanations of project.tpy, managed assets, image paths, and incoming folders.
6. Tropy Archive Plugin, official repository — ZIP export of selected items with metadata and photo files.
7. Tropy support forum, “Migration problem: 1.9 to 1.17,” February 2026 — maintainer distinction between project migration and JSON import, including list limitations.
8. Tropy support forum, “Collaborative project?” — maintainer guidance on sequential editing, synchronization, and database conflicts, September 2024–January 2025.