Database migration, reconciled table by table

Database migration in a fixed-price 30-day sprint, with everything that depends on it moved too.

Fixed price from A$50,000 per sprintUpdated

A computer motherboard with its processor socket and memory slots
The platter and read arm of an open hard drive

What is database migration?

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.

Database support dates

Oracle Database 19c has Premier Support until the end of 2029, so the usual reason to move sooner is cost.

  • 9 Jul 2024SQL Server 2014Extended support ended (paid security updates to July 2027)Ended
  • 14 Jul 2026SQL Server 2016Extended support ended (paid security updates to July 2029)Ended
  • 12 Oct 2027SQL Server 2017Extended support endsUpcoming
  • 31 Dec 2029Oracle Database 19cPremier Support ends (Extended Support to 2032)Later
  • 8 Jan 2030SQL Server 2019Extended support endsLater

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.

Database moves that fit in 30 days

Illustrative examples, one database or warehouse area per sprint.

SQL Server 2014 or 2016, back on support

Upgraded, or moved to Azure SQL or PostgreSQL, and performance tested.

Oracle to PostgreSQL or Aurora

Schema, data and PL/SQL moved, with costs compared first.

A warehouse subject area moved

Warehouses moved to Snowflake, Databricks, BigQuery or Fabric, and reconciled.

Access, FoxPro and spreadsheets to a real database

Critical data moved out of desktop files into a secure database.

Sybase, Informix or Progress to PostgreSQL

Older platforms with shrinking support moved to an open, widely supported database.

How we prove it worked

Every table reconciled

Row counts and key totals reconciled for every table.

Record-by-record samples

Sampled comparisons, record by record, on critical data.

Your real workload

Performance tested against the workload you actually run.

Backups restored

Backups restored and verified before go-live.

Signed off by owners

Reconciliation signed off by your data owners.

A rehearsed way back

The old database stays available, with a tested rollback, until sign-off.

One database, moved and reconciled in 30 days

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

Book a database call

FAQ

Database migration questions

Anything else? Email contact@sovereignsystemslabs.com.

How do you prove nothing was lost?

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.

How much can moving from Oracle to PostgreSQL save?

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.

How much downtime will we need?

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.

What about stored procedures and reports?

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.