Year-end database projects

Use your 2026 budget on the database project you keep putting off.

Choose a fixed-scope project, reserve your slot by December 11, and we start now or in Q1. Your team sets the priorities. Our specialists do the database work.

Start 2027 with the project off your list. A specialist replies within 1 business day.

Choose a project

Each project has a fixed scope and is quoted in a Statement of Work. We start with SQL Server and scope Oracle, PostgreSQL and MySQL projects on request. In every project we own the database side, and your team owns the application side: code changes, connection strings and application testing.

SQL Server upgrade

Move off SQL Server 2016 or older onto a supported version. We inventory your databases, check compatibility, build and test the new environment, rehearse the cutover and run the production upgrade. Typical timeline: 15 to 60 days. Best for teams on 2016 or earlier, or on a version that has already lost support.

Platform migration

Move databases to Azure or another cloud, or onto new servers, with the cutover rehearsed before it counts and monitored after. Cutover weekend support is available. Typical timeline: 30 to 90 days. Best for aging servers or a cloud plan that has not started.

High availability and disaster recovery (HA/DR)

Design and build high availability and disaster recovery to your recovery point and recovery time objectives. Typical timeline: 30 to 90 days. Best for teams whose recovery plan exists only on paper.

Data Environment Review

A risk-rated findings report and a prioritized remediation plan, written so a CFO can fund it. Add a block of remediation hours to start fixing what it finds. Typical timeline: 45 days. Best when you are not sure which project matters most. Covers SQL Server, Oracle, PostgreSQL and MySQL.

Why now

Two Microsoft support dates are making this decision for a lot of teams. Each one below says why it matters and why to act now.

SQL Server 2016: support ended July 2026

Why it matters

  • Microsoft no longer ships regular security patches or bug fixes for it.
  • Without Extended Security Updates, you cannot open a Microsoft support ticket, even with a support plan.
  • Extended Security Updates cover critical security fixes only.

Why now

  • Extended Security Updates billing began July 15, 2026, and costs roughly 75% of the original license price in year one (Brent Ozar Unlimited, April 2026).
  • Those charges stop once you upgrade.
  • An upgrade typically takes 15 to 60 days, so a project reserved by December 11 can start now or in Q1.

SQL Server 2017: support ends October 2027

Why it matters

  • It faces the same loss of security patches and Microsoft support that SQL Server 2016 does today.
  • The same Extended Security Updates cost applies to anyone who stays on it.

Why now

  • October 2027 lands inside next year's budget, so scoping now gives you a number to fund it.
  • Planning from 2017 is a shorter version jump than waiting until the move is urgent.

Sources: Microsoft Lifecycle pages (learn.microsoft.com/lifecycle) and Microsoft's SQL Server Extended Security Updates FAQ.

Proof

Year-end deadlines are met by planning. Two recent projects show how fast it can go.

128 days

3,500 databases and 300 applications moved in 128 days

A large North American insurer taken from SQL Server 2012 to SQL Server 2019: 3,500 databases and 300 applications upgraded, encrypted and migrated in 128 days, with no loss of service and no application failure. A fourth-quarter project. An end-of-life deadline at that scale is usually met by exception; this one was met by planning.

Read the case study

14 days

AWS migration completed in 14 days after a failed attempt

A global financial software platform handling tax filing, payroll and billions of dollars in transactions for millions of users had already attempted a cloud migration and failed. Fortified Data identified the performance bottlenecks behind the failure, downsized the environment and completed the move to AWS in 14 days, clear of peak season.

3 hrs

Zero data loss. A national bank's cluster was recovered using Always On.

6 TB

Restored in under 12 hours. A fleet management company's ransomware recovery.

How it works

  1. Tell us what you are putting off.

    The form takes 2 minutes.

  2. Get a fixed-scope quote.

    A specialist reviews your answers, holds one or two scoping calls and sends a Statement of Work, typically within 3 to 5 business days.

  3. Reserve your start date by December 11.

    We can accept a 2026 purchase order for work that begins in Q1.

  4. We do the database work.

    Your team keeps the priorities, decisions and the application side.

Why Fortified Data

  • Your team leads, our specialists do the database work. Upgrades and migrations carry the database-heavy parts of your project, so your team stays on its own roadmap.
  • A 100% U.S.-based team. Every person who touches your environment, including any subcontractor, is based in the U.S., with no hand-off to an offshore team.
  • 20+ years supporting mission-critical healthcare, financial services and retail environments.

Reserve my slot

Questions

Can I use 2026 budget for work that starts in Q1?

Yes. We can accept a 2026 purchase order and, depending on the engagement type, invoice in 2026 with work beginning in January. Please check with your finance team on how to handle it on your end.

How much does a project cost?

Each project has a fixed scope and is priced in a Statement of Work. Tell us what you need and we respond within 1 business day.

We work with an MSP. Can you still help?

Yes. Your MSP keeps the broader relationship and its infrastructure, application and security services. We deliver the database work alongside them.

What if I am not sure which project I need?

Start with the Data Environment Review. It shows which project matters most and what it costs to wait. You can also take our free Database Health Score, which takes about 5 minutes and needs no access to your systems.

What does my team still own?

The application side: code changes, connection strings, DNS updates and application testing. We own the database side, from inventory to the production event, and your team signs off on what changes around it.

Which databases do you cover?

SQL Server first, with Oracle, PostgreSQL and MySQL projects scoped on request.