We handle your migration end to end.
You have a production Oracle, MySQL, or SQL Server database that needs to move. We plan it, execute it, validate it, and hand it over — to the standard you expect from a team that has done this many times.
Migration paths we deliver
Everything from assessment to handover
Every engagement covers the full lifecycle. Nothing is charged as an add-on.
Migration Assessment
Full schema analysis before a single byte moves. We deliver a 12-section risk report covering data types, PL/SQL complexity, estimated downtime, and a recommended strategy.
- Schema and object inventory
- Risk scored LOW / MEDIUM / HIGH / CRITICAL
- Estimated migration duration and downtime window
- Recommended cutover strategy
End-to-End Migration Execution
We run the full migration: DDL conversion, parallel bulk data transfer, PL/SQL transpilation, CDC sync, validation, and cutover — with your team watching at every step.
- DDL + schema conversion with manual review
- Parallel bulk data loading (up to 16 workers)
- PL/SQL / T-SQL / stored procedure transpilation
- Row-count and SHA-256 checksum validation
Zero-Downtime Cutover
CDC-based sync keeps source and target in lock-step during cutover testing. When you flip the switch, app downtime is measured in seconds — not hours.
- Oracle LogMiner / MySQL binlog / SQL Server CDC
- Real-time lag monitoring < 5 sec steady state
- Smoke-test window with live sync running
- Coordinated cutover with your ops team
Quality Assurance & Validation
We do not call a migration done until four validation layers pass: row counts, checksum sampling, statistical distribution checks, and constraint verification.
- 100% table row-count verification
- Checksum spot-check on high-risk tables
- MIN / MAX / AVG statistical comparison
- FK and constraint integrity report
Performance Tuning
After the data lands, we tune the target. EXPLAIN ANALYZE on your top-50 queries, index recommendations, autovacuum configuration, and connection pooling advice.
- Query plan comparison (pre and post migration)
- Index coverage analysis
- Connection pool sizing recommendations
- VACUUM / ANALYZE on all migrated tables
Knowledge Transfer & Handover
Your team owns the database at the end. We document everything — the migration runbook, the changed objects, the open items — and walk through it in a structured handover session.
- Full migration runbook (Markdown + HTML)
- Objects changed / manually reviewed log
- Open items and future maintenance notes
- Live handover call with Q&A
Six steps, zero surprises
Every project follows the same rigorous process. You know what happens next at every stage.
Discovery Call
30 minTell us about your database — size, source and target engines, timeline, and any blockers you have hit before. We listen and ask the right questions. No sales pitch.
Assessment Report
1–3 daysWe connect to your source (read-only) and run the full assessment. You receive a detailed HTML report with every risk item scored and prioritised.
Project Plan
1 dayBased on the assessment we produce a migration plan: milestones, owner for each action, cutover window, and rollback criteria. You approve before any work starts.
Execution
Days to weeksWe run the migration in stages: schema, code objects, bulk data, then CDC sync. Daily status updates. Every completed chunk is checkpointed — no re-migration on failure.
Validation & Cutover
1–2 daysAll four validation layers run. Once green, we coordinate the cutover window with your ops team. Downtime target: < 5 minutes for CDC-enabled migrations.
Handover
1 dayFull documentation handover. 30-day post-migration support window included. Your team is fully briefed and confident in the new system.
High standards are non-negotiable
We apply the same standards to every engagement — whether you are migrating a 5 GB test database or a 5 TB production system. These are not optional extras. They are how we work.
- ISO-aligned project documentation
- Read-only access to source — we never write to source systems
- All credentials stored in encrypted vault, deleted post-project
- Migration tested on a staging copy before touching production
- Rollback plan documented and tested before cutover
- Your data never passes through our servers — runs on your infrastructure
Tell us about your project
Fill in the form and we will come back to you within a few hours. No obligation, no sales calls unless you want one — just a direct reply from an engineer who has looked at your situation.
Email us directly
hello@medaxai.com
Submit feedback or a question
Via our feedback form
Prefer a call?
Email us first and we will schedule one within 24 hours
Our response commitment
Project enquiry
Tell us the basics — we will handle the rest.
Common questions
Do you work on-site or remotely?
Fully remote. We connect to your source database via VPN or a secure tunnel. Most migrations do not require physical access, and keeping it remote means faster response times.
How long does a typical migration take?
Assessment: 1–3 days. Execution: days to 3 weeks depending on database size and complexity. A 50 GB Oracle database with moderate PL/SQL typically completes in 3–5 working days from assessment to handover.
What access do you need to our systems?
Read-only access to the source database is sufficient for assessment and bulk migration. We never write to your source. Target access requires CREATE privileges. All credentials are stored in an encrypted vault and deleted at project close.
Can you migrate during business hours?
Bulk migration runs continuously in the background — it does not impact source performance. The cutover window (typically 5–30 minutes) is scheduled during your low-traffic window.
What if something goes wrong during cutover?
We document and test a rollback plan before cutover starts. If any check fails during cutover, we abort and revert to the source database. The source is never shut down until the migration is validated.
Do you offer post-migration support?
Every engagement includes a 30-day post-migration support window. We monitor query performance, investigate any application errors traced to the migration, and answer questions from your team.
More questions? Email us or check our documentation.