Migrating SQL Server Reporting Services (SSRS) reports to AWS can be challenging, especially when the source and target environments are disconnected or air-gapped. Many organizations operate in secure environments where direct network connectivity between on-premises systems and AWS is not allowed.
In this case study, we examine how Leidos, USA , completed an AWS SSRS migration involving more than 80+ SSRS reports, despite having no connectivity between the source SSRS server and the AWS environment.
Background: AWS SSRS Migration with Network Isolation
Leidos was modernizing its infrastructure by moving workloads from an on-premises data center to AWS. Their legacy SSRS server (Windows Server 2016) was scheduled for decommissioning.
Over the years, the server had accumulated:
- 80+ SSRS reports
- Deep folder hierarchies
- Shared data sources
Due to security policies, the on-prem SSRS environment and AWS were completely disconnected, making a traditional SSRS migration approach impossible.
This made the project a textbook example of a disconnected SSRS migration.
Key Challenges in Disconnected SSRS Migration
- No direct network access between on-prem SSRS and AWS
- Inability to use live source-to-target SSRS migration
- Risk of missing reports, folders, or shared data sources
- Manual redeployment not feasible for large SSRS estates
- Need for a safe backup before decommissioning
Solution: File-Based SSRS Migration to AWS
To address these challenges, Leidos used SSRS Reports Migration Wizard in Standalone Mode, leveraging its offline / file-based SSRS migration capability.
This approach is ideal for:
- AWS SSRS migration
- Air-gapped or disconnected SSRS environments
- Secure enterprise networks
AWS SSRS Migration Process (Step-by-Step)
Step 1: Export SSRS Reports from On-Prem Server
On the source SSRS server, the tool:
- Automatically discovered reports, folders, and shared data sources, subscriptions, roles etc.
- Displayed the full SSRS hierarchy for validation
- Exported all selected items into a single migration file
During export:
- Individual .rdl files were generated for each SSRS report
- Folder structure and metadata were preserved
This created a complete offline SSRS backup, a key requirement in regulated environments.
Step 2: Transfer Migration File to AWS (Disconnected Network)
Since the environments were disconnected:
- The migration file was securely transferred using approved methods
- No firewall changes or temporary network access were required
This step highlights the core benefit of disconnected SSRS migration to AWS.
Step 3: Import SSRS Reports into AWS Environment
On the AWS-hosted SSRS server:
- The migration file was imported
- Folder hierarchy and shared resources were recreated
- Data source connections were updated for AWS databases
After import, all SSRS reports were available for validation.
AWS SSRS Migration Results
- 80+ SSRS reports successfully migrated to AWS
- No network connectivity required between environments
- Folder hierarchy and report dependencies preserved
- Minimal downtime
- No manual report recreation
The migration was completed smoothly despite being a fully disconnected SSRS migration.
Additional Benefit: SSRS Backup and Disaster Recovery
An unexpected advantage of the file-based approach was backup:
“The tool creates .rdl files for each report… making it an easy way to back up SSRS reports, data sources, and folders.”
This makes the solution useful not only for AWS SSRS migration, but also for:
- SSRS backup
- Disaster recovery
- Compliance and audit scenarios
Why This Approach Works for AWS SSRS Migration
- Designed for disconnected and air-gapped networks
- Supports offline SSRS migration to AWS
- Preserves full SSRS hierarchy
- Generates reusable .rdl files
- Suitable for enterprise security requirements
Read full customer testimonial the on Visual Studio Marketplace.