Video management system migration has two separate jobs: move live operations and preserve useful access to historical recordings. Plan both before retiring the old system. An open camera interface does not automatically transfer recording indexes, event tags, user rights or an entire archive.
Table of Contents
Inventory what must survive
A migration inventory should include cameras, streams, recordings, event indexes, alarm rules, maps, user roles and external integrations. Some items can be transferred; others need recreation or a retained legacy service.
ONVIF Profile G covers edge recording and retrieval functions. It is useful for assessing an interface, but its scope should not be expanded into a promise of complete database portability between video management systems.
The PSIM and VMS comparison separates operational roles. Migration adds a lifecycle question: which history and meaning must remain available when the platform changes?
Choose a historical-access strategy
| Strategy | Useful when | Main cost or risk to resolve |
|---|---|---|
| Full supported migration | Importer preserves required records and metadata | Conversion duration, validation and storage |
| Selected export | A bounded set of recordings must be retained | Selection completeness and future search |
| Read-only legacy archive | History can remain in the old system temporarily | Security, licenses, hardware and access support |
| Parallel operation | Cutover needs overlap | Duplicate administration and conflicting rules |
| Retention-led retirement | Old data expires under an approved schedule | Accurate retention and hold handling |
The choice should follow the required retrieval tasks. A playable video file can still be difficult to use if its camera identity, time reference or associated event has been lost.
A practical mapping table links the old camera or stream ID, the new ID, the site and zone, the recording schedule and the event types that must survive. Keep the mapping after cutover; it becomes the key for explaining why an old incident appears under a different name in the new system.
Estimate the transfer window
Suppose an illustrative archive contains 20 TB of decimal data and the sustained transfer rate is 100 MB/s. The ideal copy time is approximately 200,000 seconds, or 55.6 hours.
That is a lower-bound transfer calculation. It excludes indexing, verification, protocol overhead, throttling, competing workloads and retries. If the new platform also records live video, transfer activity must fit within its storage and network capacity.
The video storage calculation guide distinguishes capacity from throughput. A migration can have enough destination space and still overload the live recording path.
Prove retrieval after the move
Build a sample set spanning cameras, dates, recording modes and event types. Include a known incident or test event whose expected files and metadata are already documented. Retrieve it using the new workflow and compare camera identity, timestamps, duration and associated context.
Use the evidence export guide for preservation and recipient playback. Archive migration is broader: users also need to find the right recording later. An export that plays correctly does not by itself verify search indexes or access permissions.
For an integrated security platform in a critical infrastructure environment, include downstream alarm and incident systems in the cutover. A camera can stream successfully while its events still point to an obsolete identifier.
Record the mapping, retention strategy, rollback conditions and retirement responsibilities with the technical resources. Keep the old service available only for a defined purpose and period, with controlled access. Decommissioning should be the final verified step—not the event that reveals missing history.
FAQs
Does ONVIF conformance guarantee complete archive migration?
No. Profile G addresses recording and retrieval capabilities within its scope. It does not establish that one vendor can import another vendor's entire database, indexes and application metadata.
Must every historical recording be copied to the new system?
Not always. A controlled period of read-only access to the old archive may be appropriate if retention, security and retrieval requirements are satisfied. Compare that with export and import options.
When can the old recorder be decommissioned?
After the approved retention and migration plan is satisfied, required recordings remain retrievable and the new operational workflow has passed its acceptance checks. Keep an accountable decommissioning record.
What should happen to user roles and audit logs?
Map roles to the new permission model, migrate or recreate audit history where required, and test that separated duties remain separated. A recording that plays correctly can still be inaccessible to the wrong—or right—user.
