When a supplier says that an old footage collection needs migration, ask what will change. Moving the same files to a new storage system is a different operation from converting them into another video format. Both may be reasonable, but they require different explanations and acceptance checks.
A construction business might be replacing an ageing archive drive while also discovering that some old footage is awkward to use in its current editing workflow. Combining those issues into one vaguely described transfer makes it difficult to know what has been preserved, what has been transformed and which originals remain available.
Describe the two operations separately
For a storage move, the intended result may be unchanged files held in a different place. The acceptance questions concern the nominated collection, successful copying, file integrity, access and the handover to the new custodian.
For a format conversion, the resulting file is intentionally different. The questions include what picture, sound and metadata characteristics matter, what the conversion is intended to achieve and how the new version will be compared with its source.
The Digital Preservation Coalition explicitly distinguishes migration between storage systems from migration between file formats. Its storage guidance also emphasises continuing oversight and integrity monitoring. The commercial lesson is to avoid using one reassuring word for two technically different changes.
Keep the reason for conversion visible
Ask why conversion is proposed for this material now. A current production need, a documented compatibility issue or a planned preservation workflow can justify investigation. The mere fact that a file is old does not explain the selected destination format or the value of changing it.
In a hypothetical warehouse-project archive, the team may need only a small number of older clips for a new edit. A bounded conversion of those selected files could answer the immediate production need, while the wider archive remains under a separate preservation plan. Alternatively, the organisation may have a justified collection-wide requirement. The brief should make that choice explicit rather than allowing the size of the job to emerge accidentally.
Agree how source files, converted versions and comparison records will remain distinguishable. Do not let the converted file silently acquire the identity of the original. Later editors need to understand which generation they have received.
Match the evidence to the change
An unchanged-copy check can help establish that a storage move retained the nominated files. The same comparison cannot be expected to produce an identical result after a deliberate format conversion. A new integrity baseline may be needed for the converted version, alongside a separate assessment of its content and intended usability.
Choose representative material for the conversion assessment: the actual kinds of motion, graphics, fine detail and sound present in the collection. The producer or technical specialist should propose a proportionate review method. The buyer should identify the characteristics that matter to future use, not invent encoding settings from a general article.
Keep the decisions about retiring old storage or deleting originals outside the simple statement that a transfer finished. Those actions need the responsible owner's explicit decision under the organisation's retention arrangements. A successful copy or conversion is evidence for that decision, not automatic permission to discard anything.
A clear completion report can then state which files moved unchanged, which were converted, what was checked and what remains unresolved. That makes the next production brief more dependable and prevents a future editor from having to reconstruct the archive's history by guesswork.
Source context
Digital Preservation Coalition guidance on preservation storage supports the narrow technical distinction discussed here. The commissioning example and suggested acceptance questions are original editorial guidance, not a description of a Live Images client or storage service.
Discuss the footage requirement
If retained project footage needs to support a future film, discuss the intended use with Live Images. Agree the material available and the production work required; specialist storage or recovery services should never be assumed.
Prepared with AI assistance for Live Images. Planning guidance is general; suitability and production scope must be agreed for your project.