Migrating from Blue Iris to cloud VMS typically takes less than a day for most deployments. The process is simpler than it sounds — most Blue Iris cameras are ONVIF or RTSP compatible, meaning they can connect directly to a cloud VMS platform without replacement. This guide walks through every step.
Before You Start: Migration Eligibility Check
Likely straightforward migration if:
- Cameras were added to Blue Iris via ONVIF or RTSP
- Camera brands: Axis, Hanwha, Uniview, Vivotek, Hikvision, Dahua, Amcrest
- Cameras are 1080p or higher
- Site has at least 5 Mbps upload bandwidth
Check compatibility if:
- Cameras use proprietary protocols only (some older models)
- Cameras are very old (pre-2012)
- Site upload bandwidth <3 Mbps
- NDAA compliance is a requirement (Hikvision/Dahua cameras)
Step 1: Camera Compatibility Verification
The first step is confirming your cameras support ONVIF or RTSP — the protocols that allow them to connect to cloud VMS platforms.
Finding RTSP Credentials in Blue Iris
In Blue Iris, open the camera settings for each camera and look at the “Video” tab. The RTSP address format shown there tells you the stream URL. If Blue Iris has been receiving a stream successfully, the camera supports RTSP — it’s already connected.
ONVIF Compatibility Check
Most commercial IP cameras manufactured after 2012 are ONVIF-compliant. If your cameras were added to Blue Iris via “ONVIF profile” rather than a model-specific driver, they’re ONVIF compatible. You can verify via the ONVIF conformant products list or the iFovea camera compatibility guide.
Document All Camera Details
Before proceeding, document for each camera:
- Camera IP address and admin credentials
- RTSP stream URL (from Blue Iris settings)
- Camera model and firmware version
- Physical location and mounting angle
- Recording schedule and motion zones configured in Blue Iris
Step 2: Network Preparation
Verify these network prerequisites before deploying the cloud VMS gateway:
| Network Requirement | Minimum | Recommended |
|---|---|---|
| Upload bandwidth (ISP) | 3 Mbps per 5 cameras (event-only upload) | 10+ Mbps for smooth live view remote access |
| LAN switch | 100 Mbps switch port for gateway | Gigabit switch |
| Camera network access | Gateway must be able to reach camera IPs | Cameras and gateway on same VLAN |
| Outbound internet | Outbound HTTPS (443) allowed from gateway | No firewall blocking outbound 443 from gateway IP |
Step 3: Deploy the iFovea Gateway
The iFovea Gateway is a small appliance that connects to the same network as your cameras, bridges camera streams to the cloud, and handles local edge recording for internet outage continuity.
Physical deployment:
- Connect the gateway to a switch port on the same network as your cameras (or a VLAN that can reach them)
- Connect the gateway to internet-accessible LAN (typically the same switch that has internet routing)
- Power on the gateway — it contacts the cloud platform automatically and registers itself
- In the iFovea cloud dashboard, the gateway will appear as “Online” within a few minutes
Step 4: Add Cameras to the Cloud Platform
With the gateway online, cameras are added via auto-discovery or manual RTSP URL entry:
Auto-Discovery (ONVIF)
Click “Discover Cameras” in the iFovea dashboard. The gateway scans the local network for ONVIF cameras and presents a list. For each camera found, enter the ONVIF admin credentials — the same username/password you use to log into the camera’s admin web interface. The platform connects and begins streaming.
Manual RTSP URL Entry
For cameras that don’t respond to ONVIF discovery, enter the RTSP stream URL directly — the same URL that Blue Iris uses to connect to the camera. Common RTSP URL formats:
// Hikvision
rtsp://admin:password@[camera-ip]:554/Streaming/Channels/101
// Dahua
rtsp://admin:password@[camera-ip]:554/cam/realmonitor?channel=1&subtype=0
// Axis
rtsp://root:password@[camera-ip]/axis-media/media.amp
// Hanwha
rtsp://admin:password@[camera-ip]:554/profile2/media.smp
Step 5: Configure Recording, AI Analytics, and Access
Once cameras are connected, configure the platform to match (or improve upon) your Blue Iris settings:
- Recording schedules — continuous, motion-triggered, or time-based schedules per camera
- Cloud retention period — set how many days of footage to retain in cloud storage
- AI analytics — enable people counting, object detection, or ALPR per camera (not available in Blue Iris without third-party plugins)
- User accounts — create user accounts with appropriate roles (admin, operator, viewer) — far more granular than Blue Iris user management
- Alert notifications — configure email/SMS/webhook alerts for AI detection events
- Camera names and zones — label cameras and define detection zones
Step 6: Parallel Operation and Transition Period
Keep the Blue Iris PC running in parallel during the transition. Cameras that support multiple simultaneous RTSP connections will stream to both Blue Iris and the cloud gateway simultaneously — you can verify the cloud platform is recording correctly before decommissioning Blue Iris.
The Blue Iris historical footage cannot be migrated to cloud storage. Keep the Blue Iris PC running in read-only mode for as long as you need access to historical footage (typically 30–90 days). After that period, the PC can be shut down or repurposed.
What You Gain After Migration
Reliable Remote Access
Browser or mobile app — no VPN, no DDNS, no port forwarding
Native AI Analytics
People counting, ALPR, object detection — no GPU hardware needed
No Server to Maintain
The Blue Iris PC can be retired — no more Windows server to patch
Multi-Site Dashboard
If you have additional sites, all managed from one login
Cloud Retention
Footage stored in cloud — no hard drive failure risk
RBAC + Audit Trail
Full access logging — who viewed what footage, when
Ready to Start the Migration?
Our team can walk through your Blue Iris camera inventory and confirm compatibility before you commit. Most migrations complete in under a day.
FAQ
Can I migrate Blue Iris historical footage to iFovea?
Not directly — cloud VMS platforms store footage recorded through their own gateway; they cannot import historical footage from a Blue Iris hard drive. Keep the Blue Iris PC running in read-only mode for as long as you need access to historical footage.
Will all my cameras work with iFovea?
If your cameras currently work with Blue Iris via ONVIF or RTSP, they will very likely work with iFovea. The same RTSP URLs Blue Iris uses can be added directly. Some very old or proprietary-protocol cameras may not be compatible — these cases are identified during the compatibility assessment.
Do I need to reconfigure my cameras during the migration?
Camera hardware configuration (IP address, codec settings) does not need to change. You’re simply redirecting where the stream goes — from the Blue Iris PC to the iFovea gateway. Cameras remain on the same network with the same settings.
