Detection must be version-aware
A filename is not enough to identify a legacy database safely. GeneaProof inspects signatures and schema details so an adapter can be selected for the detected version, while unsupported or ambiguous variants stop before research data is written.
Unknown fields still have research value
A field that has no native GeneaProof equivalent should not disappear. Original records can be preserved for review, and researchers can define structured custom record types until a widely useful field is assessed for the standard library.
A result should be auditable
The final report should reconcile input counts with native, preserved, skipped and blocked records. That evidence lets a researcher verify the migration, correct mappings and keep working without pretending that every third-party format means exactly the same thing.