Reviewable Pydantic v1 → v2 cleanup for existing Python apps

What the $249.99 pack adds

A downloadable CLI that previews and applies the documented mechanical rewrites on your branch, with diffs and a JSON report. It leaves unsupported files unchanged. Dependency upgrades and application-level validation remain your responsibility.

Best fit: an existing Python application with repeated direct Pydantic v1 imports, simple validators, settings imports or Config classes, and tests you can run. For a few edits, use the free report and migrate manually.

Not a complete FastAPI upgrade. Complex validators, aliases and unsupported configuration remain manual work.

One-time purchase, $249.99 per team. Download the commercial ZIP after payment. No source upload, account with Zipper Tools or paid API required.

14-day refund review for published-scope or delivery mismatches. Read the license, refund and support terms. Questions: support@zippertools.org.

Supported scope and limitations

• Supported direct imports and BaseSettings moves.
• Simple two-parameter validators and pre root validators.
• Safe literal Config blocks and bare validate_arguments.
• Alias-heavy imports, validators using values/field/config, each_item/always, post root validators and removed config keys require manual review.
• Files containing unsupported patterns stay unchanged. Review all diffs and run your application tests.

Planning a Python or FastAPI upgrade?

FastAPI documents the Pydantic v2 requirement in recent releases, while Pydantic 2.13 added Python 3.14 support to its v1 namespace. A warning alone does not establish a need to migrate. Check your actual dependency versions and migration plan. This pack automates only the patterns listed above.

Start with the guide that matches your code: BaseSettings imports · Config classes · simple validators.

Evidence you can inspect

Our order-API example exercises request validation, normalization, settings and response serialization. A separate unsupported validator checks that the tool leaves uncertain code alone. This is a small synthetic application, not a customer migration or a time-savings benchmark.

Why not use the free alternative?

The free report is enough to evaluate supported patterns. No paid fit report is required. You can use the official migration guide or the free bump-pydantic codemod. Compare both on a branch before paying.

Our offer is the documented local workflow, explicit manual-review findings and packaged guidance. The comparison reports observed results, not a claim that Zipper Tools is universally better. If the free tool does the work you need, use it.

After payment

1. Download and extract your ZIP from the payment success page.
2. In a separate Python environment, run python -m pip install . from the extracted pack directory.
3. Preview against a clean branch, inspect the report, then apply supported edits.
4. Install the target project dependencies, run your tests and review before merging.

python -m pydantic_v2_porter.cli path/to/repo --diff --report preview.json
python -m pydantic_v2_porter.cli path/to/repo --apply --diff --report applied.json

If BaseSettings is migrated, add pydantic-settings to the application dependencies. The tool does not promise to resolve dependency or behavior changes.

One-time purchase, $249.99 per team. Download the commercial ZIP after payment. No source upload, account with Zipper Tools or paid API required.

14-day refund review for published-scope or delivery mismatches. Read the license, refund and support terms. Questions: support@zippertools.org.