Database Migration & Modernization
Licence renewals, data centre exits and consolidation programs all end in the same place: moving data without breaking the business. We assess every database honestly, move only what pays back and validate every row before cut-over.

Sound familiar?
- An Oracle or SQL Server renewal is coming and finance wants to know what a move to PostgreSQL would really cost.
- You are leaving a data centre or VMware and dozens of databases need a home on AWS, Azure or Google Cloud.
- Years of growth left you with too many small instances, engines and versions to secure and patch.
- A previous migration stalled on stored procedures, data types or a cut-over nobody could rehearse.
What you receive
- Assessment with a target and effort per database
- Licence and run-cost comparison
- Wave plan with dependencies
- Converted schema and code in your repository
- Validation reports and cut-over runbooks
What we deliver
Scope is confirmed in writing in the assessment, with anything out of scope listed too.
- 01
Portfolio assessment
Every database scored on size, complexity, code, dependencies and business criticality, with a recommended target.
- 02
Target design
Aurora, RDS, AlloyDB, Cloud SQL, Spanner, Azure SQL or Azure Database for PostgreSQL, sized and secured with Terraform.
- 03
Schema and code conversion
Stored procedures, packages, triggers and data types converted and unit-tested, with tooling where it helps and engineers where it does not.
- 04
Data movement
Bulk load plus change data capture (AWS DMS, Datastream, Debezium or native replication) to keep downtime short.
- 05
Validation
Row counts, checksums and side-by-side query results compared automatically before each cut-over.
- 06
Consolidation
Fewer, larger, better-run instances with a clear owner, backup policy and patch routine.
Fixed scope and a fixed fee, agreed in writing.
Every engagement is scoped after a free 30-minute review. The scope and fee are confirmed in writing before work starts, and the assessment fee is credited toward the project.
Step 01
Migration assessment
Fixed fee, scoped after the free review
Target per database, effort and risk, licence and run-cost comparison, wave plan and a fixed migration quote. Credited toward the migration.
Step 02
Migration waves
Fixed fee, scoped after the free review
Scoped per wave from the assessment, agreed in writing before work starts.
Samples and an example engagement
Templates with fictional systems and an illustrative scope, so you can judge the depth before the first call.
Sample assessment report: database upgrade readiness
The structure and depth of the written plan you receive at the end of a paid assessment, shown with fictional systems.Sample deliverableSample cut-over runbook: PostgreSQL major upgrade with blue/green
A step-by-step runbook excerpt with timings, owners, checks and the rollback path.ChecklistDatabase upgrade readiness checklist
29 checks before a major-version upgrade of PostgreSQL, MySQL, SQL Server, MongoDB or Cassandra. Printable.From first call to delivery
You can stop after any step and keep everything we have written.
- 01
Free
Free 30-minute review
We look at what you run, what is urgent and whether a fixed-fee engagement fits. You get a short written summary.
- 02
2โ4 weeks ยท credited
Migration assessment
Targets, wave plan, cost comparison and a fixed quote.
- 03
Per wave
Migration waves
Converted, loaded, validated and cut over with a way back.
Technologies
Names are trademarks of their owners. Listing does not imply partnership.
Questions about this service
Straight answers on scope, fees and how we work. Anything else, ask us.
Do you always recommend leaving Oracle or SQL Server?
No. Some workloads depend on features that make a move expensive. The assessment shows the cost and payback for each database, and keeping some where they are is a valid outcome.
Can the migration be funded by the cloud provider?
Programs such as AWS MAP, Azure Migrate and Modernize and Google RaMP exist, but they are usually run through accredited partners. We are independent and do not claim access to them; we can work alongside a partner if you use one.
How long does a typical migration take?
A single application database usually takes weeks; a large estate is run in waves over months. The assessment gives a realistic plan.
Who owns the converted code?
You do. Everything goes into your repository.
Start with a free 30-minute review.
Databases, cloud or AI: talk to a senior engineer about what you run and what is coming. We reply within one business day and sign your NDA on request.
