Pydantic Migration Guides
Migrate schema_extra in Config to json_schema_extra in model_config.
Start here
Replace schema_extra with json_schema_extra in your model_config.
Stop before automation when: schema_extra as a callable that needs signature changes. Files with other unsupported Config keys.
class User(BaseModel):
model_config = ConfigDict(
json_schema_extra={"examples": [{"name": "Alice"}]}
)
Repo fit check
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.
Example scan summary
supported_findings: 38
manual_review_findings: 6
files_uploaded: 0
confidence: reviewableWhy this page exists
schema_extra was renamed to json_schema_extra in Pydantic v2.
Direct answer
Replace schema_extra with json_schema_extra in your model_config.
Example
class User(BaseModel):
class Config:
schema_extra = {"examples": [{"name": "Alice"}]}
class User(BaseModel):
model_config = ConfigDict(
json_schema_extra={"examples": [{"name": "Alice"}]}
)
Decision path
The cleanup pack is strongest when the repo still uses direct pydantic imports and a clean validator/settings/config subset.
Before checkout
Price: $249.99 per team.
Use the exact-problem guides as a triage layer, then decide whether the repo is inside the supported subset.
FAQ
Replace schema_extra with json_schema_extra in your model_config.
Automate only the supported subset: schema_extra to json_schema_extra rename. Integration with Config to model_config migration. Reporting for where the old key appears. Keep these cases in manual review: schema_extra as a callable that needs signature changes. Files with other unsupported Config keys. Dynamic schema_extra generation.
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
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.
Replace @validator with @field_validator, Move BaseSettings to pydantic-settings, Convert Config to model_config, Replace validate_arguments with validate_call, Replace @root_validator(pre=True) with @model_validator(mode="before"), Why post root validators need manual review, Move pydantic.v1 imports onto pydantic, Why Config.fields is a manual-review case