# Managed Windows & SQL Server Hosting Migration

> URL: https://www.atlantic.net/dedicated-server-hosting/managed-windows-sql-server-hosting-migration/ | Published: 2026-10-07 | Author: Richard Bailey

# Managed Windows And SQL Server Hosting With End-To-End Migration

An organization approached Atlantic.Net about moving its business-critical websites and web applications from an existing managed hosting provider. It needed replacement Windows infrastructure and an end-to-end migration covering SQL Server, IIS, application files, firewall configuration, backups, testing, and final cutover.

The customer had no internal infrastructure or SQL team. Its chosen hosting partner would therefore need to plan and carry out the migration, identify specialist work during discovery, and provide clearly defined ongoing support. An independent assessment of its SQL Server requirements was particularly important: the organization wanted its proposed architecture and licensing validated before signing the final hosting agreement.

For this inquiry, we would begin by scoping the discovery and assessment. This installment of our managed hosting proposal series examines the requirements and how we would evaluate a potential response, with the final configuration, migration scope, and commercial terms still to be determined.

## Reviewing The Existing Environment And Replacement Requirements

The existing environment ran Microsoft SQL Server 2019 Standard Edition and approximately five SQL databases, including a SQL Server Services database. IIS hosted the websites and applications, with additional application files, services, and server configuration to account for during migration.

The customer also supplied a replacement specification previously proposed by its current provider. This was for reference for assessment, not an Atlantic.Net configuration or a requirement to reproduce the same architecture.

| **Component** | **Existing Provider’s Replacement Proposal** | **What to Check** |
| --- | --- | --- |
| **Server and processor** | Dedicated server with a modern enterprise-grade Intel Xeon processor | CPU utilization, workload peaks, and the appropriate physical or virtual deployment |
| **Memory** | 128 GB RAM | Actual memory demand across SQL Server, IIS, and background processes |
| **Storage** | 2 × 960 GB SSDs in RAID 1 | Usable capacity, storage performance, transaction logs, temporary files, and growth |
| **Operating system** | Windows Server 2025 Standard | Application compatibility, SQL Server compatibility, and managed support coverage. |
| **Security** | Managed firewall | Required traffic flows, administrative access, VPNs, and existing rules |
| **Protected backup data** | Approximately 600 GB | Protected data inventory, daily change rate, retention, and recovery requirements |

Our assessment would compare this reference with the workload’s measured requirements. Atlantic.Net offers [dedicated infrastructure](https://www.atlantic.net/dedicated-server-hosting/managed-private-cloud/)and a managed private cloud, providing options to evaluate a physical or virtualized deployment without deciding the architecture in advance.[ ](https://www.atlantic.net/managed-hosting/)

The approximately 600 GB of protected data would also need verification. The RFQ did not establish how much of that total consists of databases, application files, or other server data, so it would not be sufficient on its own to size the replacement environment.

## Assessing SQL Server Before The Hosting Contract

The customer wanted a documented explanation of whether Standard Edition was necessary, which features were being used, and whether another licensed architecture could reduce costs while preserving application functionality.

For this requirement, we scoped a review of the SQL installation, database configuration, scheduled jobs, integrations, and application dependencies. The assessment needed to distinguish between installed components and the features production processes actually used.

### Understanding the SSISDB Dependency

SSISDB required particular attention during the pre-sales process; our database engineers needed to confirm whether SSIS packages were active and which corresponding server applications depended on them.

Microsoft lists core SSIS functionality—including built-in tasks, transformations, and data-source connectors—as unavailable in Web Edition. If the customer’s production processes rely on those features, a straightforward replacement of Standard Edition with Web Edition would not preserve the existing functionality.[ ](https://learn.microsoft.com/en-us/sql/integration-services/integration-services-features-supported-by-the-editions-of-sql-server?view=sql-server-ver15)

There were a few concerns over the SQL version being used; [Microsoft has discontinued](https://learn.microsoft.com/en-us/sql/sql-server/what-s-new-in-sql-server-2025?view=sql-server-ver17) the Web Edition in SQL Server 2025. Any earlier-version Web Edition option would therefore need review for availability, support lifecycle, licensing eligibility, and technical suitability.[ ](https://learn.microsoft.com/en-us/sql/sql-server/what-s-new-in-sql-server-2025?view=sql-server-ver17)

### Choosing Compatible Windows And SQL Versions

Windows Server 2025 does not automatically require SQL Server 2025. Microsoft [supports SQL Server 2019](https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/install/windows/use-sql-server-in-windows)on Windows Server 2025, although application compatibility, patch levels, and Atlantic.Net’s management coverage for the selected versions would still need confirmation.

The intended assessment deliverable would be an edition and version recommendation supported by feature evidence, compatibility testing, and licensing review. That would give the customer a basis for evaluating the final proposal before committing. These options can help reduce costs; it’s always advisable to run the latest operating system and application versions wherever possible.

## Defining The End-To-End Migration Scope

The Atlantic.Net Advanced Migration service includes engineer-led environment review, migration planning, setup within the managed-services scope, migration of specified data, and customer sign-off. This inquiry would require a detailed scope covering the Windows, SQL Server, and application dependencies identified during discovery.

The inventory would include databases, SQL logins and permissions, scheduled jobs, relevant services, and any external connections. On the web-server side, we would audit IIS sites, application pools, bindings, application files, runtime dependencies, TLS certificates and their private keys, file permissions, and Windows scheduled tasks.

SSISDB requires catalog-specific migration preparation. [Microsoft documents requirements](https://learn.microsoft.com/en-us/sql/integration-services/catalog/ssis-catalog?view=sql-server-ver17) around a database master key, relevant server objects, catalog compatibility, and validation through package execution after restoration.

Any specialist SSIS remediation or application-vendor involvement would need a named owner and clear treatment in the Statement of Work. The migration plan would not assume that the customer could complete unassigned DBA or application-engineering tasks.

## Planning A Parallel Build, Testing, And Cutover

The customer preferred to keep its existing environment operational while we built, migrated, and tested the replacement. For this requirement, we would assess a parallel approach with controlled test access and safeguards against duplicate scheduled processes or unintended production activity.

Acceptance testing would cover database connectivity, websites and application workflows, IIS behavior, HTTPS, permissions, scheduled processes, and SSIS functionality where applicable. The test plan would also include the services and integrations discovered during the initial review.

A migration rehearsal is needed to help establish a final synchronization method and estimate expected downtime. The cutover procedure would identify when to pause application writes and background jobs, complete the remaining database and file transfers, redirect traffic, and validate production operation.

This proposal requires special attention to rollback. Where a SQL version upgrade is involved, Microsoft confirmed that an upgraded database [cannot run on an older Database Engine version](https://learn.microsoft.com/en-us/sql/relational-databases/backup-restore/restore-a-database-backup-using-ssms?view=sql-server-ver17). The recovery plan would therefore need to account for that limitation.[ ](https://learn.microsoft.com/en-us/sql/relational-databases/backup-restore/restore-a-database-backup-using-ssms?view=sql-server-ver17)

The old environment would remain available for an agreed validation period, with controls preventing conflicting writes. Decommissioning would follow the customer’s explicit approval.

## Managing Firewall Rules, Public IPs, And Remote Access

Atlantic.Net’s managed firewall service includes policy configuration, updates, monitoring, and VPN capabilities. For this customer, the security scope would need to document public services, database connectivity, administrative access, and any VPN requirements identified during discovery.

The preference to retain existing public IP addresses would require an investigation into address ownership and portability. We would not include IP retention as a confirmed part of the migration until that review was complete.

Where new addresses were required, the plan would cover DNS changes, firewall rules, external allowlists, application settings, and VPN endpoints. DNS [time-to-live settings](https://developers.cloudflare.com/dns/manage-dns-records/reference/ttl/) would need attention before cutover because cached records affect how quickly address changes reach users.

## Specifying Backups And Recovery

Our [managed Veeam service](https://www.atlantic.net/managed-services/veeam-services/)provides backup policy design, off-site storage options, monitoring, and engineer-led recovery for supported workloads. It fits this client’s requirements well.

The proposal included our recommendations for backup frequency, retention, storage location, and whether immutable protection was needed, along with details on restore procedures and any associated charges.

SQL recovery requires attention to database recovery, and a transaction-log backup strategy is a necessity. Microsoft’s full recovery model supports [point-in-time recovery](https://learn.microsoft.com/en-us/sql/relational-databases/backup-restore/recovery-models-sql-server?view=sql-server-ver17)when the necessary backups are available.

## Establishing Ongoing Windows And SQL Support

Atlantic.Net’s [server management services](https://www.atlantic.net/managed-services/server-management/)include Windows platform support, IIS assistance, operating-system patching, monitoring, and 24/7/365 incident response. The database support scope covers tasks such as database imports, user configuration, and backup setup, while excluding site-code and query analysis.

We also offer separately scoped consulting that includes [database administration](https://www.atlantic.net/managed-services/consulting/). For this inquiry, the proposal needed to determine whether specific SQL Server and SSIS were needed, what ongoing management covered, and whether any specialist professional services were required.

The support agreement would also need to define critical-incident escalation, response commitments, maintenance arrangements, and ownership of application-specific problems. With no internal infrastructure team, the customer needed a support model that left no essential operational task unassigned.

## Making The Complete Commercial Scope Clear

The customer requested a breakdown separating hosting infrastructure, Windows licensing, SQL Server licensing, firewall services, backup storage, bandwidth or data transfer, and monitoring and support. Migration and other professional services would need to appear separately from recurring charges.

Following discovery, the organization preferred a fixed monthly price for the agreed environment and a fixed-price migration Statement of Work. The customer also wanted completed variable charges, additional-work approval procedures, contract duration, minimum commitments, annual increases, and early-termination provisions. This would support the customer’s main purchasing requirement: understanding the validated technical scope and ongoing cost before signing.

## Discussing A Windows And SQL Server Migration With Atlantic.Net

This inquiry brought infrastructure selection, SQL assessment, migration delivery, and ongoing support into one purchasing decision. A useful response would connect those requirements through a documented discovery process, an accountable migration scope, and acceptance criteria the organization could evaluate.

For a similar project, [contact our solutions team](https://www.atlantic.net/about-us/corporate-contact/) with your current Windows and SQL Server versions, database and file-storage requirements, known SSIS dependencies, and acceptable downtime. Include your recovery requirements so we can discuss the discovery and managed-service scope appropriate to the environment.