# Overview

> Guides for upgrading between better-supabase versions and for moving an existing app or library onto better-supabase.

Source: https://bettersupabase.com/docs/migration

Upgrade one minor version at a time: each version guide lists what to
change when moving from the version before it. To bring better-supabase
into an app that already runs, start with the existing-apps guide.

| Page                                                                  | Covers                                                                      |
| --------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| [Existing apps](/docs/migration/existing-apps)                        | Adopting better-supabase one module at a time next to your own tables       |
| [From 0.5 to 0.6](/docs/migration/0.5-to-0.6)                         | Kits renamed to blocks, the `better-supabase/blocks` subpaths and providers |
| [From 0.4 to 0.5](/docs/migration/0.4-to-0.5)                         | SQL object renames and a block that fails closed                            |
| [From 0.3 to 0.4](/docs/migration/0.3-to-0.4)                         | Cheaper requests, generated types and CLI                                   |
| [From 0.1 to 0.2](/docs/migration/0.1-to-0.2)                         | One claim contract for claims and SQL functions                             |
| [From plain supabase-js](/docs/migration/supabase-js)                 | Replacing `supabase.from()` calls with typed repositories                   |
| [From supabase-cache-helpers](/docs/migration/supabase-cache-helpers) | Mapping the cache-helpers React Query hooks to better-supabase              |