#Upgrading Appwrite 1.7.4 → 1.8.x: What Happens to My Collections?

10 messages · Page 1 of 1 (latest)

sleek ruin
#

I'm currently running a self-hosted Appwrite v1.7.4 instance that still uses the old Collections/Documents database model.

I noticed that starting from v1.8.x, Appwrite introduces the new Tables (TablesDB) structure, which replaces the old model. The documentation also mentions that the legacy API will eventually be deprecated.

Before upgrading, I’d like to clarify a few important points:

Structural migration:
If I upgrade directly from v1.7.4 → v1.8.x, will everything migrate silently in the background?
For example, will my existing data automatically continue to work as:

Collection → Table

Attribute → Column

Document → Row

Can I continue using both the legacy SDK and the new SDK to access the same data after the upgrade, or will I need to choose one?

Release status:
I checked GitHub and saw that v1.8.x currently appears to be in RC (Release Candidate) status.
Because of that, I’m hesitant to migrate now — I’m concerned that new RC versions or bug fixes might appear soon, forcing me to upgrade again later when the stable release comes out.
Would you recommend waiting for a fully stable release before migrating?

Is it something like this ?

image.png
flat crest
#

It's better to wait, it might relieve you of a serious headache.

sleek ruin
#

Yeah, still waiting a meaningful response from a DB guy.

sturdy briar
calm river
#

Also appwrite is backwards compatible, meaning the old API will be mapped to the new API and won't stop working as long as you use the SDK or the X-Appwrite-Response-Format in the case of the REST API

sleek ruin
#

1.8 released! Anyone from the team or who’s upgraded — can you share your experience or answer some questions? @stuck stream

calm cave
#

I have upgraded and still using legacy documents CRUD everywhere.

I have not upgraded sdk documents usage to tablesdb yet because it's not a priority right now

One thing that is crucial to update in your code is opt in relationship loading. It's easy to do where you need it.

Screenshot_2025-10-26_at_10.55.50_AM.png
calm river
#

@calm cave @sleek ruin pls create a separated post or post in #🏠│general 😅

sleek ruin
#

Why are we opening a new thread though? I’m genuinely asking because I don’t understand 🙂
If we post it in general, the discussion might go off-topic and lose focus. Right now, it’s already in a perfectly fitting thread and all the replies are directly related.