Every form you are responsible for, in one list
Import once and every asset gets an identity that survives renaming, re-foldering and repository migration. Paths and filenames become aliases of a UUID, not the thing itself.
Filenames are not identity
Two files called final_v3 in different folders are not the same form, and the same form moved between folders is not a new one. YakForms assigns a UUID on first sight and keeps every path it has ever been known by, so history survives the reorganisation nobody documented.
Forms, fragments and schemas are different things
An estate of 4,000 files is usually around 900 rendered forms and 3,100 shared parts. Counting them together is what makes migration estimates wrong. The inventory separates them from the start and tells you which of the shared parts are actually load-bearing.
Import does not modify the source
Point YakForms at a repository, an archive or a Git remote. It reads, hashes and records; it never writes back. You can run an assessment against a copy of production without a change-control conversation.
Start with an estate assessment
Point YakForms at a copy of your repository. You get an inventory, a dependency graph and a validation report for the whole estate — before you commit to anything.