SQLAlchemy Migration Guides
Separate the easy Query cleanup from the broader Query-to-select refactor work.
Start here
Start with deterministic fixes like Query.get(...), string joins, string loader paths, and select([..]) list syntax. Treat broad Query-to-select rewrites as manual review.
Stop before automation when: Broad Query-to-select rewrites. Result-shape changes.
query = session.query(User) # still legacy, not the first rewrite target
user = session.get(User, user_id)
rows = session.query(User).join(User.addresses).all()
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
Query still exists in 2.0, but legacy breakages should be split from the bigger refactor bucket.
Direct answer
Start with deterministic fixes like Query.get(...), string joins, string loader paths, and select([..]) list syntax. Treat broad Query-to-select rewrites as manual review.
Example
query = session.query(User)
user = session.query(User).get(user_id)
rows = session.query(User).join("addresses").all()
query = session.query(User) # still legacy, not the first rewrite target
user = session.get(User, user_id)
rows = session.query(User).join(User.addresses).all()
Decision path
Start with the free scan, inspect the report, and only move to the cleanup pack if the repo has repeated supported patterns that are still expensive to fix by hand.
Before checkout
Price: $299.99 per team.
Use the exact-problem guides as a triage layer, then decide whether the repo is inside the supported subset.
FAQ
Start with deterministic fixes like Query.get(...), string joins, string loader paths, and select([..]) list syntax. Treat broad Query-to-select rewrites as manual review.
Automate only the supported subset: Repo-fit guidance for the safe Query cleanup subset. Internal links to the exact issue pages. A scanner-first path before paid tooling. Keep these cases in manual review: Broad Query-to-select rewrites. Result-shape changes. App-specific loader strategy decisions.
Use SQLAlchemy 1.4 to 2.0 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 session.query(...).get(...), Fix engine.execute(...) removal, Clean up joinedload_all(...), Fix select([..]) list syntax, Replace string join paths, Replace string loader options, Move sqlalchemy.ext.declarative imports to sqlalchemy.orm, Replace insert(..., values=...)
View all SQLAlchemy 1.4 to 2.0 Migration Cleanup Pack guides