SQL Server 2014 or 2016, back on support
Upgraded, or moved to Azure SQL or PostgreSQL, and performance tested.
Database migration in a fixed-price 30-day sprint, with everything that depends on it moved too.

Database migration moves data, schema and database code to another platform or version, and repoints everything that uses it.
It succeeds when every row matches, performance holds, and backups work on the new platform.
Oracle Database 19c has Premier Support until the end of 2029, so the usual reason to move sooner is cost.
Sources: SQL Server 2014, SQL Server 2016, SQL Server 2017, SQL Server 2019 (Microsoft Lifecycle); Oracle Lifetime Support Policy. Microsoft publishes dates in US Pacific time.
Support dates SQL Server 2014 SQL Server 2016 SQL Server 2017 SQL Server 2019 Oracle Database 19c
Illustrative examples, one database or warehouse area per sprint.
Upgraded, or moved to Azure SQL or PostgreSQL, and performance tested.
Schema, data and PL/SQL moved, with costs compared first.
Warehouses moved to Snowflake, Databricks, BigQuery or Fabric, and reconciled.
Critical data moved out of desktop files into a secure database.
Older platforms with shrinking support moved to an open, widely supported database.
Row counts and key totals reconciled for every table.
Sampled comparisons, record by record, on critical data.
Performance tested against the workload you actually run.
Backups restored and verified before go-live.
Reconciliation signed off by your data owners.
The old database stays available, with a tested rollback, until sign-off.
A five-day Migration Blueprint inventories the database, its code and every connection, from A$9,500, credited in full if you go ahead within 60 days. Then a fixed-price 30-day sprint.
from A$50,000
Every table is reconciled against the source: row counts, totals on key columns and sampled record-by-record comparisons. Your data owners sign off the reconciliation before cutover, and the old database stays available until they do.
It depends on your licence and support terms, hardware and how much database code you have. The Migration Blueprint compares your current spend with the target's running cost before you commit, so the business case is built on your own numbers.
For most moves, data is copied and kept in sync while the old system runs, so the final cutover window is short. The exact window is measured in rehearsals and agreed before you book it.
They are part of the scope. Database code, scheduled jobs, reports and every application connection are inventoried in the Blueprint and moved, rewritten or retired in the sprint.