CBRS Migration Guide: Transitioning to Band 48

April 8, 2026 · BATS Wireless

The Citizens Broadband Radio Service (CBRS) in the 3.5 GHz band (Band 48) has become the dominant spectrum choice for private LTE and 5G deployments in the United States. If you're running a private network on a different band — or if your existing CBRS deployment needs a platform upgrade — migrating to (or within) CBRS involves specific considerations around spectrum access, SAS coordination, and device compatibility.

This guide covers what you need to know.

CBRS Spectrum Basics

CBRS operates in the 3550–3700 MHz range and uses a three-tier spectrum sharing framework managed by a Spectrum Access System (SAS):

Most private network deployments use GAA access — it's free, immediately available, and sufficient for indoor and campus environments where interference is manageable. PAL licenses are valuable for outdoor, mission-critical, or high-density deployments where guaranteed spectrum access matters.

What Changes During a CBRS Migration

If you're migrating from a non-CBRS band (e.g., Band 41, Band 14, or licensed spectrum) to CBRS Band 48, several things change:

Migrating Within CBRS (Platform Upgrade)

If you're already on CBRS but migrating from one platform to another (e.g., from Baicells to BATS ECHO), the spectrum piece is simpler — you're staying on Band 48. The migration primarily involves:

CPI Requirements

Category B (outdoor) CBRS devices must be installed by a CPI — a Certified Professional Installer who is responsible for accurate location reporting, antenna parameters, and SAS registration. BATS Wireless maintains CPI certification and handles all SAS coordination as part of the migration.

Category A (indoor) devices have relaxed installation requirements but still need SAS registration.

RF Planning for CBRS

CBRS at 3.5 GHz behaves differently from lower bands like Band 41 (2.5 GHz) or Band 14 (FirstNet, 700 MHz). Key considerations:

How BATS Wireless Handles CBRS Migration

We manage the full CBRS migration process:

  1. Verify end-device Band 48 compatibility across your fleet
  2. Design RF plan optimized for 3.5 GHz propagation at your site
  3. Deploy BATS ECHO core and CBRS-certified radios
  4. Register all CBSDs with SAS under CPI credentials
  5. Reprovision SIMs and reconfigure devices
  6. Validate coverage, capacity, and SAS grant behavior
  7. Decommission legacy SAS registrations and hardware

Whether you're moving to CBRS for the first time or upgrading your existing CBRS platform, we handle the spectrum coordination so you can focus on operations.

Talk to us about your CBRS migration.

← Previous: 5 Signs You Need a Migration Next: Zero-Downtime Core Cutover →