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

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 ?

TL;DR

Appwrite developer wants to upgrade from v1.7.4 to v1.8.x, concerned about the migration from Collections to TablesDB. Unsure if data will migrate seamlessly and if both legacy and new SDK can be used post-upgrade. Also, hesitant to upgrade due to v1.8.x being in Release Candidate status. Solution: No automatic migration, migrate manually. Wait for a stable release before upgrading.

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more

Recommended threads

Need support?

Join our Discord

Get premium support