How to Migrate Your Legacy Security System to BluSKY

Define Your System Structure in BluSKY

Begin by setting up the core framework:

• Create your enterprise-level system in BluSKY.
• Define each facility (branch, data center, HQ, admin building).
• Define occupancy — which people belong to which buildings.

This establishes the foundation for devices, people, and access assignments.

Define Your Devices and Hardware for Each Facility

For every facility, configure:

• Card readers
• Portals/doors
• Alarm points
• Cameras
• Intercom stations
• Elevators
• Any other security devices

Fast Method: Import directly into BluSKY

If your existing system can export hardware, schedules, or access levels to Excel or CSV, BluB0X can:

• Import all devices
• Import device locations
• Import schedules
• Import access levels
• Import access level groups

This instantly populates the entire security architecture without manual entry.

Import All Personnel, Visitors, and Vendors

Export your current personnel database — employees, contractors, tenants, vendors — including:

• Unique identifiers (required)
• Access levels
• Building occupancy
• Access level groups
•  Roles or departments

BluSKY imports all of this directly, preserving structure and assignments.

Set Up Automated Database Synchronization (Optional but Recommended)

If your institution maintains a centralized identity system (HRIS, IAM, IT directory), BluSKY can receive automated updates through:

• SCIM integration
• BluSKY API
• Nightly sync files
• Real-time event-based updates

Adds, edits, and deletes flow automatically—including access entitlement changes.
This ensures your cloud database stays perfectly aligned with your authoritative identity source.

Create Maps and Plot Devices Automatically

Import any existing floor plans or building maps.

BluSKY will:

• Automatically place devices
• Associate devices with physical areas
• Determine camera descriptions
• Generate camera metadata and relationships
• Link access, alarms, and video by location

This produces a clean, visual layout before any cutover begins.

Configure Rules, Alerts, and Automations

Next, configure BluSKY’s automation engine:

• “If-this-then-that” rules
• Alarm actions
• Video verification
• Behavioral analytics
• Notification routing
• Escalation logic
• Compliance workflows

Again — all done before switching hardware over.

Perform Full QA and Database Validation

Before migration day, the entire cloud system can be:

• Fully tested
• Validated against the legacy system
• Compared for consistency using BluSKY reports
• Checked for missing access levels, people, devices, or schedules
• Reviewed in parallel with your current system

BluSKY allows organizations to verify 100% of the database before going live.

Cut Over Hardware — Quickly and with Minimal Downtime

Once BluSKY is built, tested, and validated:

Option A: You already use Mercury hardware

Simply point your Mercury controllers to BluSKY.
They immediately begin taking updates and instructions from the cloud.

Cutover can be done:

• Overnight
• Over a weekend
• Site by site

No major hardware replacement.

Option B: You use proprietary legacy hardware

Replace it with:

• BluB0X ARC controllers, or
• Mercury boards

This step is simple because all configuration is already prepared in BluSKY.

Run Both Systems in Parallel (Optional)

BluSKY supports dual-running:

• The legacy system continues receiving identity updates
• BluSKY receives the same updates through API/SCIM
• Both systems operate simultaneously
• QA can be performed without any operational impact

This eliminates risk and ensures zero disruption during the transition.

Enable Single Sign-On (Recommended During Setup)

While integrations and imports are being set up, many institutions also deploy:

•  SSO for BluSKY dashboard access
• Integration with Azure AD, Okta, Ping, or any SAML/OIDC provider
• Adaptive MFA for admins or high-privilege users

This improves consistency and governance for both IT and physical security.

Final State: Your Institution Is Fully Modernized

Once a site is migrated:

• All devices communicate with the cloud
• All people and access permissions flow automatically
• All schedules, access levels, and groups are unified
• All logs, alarms, and events are neatly correlated
• All analytics and AI pipelines are active
• All compliance reporting becomes automated
• All audit trails become unified and searchable

Your institution now has enterprise-wide cloud-native security — with minimal disruption and minimal cost.

Summary: The Fastest, Safest Path to a Modern Security Platform

BluSKY allows institutions to:

•  Build the entire system before cutover
• Automate all identity changes
• Import all devices, schedules, and access levels
• Test everything in parallel
• Migrate site-by-site with almost zero downtime
• Reuse Mercury hardware
• Keep costs low
• Avoid operational disruption

This is the most modern, controlled, and low-risk migration process in the industry.