Skip to main content
Free plan, no cardStart free
Test data and credentials 6 min read Updated

Data Shift: check a database migration before moving

Data Shift is the migration workbench inside API Studio. Today it does the part that goes wrong first: connect to the source with a connection string or a structured credential, read its tables, pick a target engine and generate the migration schema with a pre-flight list of what will change or drop, then run the governance checks on the plan. PostgreSQL, MySQL, SQLite and MongoDB are the targets implemented today. Copying rows and keeping the two sides in sync are later milestones, and the screens that preview them say so.

About this guide

Written for
Developers who own their tests · Engineering managers · SDETs and automation engineers

What works today

  1. Source database: choose the engine, paste a connection string or enter a structured credential, and test the connection. A failure names the stage it failed at.
  2. Read the schema: the tables and columns of the source.
  3. Target database: choose the target and generate the migration DDL. The pre-flight lists what will change or drop before you run anything.

Targets that are real, and targets that are not

The target picker lists twelve engines; four are implemented today: PostgreSQL, MySQL, SQLite and MongoDB. Supabase, Neon and CockroachDB generate PostgreSQL; PlanetScale generates MySQL. A target that is listed but not implemented produces no DDL and says exactly that, rather than a plausible script that would fail on the first statement.

Governance and safety

The governance tab checks the plan rather than the data: whether the move takes personal data across a border lawfully, a scan for personal-data columns with a masking plan for them, a comparison of the two engines by key column, and the success metrics the migration will be signed off against. Use it before anyone copies a row, because it is cheap here and expensive later.

What is a preview

Three screens show what the finished product will look like and are labelled as previews: the assessment (a complexity score, risk items, stored-procedure conversions and an hour estimate) is marked as a legacy preview with no data-movement backend behind it; the migration and change-data-capture progress, and the verify-and-cutover page, say that no verification run is backing their numbers; the post-migration health page says its grade, latency and drift are placeholders, not measurements. We would rather label a preview than let you read it as a result.

Who can use it

Data Shift is on the API testing entitlement, so every plan has it. Run the generated DDL yourself, in your own tooling, after reading the pre-flight; the platform does not run it against your target.

Questions people ask about this

Does Data Shift move my data?
Not yet. It generates the target schema and the checks around it. The row copy and the change-data-capture sync are later milestones, and their screens say so.
Which engines are implemented?
PostgreSQL, MySQL, SQLite and MongoDB as targets, with Supabase, Neon and CockroachDB mapped to PostgreSQL and PlanetScale to MySQL. The other engines in the picker generate nothing and say why.
Why does the health page show dashes?
Because nothing is measuring yet. The page prints a dash rather than a number it did not measure.

Source: /documentation/data-shift-migration-checks, updated 2026-11-16. Answers are checked against the shipped product on that date.

Found something out of date? The people who build the module answer the contact form on the home page, and corrections to this guide are dated above. Tell us.

This guide is about the API testing studio, where Data Shift lives. Twenty tools, including ours, are compared by job.

Try it against your own app.

Record one flow and get four kinds of evidence back. Judge the results yourself.

  • Free plan, no card
  • 14-day Solo Pro trial
  • Demo replies within one business day
  • Data hosted in India