Zipper Tools

Pydantic Migration Guides

How to move pydantic.v1 imports onto pydantic in the safe Pydantic v2 subset

Rewrite direct pydantic.v1 imports when the imported symbols stay inside the supported v2 subset.

Start here

The safe first move

For supported direct imports, move from pydantic.v1 back to pydantic. Keep BaseSettings and unsupported decorators in their own migration buckets.

Stop before automation when: Aliased imports. Imports that include BaseSettings or other moved symbols.

Target shape

from pydantic import BaseModel, ValidationError

Repo fit check

Want to know if your repo has this pattern?

Run the matching scanner locally first. Read the free findings and manual alternatives; consider paid cleanup only if supported patterns repeat enough to justify the price.

  • Local scan; no repository upload.
  • Supported findings are separated from manual-review findings.
  • Buy only when the repeated pattern is worth automating.
Run the Pydantic scan first View example report See when to buy 
Example scan summary
supported_findings: 38
manual_review_findings: 6
files_uploaded: 0
confidence: reviewable

Why this page exists

How to move pydantic.v1 imports onto pydantic in the safe Pydantic v2 subset

Direct import path cleanup is deterministic as long as the symbols stay in the supported subset.

Direct answer

What changes

For supported direct imports, move from pydantic.v1 back to pydantic. Keep BaseSettings and unsupported decorators in their own migration buckets.

Example

Before and after

Before

from pydantic.v1 import BaseModel, ValidationError

After

from pydantic import BaseModel, ValidationError

Decision path

If this repeats across the repo, open the evaluation pages next.

The cleanup pack is strongest when the repo still uses direct pydantic imports and a clean validator/settings/config subset.

  • The repo has direct pydantic or pydantic.v1 imports, BaseSettings usage, safe Config blocks, or simple validators.
  • The migration pain is repetitive v1-to-v2 cleanup, not a custom semantic rewrite.
  • If the scan output is ambiguous, review its findings and upstream guidance. Do not buy expecting unsupported cases to be resolved.

Typical symptoms

  • Repos still pin import paths to pydantic.v1 after starting the v2 migration.
  • Teams want the import cleanup separated from the harder validator and config work.
  • Reviewers need proof that the porter will not touch unsupported symbols by guesswork.

What the product covers

  • Direct pydantic.v1 import-path rewrites in the supported subset.
  • Cross-links to the BaseSettings and validator pages.
  • Repo reporting for files that still rely on pydantic.v1 imports.

Manual-review boundary

  • Aliased imports.
  • Imports that include BaseSettings or other moved symbols.
  • Files that also contain unsupported validator/config patterns.

Keep the migration narrow

Use the exact-problem guides as a triage layer, then decide whether the repo is inside the supported subset.

FAQ

Fast answers before you decide

What is the safest fix for pydantic.v1 import path pydantic v2?

For supported direct imports, move from pydantic.v1 back to pydantic. Keep BaseSettings and unsupported decorators in their own migration buckets.

Can pydantic.v1 import path pydantic v2 be automated?

Automate only the supported subset: Direct pydantic.v1 import-path rewrites in the supported subset. Cross-links to the BaseSettings and validator pages. Repo reporting for files that still rely on pydantic.v1 imports. Keep these cases in manual review: Aliased imports. Imports that include BaseSettings or other moved symbols. Files that also contain unsupported validator/config patterns.

When should I buy Pydantic v1 to v2 Migration Cleanup Pack?

Use Pydantic v1 to v2 Migration Cleanup Pack only when this pattern repeats across enough files that manual cleanup is still costly. Use the free report and upstream guide to evaluate fit. Buy only if repeated supported edits justify the price; no paid assessment is required.

Purchase fit

Choose the lowest-risk next step.

One matching page is not enough by itself. Run the local scan, then buy only when the same supported pattern appears often enough to matter.

Buy if

  • The repo has direct pydantic or pydantic.v1 imports, BaseSettings usage, safe Config blocks, or simple validators.
  • The migration pain is repetitive v1-to-v2 cleanup, not a custom semantic rewrite.
  • The team accepts manual-review findings for alias-heavy imports and signature-heavy validators.

What the workflow includes

  • Installable local CLI workflow, not a hosted black box.
  • Supported validator, settings, import, and config rewrites.
  • Demo report, public proof, coverage notes, rollback checklist, and buyer terms.

Before checkout

  • Stripe Checkout handles secure payment and receipts.
  • Download your purchased ZIP after payment.
  • Runs locally; no hosted API, repo upload, or production credentials needed.
  • The free report includes the evidence needed to evaluate fit. Paid summary and template add-ons are optional.
  • 14-day refund review for published-scope or delivery mismatches.
Run the Pydantic scan first

Explore the details