FAQ
Find answers to commonly asked questions for this workflow
If the new site has a newer XProtect version, how does a recorder on an older version connect to the newer site?
The migration workflow in XPort monitors versions at both the source and destination, prompting the user to update the XProtect recorder version at the right time during the migration process.
What product flavors and source versions are supported?
All C-code flavors and versions are supported.
What product flavors and target versions are supported?
All C-code product versions and flavors are supported. It is assumed that the target is at least the same version or more recent than the source version.
Is footage lost during migration? What is the duration? How do I fix it?
Footage is lost during media database reconfiguration and rebuilding because the recorder service must be shut down to facilitate this process. The length of this loss depends on the size of the database. One approach to mitigate this is to utilize edge recording and enable the 'Restore from the Edge' feature in XProtect.
What types of Users are migrated?
XPort migrates XProtect Basic and Active Directory users. Machine users are not migrated because XPort can't read credentials.
Is migration reversible?
To reverse migration on the source, rerun XPort after swapping the source and destination. While the supported configuration content is restored, the recorder is reattached to the original site, and media content is rehydrated; the state of the original source before migration and after reverse migration is not exactly the same.
Do you support the migration of third-party integrations, such as Analytics, PSIM, and access control?
As of June 2025, we do not support this yet.
Last updated