SQL Server 2014 or 2016, back on support
Upgraded to a current SQL Server release, or moved to Azure SQL or PostgreSQL, with applications repointed, jobs and reports moved, and performance tested against today's workload.
Database migration
Database migration, reconciled table by table.
Unsupported versions, rising licence bills and slow warehouses have the same fix. We move the database and everything that depends on it in a fixed-price 30-day sprint.
What is database migration?
Database migration moves data, schema and database code, such as stored procedures, triggers and scheduled jobs, from one database platform or version to another, and repoints the applications, reports and integrations that use it. It covers upgrades within a product, such as SQL Server 2016 to a current release, and platform changes, such as Oracle to PostgreSQL or Teradata to Snowflake.
A successful database migration proves three things before cutover: every row and total matches the source, performance meets today's workload, and security, backups and monitoring work on the new platform.
Database support dates
Not every move is urgent. Oracle Database 19c has Premier Support until the end of 2029, so the reason to move off it is usually cost, not a deadline.
- 9 Jul 2024SQL Server 2014Extended support ended (paid security updates to July 2027)Ended
- 14 Jul 2026SQL Server 2016Extended support ended (paid security updates available)Ended
- 12 Oct 2027SQL Server 2017Extended support endsUpcoming
- 31 Dec 2029Oracle Database 19cPremier Support ends (Extended Support to 2032)Later
Sources: SQL Server 2014, SQL Server 2016, SQL Server 2017 (Microsoft Lifecycle); Oracle Lifetime Support Policy.
Database moves that fit in 30 days
Illustrative examples, one database or warehouse subject area per sprint. Your scope is confirmed in the Migration Blueprint.
Oracle to PostgreSQL or Aurora
Schema, data and PL/SQL moved, with a side-by-side cost comparison agreed before the sprint starts.
A warehouse subject area moved
Teradata, Netezza or SQL Server warehouse tables, loads and reports moved to Snowflake, Databricks, BigQuery or Microsoft Fabric, and reconciled.
Access, FoxPro and spreadsheets to a real database
Business-critical data moved out of desktop files into a secure, backed-up database with proper access control.
Sybase, Informix or Progress to PostgreSQL
Older platforms with shrinking support moved to an open, widely supported database.
How we prove it worked
- Row counts and key totals reconciled for every table
- Sampled record-by-record comparisons on critical data
- Performance tested against your real workload
- Backups restored and verified before go-live
- Reconciliation signed off by your data owners
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 and credited in full if you go ahead within 60 days. Then a fixed-price 30-day sprint.
from A$50,000
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 uses your numbers, not ours.
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.