Pay once. Migrate with confidence.
No subscription, no per-seat, no metered runtime. One fixed quote covers the analysis and every generated artifact — and you see the exact number before you pay.
A 48-table MySQL → PostgreSQL move, 180 GB, near-zero downtime.
Small, homogeneous moves with a clear path.
- Up to ~25 tables / 10 GB
- AI-generated DDL + data scripts
- Validation query suite
- Rollback plan & runbook
- Email support
Cross-engine moves and moderate data volumes.
- Up to ~200 tables / 250 GB
- Type-mapping & transformation logic
- Zero-/low-downtime cutover plan
- Validation + reconciliation suite
- Priority support
Cross-paradigm or mission-critical migrations.
- Unlimited tables / TB-scale
- Cross-paradigm remodeling (SQL ⇄ NoSQL)
- CDC dual-write & phased cutover
- Full rollback + DR runbook
- Dedicated migration architect
Listed prices are the tier base. Your real quote scales from there with the factors below — every migration is priced for what it actually is.
The price is computed, not negotiated.
Morph never lets the AI invent a number. The model proposes a complexity score; the price is derived on the server from concrete properties of your migration. Same inputs, same price — every time.
Data volume
+$90 / 100 GBThe first 10 GB are included. Beyond that, every additional 100 GB adds about $90 — copy time, checksums and reconciliation all scale with bytes moved.
Schema breadth
+$40 / tableUp to 25 tables are baked into the base. Each table past that adds $40 — every relation needs its own type map, indexes and validation probes.
Cross-engine move
× 1.25Same family, different engine (PostgreSQL → MySQL). Dialect, function and type-system differences raise translation effort by a quarter.
Cross-paradigm remodel
× 1.6Relational ⇄ document, SQL ⇄ wide-column. The data model itself is redesigned from your access patterns — the hardest class of migration.
Downtime tolerance
× 1.1 – 1.35“Minimal” adds 10%; “none” adds 35%. Zero-downtime cutovers need CDC dual-write, traffic routing and a rollback armed the whole way.
Cheaper than the wrong way to migrate.
A migration done by hand or by a contractor isn’t free — it’s weeks of senior time, scoping calls and a rollback plan nobody wrote. Here’s the trade, without the spin.
Contractor figures are typical day-rate ranges for a senior migration engineer in North America and Western Europe; your mileage varies by region and scope.
Before you commit
Is this really a one-time charge?+
Yes. You pay once per migration — for the analysis, the quote and every generated artifact. There is no subscription, no per-seat licence and no metered runtime. Run the migration on whatever schedule you like; nothing keeps billing you.
When and how is the exact number set?+
Before you pay. Morph computes the price deterministically from your migration's shape — data volume, table count, whether it crosses engines or paradigms, and your downtime requirement. You see the precise figure on the quote screen, and it does not change after the fact.
What if my move sits between two tiers?+
The tier comes from the AI's complexity score, then the volume, breadth and multiplier factors are applied on top. So a 60-table same-engine upgrade and a 12-table cross-paradigm remodel can land at very different prices even though both start from the Standard base.
Do you need access to my production database to quote?+
No. The quote is built from the shape you describe — engines, versions, rough size, table count and constraints. Nothing connects to your data. You run the generated scripts yourself, against your own infrastructure.
What happens if the migration needs changes after I pay?+
Every migration includes its own AI chat. Ask it to adjust the type map, add a validation probe or rework a cutover step and it regenerates the affected artifact — no new charge for iterating on the migration you already bought.
Get a fixed quote for your migration.
Describe the move, see the exact one-time price, then let Morph generate every artifact. No card required to get the quote.