Migration planning resource
Migrating to cloud surveillance involves more moving parts than simply swapping out a camera system. Skipping steps creates security gaps, budget surprises, and post-migration cleanup that nobody wants. This checklist covers the full migration lifecycle – from pre-migration assessment through post-go-live validation – organized so your team can execute the transition systematically without missing critical details.
Migrating to cloud surveillance involves more moving parts than simply swapping out a camera system. Skipping steps creates security gaps, budget surprises, and post-migration cleanup that nobody wants. This checklist covers the full migration lifecycle – from pre-migration assessment through post-go-live validation – organized so your team can execute the transition systematically without missing critical details.
Inventory first
Confirm camera models, ONVIF support, bandwidth, retention, and access requirements before cutover.
Pilot before rollout
Validate live view, playback, AI search, alerts, and local survivability at a lower-risk site.
Decommission cleanly
Archive required footage, document ownership, and retire legacy hardware without gaps.
Phase 1: Pre-Migration Assessment
Inventory and Documentation
- ?Document all cameras by site: manufacturer, model, resolution, age, mounting location
- ?Confirm ONVIF compliance for all existing IP cameras
- ?Identify analog cameras that require replacement (no ONVIF path)
- ?Document current NVR/DVR hardware: model, age, storage capacity, location
- ?List all current users and their access levels
- ?Document current retention policies by camera/site
- ?Identify any camera integrations (access control, alarm, POS, etc.)
Footage and Data
- ?Identify footage with ongoing legal, insurance, or compliance hold requirements
- ?Export and archive all footage under legal hold to local or long-term storage
- ?Document retention requirements for each site under applicable regulations
- ?Confirm footage export format and storage destination before migration begins
Network Assessment
- ?Measure current internet bandwidth at each site (upload and download)
- ?Identify sites with bandwidth limitations that may need hybrid local recording
- ?Confirm PoE switch availability and capacity for IP cameras at each location
- ?Identify sites with unreliable internet that require local survivability
- ?Document VLAN and firewall requirements for cloud platform communication
Contract and Compliance
- ?Review current VMS or subscription contract terms and termination clauses
- ?Identify renewal dates to time migration to avoid unnecessary renewals
- ?Confirm data ownership terms with new cloud provider
- ?Verify new platform meets applicable compliance requirements (HIPAA, SOC 2, etc.)
- ?Review privacy laws applicable to surveillance in your operating states
Phase 2: Platform Selection and Procurement
- ?Confirm new VMS supports ONVIF cameras in your existing fleet
- ?Verify hybrid architecture capability if local recording survivability is required
- ?Confirm AI analytics capabilities: forensic search, ALPR, people counting, behavioral alerts
- ?Validate multi-site management structure matches your organizational hierarchy
- ?Review pricing model for your camera count and growth trajectory
- ?Confirm data center region and geographic redundancy
- ?Obtain data processing agreement (DPA) from cloud provider
- ?Procure edge gateway appliances for sites requiring local recording
- ?Procure replacement cameras for sites with non-ONVIF legacy hardware
Turn this into a practical surveillance plan
iFovea can review your camera fleet, sites, bandwidth, AI analytics needs, and migration path.
Phase 3: Pilot Site Deployment
- ?Select low-risk pilot site (not your highest-security location for first go-live)
- ?Install edge gateway appliance (if hybrid deployment)
- ?Connect existing ONVIF cameras to new platform
- ?Configure recording schedules and retention policies
- ?Set up motion detection zones and alert rules
- ?Configure AI analytics: forensic search, ALPR, people counting, behavioral alerts
- ?Create user accounts and role-based access permissions
- ?Test live view, playback, and AI search functionality
- ?Test local recording survivability: disconnect internet and confirm local recording continues
- ?Validate footage sync when internet connection is restored
- ?Test mobile app access for relevant users
- ?Confirm alert and notification delivery
- ?Train security staff on new platform interface
- ?Run parallel operation period (old and new system simultaneously at pilot site)
Phase 4: Full Site Rollout
- ?Sequence remaining sites by priority (highest risk or contract expiration first)
- ?Replicate pilot configuration to each new site
- ?Validate recording and AI functionality at each site before decommissioning legacy system
- ?Maintain parallel operation at each site for at least 72 hours post-migration
- ?Decommission legacy NVR/DVR hardware after validation
- ?Update physical security documentation at each site
Phase 5: Post-Migration Validation
- ?Confirm all cameras across all sites are recording and accessible in centralized dashboard
- ?Verify retention policies are applying correctly across all cameras
- ?Run AI forensic search test across all sites to validate cross-site search functionality
- ?Confirm ALPR is capturing and logging plates at designated camera locations
- ?Verify alert and notification rules are functioning correctly
- ?Confirm all user accounts have correct role-based access
- ?Validate mobile access for remote users
- ?Test incident investigation workflow end-to-end
- ?Confirm bandwidth usage is within acceptable parameters at each site
- ?Document new system architecture for IT and security documentation
- ?Schedule periodic system health check cadence
Phase 6: Legacy System Decommission
- ?Confirm all critical footage has been exported and archived
- ?Remove cameras from legacy NVR/DVR systems
- ?Securely wipe NVR/DVR storage before disposal
- ?Cancel legacy subscriptions or maintenance contracts
- ?Dispose of or repurpose NVR/DVR hardware per organizational policy
- ?Close legacy vendor accounts and remove integrations
Common Migration Mistakes to Avoid
- Not archiving footage before migration: Once a legacy system is decommissioned and subscriptions lapse, cloud footage access is lost. Archive everything under legal hold before you start.
- Migrating your highest-security site first: Pilot on a lower-risk location. Work out operational issues before going live at your most critical site.
- Underestimating bandwidth requirements: Assess upload bandwidth at each site before go-live. Configure cloud sync to avoid saturation of limited WAN connections.
- Not testing local survivability: If you’re using hybrid local recording, physically disconnect internet and confirm recording continues before decommissioning legacy hardware.
- Skipping the parallel operation period: Running new and legacy systems simultaneously for 48-72 hours catches issues before you’re fully committed.
Get Your Migration Assessment
Ifovea’s onboarding team provides a structured migration assessment for organizations planning the transition from legacy surveillance, Verkada, Rhombus, Genetec, or other platforms. The assessment covers camera compatibility, network requirements, phasing recommendations, and total cost of ownership comparison.
Turn the checklist into a migration plan
Use these deeper planning guides to validate camera reuse, ONVIF support, hybrid architecture, and multi-site rollout before changing platforms.
Frequently asked questions
What should be checked before migration?
Camera model, ONVIF support, network bandwidth, retention policy, user permissions, legal hold footage, and legacy contract dates should be reviewed first.
Should every location migrate at once?
Usually no. A pilot site helps validate configuration, recording, alerts, AI search, and user workflows before a broader rollout.
Can hybrid cloud reduce risk?
Hybrid cloud can preserve local recording during internet interruptions while still giving teams cloud access and centralized management.
What does iFovea review in an assessment?
iFovea can review camera compatibility, deployment architecture, network readiness, retention needs, and total cost considerations.
Related resources
Continue comparing options, planning migration, and estimating the right cloud surveillance architecture.
Ready to plan the next step?
iFovea can review your camera fleet, sites, bandwidth, AI analytics needs, and migration path.
