iFovea cloud VMS and AI video analytics platform logo

Migrate Blue Iris to Cloud VMS: Step-by-Step Guide

Migration Guide

Migrate from Blue Iris to Cloud VMS

A step-by-step migration guide. Most Blue Iris deployments migrate in under a day — existing cameras typically connect without replacement.

Blue Iris to Cloud VMS Migration — cloud VMS operations visual
Blue Iris to Cloud VMS Migration — cloud VMS operations visual

✅ 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
  • Cameras are very old (pre-2012)
  • Site upload bandwidth <3 Mbps
  • NDAA compliance is required (Hikvision/Dahua)

The 5-Step Migration Process

1

Camera Compatibility Verification

Open each camera in Blue Iris settings → Video tab → check the RTSP address. If Blue Iris has been receiving a stream successfully, the camera supports RTSP. Most commercial cameras added to Blue Iris since 2012 also support ONVIF — check the ONVIF conformant products list to verify.

2

Network Preparation

Minimum

3 Mbps upload per 5 cameras, 100 Mbps switch port for gateway

Recommended

10+ Mbps upload for smooth remote live viewing, gigabit switch

3

Deploy the iFovea Gateway

The iFovea Gateway connects to the same switch as your cameras. Power on → it contacts the cloud platform automatically and registers itself. The gateway appears as “Online” in your cloud dashboard within a few minutes.

4

Add Cameras via Auto-Discovery or RTSP URL

Click “Discover Cameras” — the gateway scans for ONVIF cameras and presents a list. Or add cameras manually using the RTSP URL from Blue Iris. Common formats:

// Hikvision

rtsp://admin:pass@[ip]:554/Streaming/Channels/101

// Dahua

rtsp://admin:pass@[ip]:554/cam/realmonitor?channel=1&subtype=0

// Axis

rtsp://root:pass@[ip]/axis-media/media.amp

5

Configure & Transition

Set recording schedules, AI analytics, user access roles, and alert notifications in the cloud dashboard. Run Blue Iris in parallel during transition — cameras supporting multiple RTSP connections stream to both simultaneously. After verifying the cloud platform meets your needs, retire the Blue Iris PC. Keep it in read-only mode for 30–90 days for historical footage access.

What You Gain After Migration

📱

Reliable Remote Access

Browser or mobile — no VPN, no DDNS, no port forwarding

🤖

Native AI Analytics

People counting, ALPR, AI search — no GPU needed

🖥️

No Server to Maintain

The Blue Iris PC can be retired permanently

☁️

Cloud Retention

No hard drive failure risk — footage stored in cloud

🏢

Multi-Site Dashboard

All sites managed from one login

📋

RBAC + Audit Trail

Full access logging — who viewed what, when

Ready to Start the Migration?

Our team will walk through your Blue Iris camera inventory and confirm compatibility before you commit. Most migrations complete in under a day.

Schedule a Migration Assessment

FAQ

QCan I migrate Blue Iris historical footage to iFovea?

Not directly — cloud VMS platforms store footage recorded through their own gateway and cannot import historical footage from a Blue Iris hard drive. Keep the Blue Iris PC running in read-only mode for 30–90 days for historical footage access, then retire it.

QDo I need to reconfigure cameras during the migration?

No — camera hardware configuration (IP address, codec settings) does not need to change. You’re redirecting where the stream goes — from the Blue Iris PC to the iFovea gateway. Cameras remain on the same network with the same settings.

QWill 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. Some very old or proprietary-protocol cameras may not be compatible — these are identified during the compatibility assessment before you commit.

Related Resources

The True Cost of Running Blue Iris: What “Free” Actually Costs

Migration from Blue Iris to cloud VMS typically takes 1–2 days and requires no new cameras.

The software license is the smallest item in your total cost. The real costs are infrastructure: the server that runs it, the electricity that powers it, the storage that holds footage, the IT time that keeps it running, and the remote access tools required to view it from anywhere. Here is what 10 cameras on a self-hosted VMS actually costs per month.

Cost Item Annual Cost (10 cams) Per Camera / Month Notes
Dedicated server / mini PC $167–$267/yr $1.39–$2.22 $500–$800 hardware, amortized 3 years. Needs replacement when drives fail or CPU can’t handle camera count.
Electricity (server, 24/7) $74–$160/yr $0.62–$1.33 65W server = $74/yr at $0.13/kWh. Add a GPU for AI: +75W = $86/yr more. At commercial rates ($0.18/kWh), multiply by 1.4×.
HDD storage (30-day retention) $53–$100/yr $0.44–$0.83 10 cameras at 1080p H.265 ≈ 5–6TB on-disk for 30 days. Two 4TB HDDs ($140) replacing every 3 years. No redundancy included.
Remote access infrastructure $60–$200/yr $0.50–$1.67 Blue Iris Cloud relay $5/mo ($60/yr). VPN router $150 setup + DDNS service. Corporate VPN client licenses add more.
UPS / power protection $30–$60/yr $0.25–$0.50 Uninterruptible power supply to protect HDDs from power loss. $100–$180 unit, 3-year lifespan.
IT maintenance labor $600–$2,400/yr $5.00–$20.00 Minimum 1–4 hrs/month: OS updates, HDD health checks, camera re-authentication after firmware updates, troubleshooting failed recordings. At $50/hr.
TOTAL (no AI analytics) $984–$3,187/yr $8.20–$26.56 Excludes GPU for AI. Lower end assumes low labor cost; upper end reflects real IT billing rates.
+ GPU for AI analytics (Frigate, DeepStack) +$300–$560/yr +$2.50–$4.67 RTX 3060 Ti: ~$350 (amortized 3 yrs = $117/yr) + 75W electricity ($86/yr) + setup/maintenance time (~$100/yr).

Self-Hosted VMS (10 cameras, conservative)

$8–$27 / camera / month

Infrastructure + labor. Software license not the main cost.

  • No native AI analytics (people counting, ALPR, forensic search)
  • No multi-site dashboard
  • Remote access requires VPN or cloud relay setup
  • You are responsible for uptime, backups, and recovery

iFovea Cloud VMS (10+ cameras)

Contact for per-camera quote

One line item. Infrastructure, AI, and maintenance included.

  • 10 AI analytics types included: ALPR, people counting, forensic search, heat maps, and more
  • All sites on one dashboard
  • Native mobile app remote access — no VPN required
  • Cloud infrastructure managed and monitored by iFovea

The honest math

For organizations with a dedicated sysadmin who manages many other systems (where surveillance is a minor time allocation), self-hosted VMS can make sense. For businesses paying someone to manage surveillance infrastructure specifically — or where IT time has opportunity cost — cloud VMS is often cheaper on a per-camera basis when all costs are counted. Use the NVR Replacement ROI Calculator to model your specific deployment.

Open-Source VMS Resource Center

Compare platforms, estimate costs, and plan your migration

Open-Source vs Cloud VMS Guide
Blue Iris Alternative
Frigate NVR Alternative
ZoneMinder Alternative
Shinobi Alternative
NX Witness Alternative
Self-Hosted VMS Security Risks
GPU Requirements for AI Surveillance
VPN vs Cloud Remote Access
Edge Recording vs Cloud Recording
NVR Replacement ROI Calculator
Centralized Camera Management