Database Migration: MySQL to Postgres (and Back), Redis to Valkey
I move your data between database engines with a backup, a rehearsal, row-count checks, a rollback plan and a window you approve. Redis to Valkey from $260 ($200 founding). MySQL ↔ Postgres from $1,040 ($800 founding) after a short assessment, for apps with up to 30 tables that mostly use an ORM. Email your database and stack.
See a sample report, proposal and weekly update- Price
- from $260
- Founding
- from $200
- Timeline
- ~1 week
- Format
- Fixed scope, fixed price
- Hours
- US Eastern Time, async
Who this is for.
A good fit if
- Laravel, Python or Go apps moving between MySQL/MariaDB and Postgres
- Teams replacing Redis with Valkey after Redis’s license changes
- Apps consolidating on one database engine
Common triggers
- MySQL 8.0 reached end of life in April 2026 and you’d rather move to Postgres than upgrade
- Wanting Postgres features (JSONB, extensions)
- Redis licensing or a host that now ships Valkey
Not a fit if
- The database relies heavily on stored procedures, triggers or engine-specific views
- It’s hundreds of gigabytes with no possible maintenance window
- You need Oracle, SQL Server or MongoDB moves
What I do, and what you get.
What I do
- Assess first: schema, data types, queries that won’t work on the other engine, size
- Write the plan: tools, order, checks, rollback and window, for your sign-off
- Take a fresh backup of the source
- Convert schema and data (pgloader for MySQL to Postgres), fix types, sequences and indexes
- Run your tests and key flows against the new database on staging
- Cut over in the window and keep the old database untouched for rollback
- Redis to Valkey: check your Redis version, switch on staging, then production
What you get
- Assessment notes and a fixed quote (MySQL ↔ Postgres)
- A signed-off migration plan
- The app running on the new database, with row-count and checksum results
- A list of code changes made for engine differences
- Runbook and handover notes
Your part
- Access to the database, app repo and staging
- Tests or a list of key flows to check
- Sign-off on the plan and window
- Keeping the old database for at least 7 days
Included
- Schema and data move, type fixes, index and sequence fixes
- Code fixes for common engine differences (within scope)
- Backup, rehearsal, checks, rollback plan
- Redis to Valkey switch
Not included
- Rewriting stored procedures in bulk
- Performance tuning beyond basics
- Very large or zero-downtime replication (quoted)
- Redis modules with no Valkey equivalent
Fixed prices, agreed before work starts.
One instance, staging then production
Up to 30 tables, mostly ORM queries; scoped quote after a short assessment
More tables or raw SQL, priced after assessment; two monthly milestones of $975 ($750 founding)
Build your scope
- Timeline
- ~1 week
- Payment
- Paid in full before work starts
- Earliest start
- Oct 5
Founding price: 3 of 7 spots left, until Mar 31, 2027 — one-off work, in return for a testimonial. How it works
Prices are in USD, paid by bank transfer against an invoice. Work under $1,000 is paid upfront; larger work is 50% to start and 50% before handover, or monthly milestones. How working together works
Variations
- Redis → Valkey
- Usually a drop-in swap for Redis 7.2 and earlier; newer Redis data files need a different path.
- MySQL → Postgres (ORM apps)
- Most of the work is data types, case sensitivity and raw SQL.
- Postgres → MySQL
- Less common, and assessed the same way.
- Large data
- Replication-based options quoted after the assessment.
How it runs.
- 01
Send database details
Email your engine, version, size and stack, and I reply within one US business day.
- 02
Assessment and quote
For MySQL ↔ Postgres I run an assessment and send a fixed quote with a prepaid invoice.
- 03
Rehearse on staging
I rehearse on staging with a copy of the data while your tests run.
- 04
Sign-off and cutover
You sign off the plan, and I cut over in the window after a fresh backup.
- 05
Checks and handover
I run the checks and hand over, keeping the old database for rollback.
A new service, done openly.
I have not delivered this exact service for a client before, so there is no case study to point to yet. The approach above is built from parts I have shipped in production — see the case studies — and the fixed price and written scope protect you while it is new.
Questions buyers ask.
Is Valkey really a drop-in for Redis?
For Redis 7.2 and earlier, yes in most apps. Data files from Redis 7.4 and later can’t be loaded directly; I’ll check your version first.
Will my Laravel app just work on Postgres?
Mostly, if it uses Eloquent. Raw SQL, case-sensitive comparisons and some column types need changes; the assessment finds them.
How long is downtime?
It’s set by data size, measured in the rehearsal and written in the plan.
Can we go back?
Yes. The old database stays untouched until you confirm.
Have you done engine migrations for clients before?
This is a new service, with no past engine migration to point to. I’ve shipped systems on MariaDB and PostgreSQL, built a Go relay on Valkey, and designed backup and restore with a restore drill.
Ask about Database Migration.
Tell me what you have and where it hurts. I reply within one US business day with either a fixed quote or the entry step that makes a fixed quote possible.
Helpful to include
- Source engine and version
- Target engine
- Database size
- Number of tables
- ORM or raw SQL
- Stored procedures or triggers?
- Redis version (for Valkey)
- Deadline
More in Cloud & Server Migration
Hosting Migration
I move your app, database, files and workers to a new server or provider with a written plan, a fresh backup, a rollback path and a short maintenance window you approve. From $390 ($300 founding) for one site or app, usually 1–3 weeks. Email the current and target hosting to start.
Heroku/PaaS Exit
I move your Heroku (or similar PaaS) app to Docker on a VPS you own: web, worker, Postgres, Redis, scheduler and deploys, with a backup, a rollback plan and a short approved window. From $780 ($600 founding), typically 2–4 weeks. A new service. Email your Heroku app list and add-ons to start.
AWS to VPS Migration
For small apps paying more for AWS than they need, I move EC2, RDS, ElastiCache and S3-backed workloads to a simpler VPS you own, with backups, a rollback plan and an approved window, after a Cloud Cost Review. From $1,560 ($1,200 founding), about 4–6 weeks. Email your AWS services and bill.