iFovea cloud VMS and AI video analytics platform logo

How to Migrate from 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.

✅ 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