County Land and Deed Record Microfilm Conversion

Collection conversion is different from record lookup

This page is for an organization that controls, or is authorized to manage, a land-record microfilm collection. It helps that team scope capture, indexing, review, and delivery decisions for deeds, record books, indexes, plats, maps, or related material.

It does not search a specific property, provide copies to residents, determine ownership, interpret an instrument, or establish release rights. Public land-record research follows the rules and access channels of the responsible office. For example, Fairfax County describes its land-record materials as public documents that researchers must investigate themselves, even though its collection was converted from microfilm and books to digital images.

Technical references:[1]

Inventory the record series before defining capture

A practical inventory separates the collection into workable series rather than treating every reel alike. Teams can note the carrier, reel or container identifier, date span, record type, visible book or volume sequence, labels, targets, and any observable gaps or duplicate material. That inventory gives the project a shared vocabulary before samples are selected.

It also identifies where a series changes. Deed books may use book and page references, while grantor-grantee indexes, plats, map volumes, or loose instruments may use different identifiers. A collection-specific inventory keeps those distinctions available for the field map and sample review instead of assuming one indexing pattern fits every image.

Design retrieval fields from the source record

Retrieval design starts with identifiers that are present in the source or in an approved register. The table shows examples, not a universal land-record schema. The organization decides which fields are appropriate, how they are normalized, which identifiers are optional, and how a record stays traceable to its original reel, book, frame, or other source reference.

Technical references:[1]

Treat plats and maps as their own material decision

Plats, maps, and record drawings can have different image layouts and retrieval references than textual deed pages. Their inclusion should be established during inventory, along with the available labels, volume relationships, map or plat identifiers, and the level of detail the organization needs reviewers to examine in a representative sample.

Archival finding aids also show that record plats, maps, and engineering materials may be held on microfilm. That context supports keeping map-like material visible in the project plan rather than silently grouping it with book pages. Output remains raster imagery; no editable CAD conversion is implied.

Technical references:[2]

Validate representative material before scaling

A representative sample can cover more than one record series, date range, condition pattern, and label style. It is the point to review image orientation, frame boundaries, book or page relationships, index-field availability, and the way exceptions will be recorded. Sample review is also where the project team can confirm whether supplied registers or existing indexes are usable as source references.

If text recognition is considered, it should be evaluated on representative material and treated as a project option rather than a guarantee. The approved field map, source-reference approach, exception handling, and review criteria should be settled from the sample results before wider production is planned.

Prepare delivery around the approved workflow

Delivery planning can define stable record identifiers, selected image derivatives, a data dictionary, source-reference fields, and an exception list. The receiving organization determines its own access, release, retention, and repository requirements. A planned handoff can be tested against the destination's approved specifications without assuming a native integration or automatic repository load.

Link the project plan to the existing microfilm service for material intake, the indexing service for field-design discussion, and the delivery-planning guide for a vendor-neutral manifest and mapping conversation. Government procurement requirements remain separate and organization-specific.

Common questions