# Migrating from Redocly to Powerduck

**Short answer:** The contract is already the valuable asset, so the migration is not a rewrite. Bring the OpenAPI file into the studio, validate it, and generate the reference, mocks, tests, and tools from it. The move consolidates the surfaces around the spec you already maintain.

## What carries over

The OpenAPI contract, the lint rules as a reference, and the existing reference as a visual baseline. Nothing has to be rebuilt from scratch.

## The migration path

1. Open the contract in the studio and validate it against the declared dialect.
2. Generate the reference and compare it to the old portal.
3. Generate the mocks and tests and wire them into CI.
4. Generate the MCP server and point the agents at it.

## What to expect

The first pass will surface the gaps that were previously handled by separate products. Treat them as a punch list; the result is one contract driving every surface.

## The payoff

After the move, a change is made once in the spec and every surface reflects it. The team stops keeping the portal, mocks, and tools in sync by hand.

Return to the [Powerduck vs Redocly comparison](https://www.powerduck.com/blog/powerduck-vs-redocly/), or read the [OpenAPI guide](https://www.powerduck.com/blog/openapi-guide-hub/).