Appwrite Database attribute deletion and data persistence

Question

Schema Modification Behavior
Appwrite allows for the dynamic definition of collection attributes to structure document data. When managing these schemas, certain modifications are additive, while others are destructive. Specifically, the platform does not currently provide a native mechanism to revert a schema change without manually deleting the modified attribute.

Data Loss Constraints
Because changing an attribute type typically requires the deletion and subsequent recreation of that attribute, the associated data for that specific field is removed across all documents in the collection. This creates a challenge for maintaining data integrity during iterative schema updates or when attempting to roll back a structural change.

What is the recommended approach for preserving field data when an attribute type must be changed? Is there a documented method to perform a non-destructive schema migration within the Appwrite Database service?

Siddharth · Answer

Answer
The recommended way to keep field data when you must change an attribute’s type in Appwrite is to back up the collection, delete the old attribute, create a new attribute with the desired type, and then restore the data into the new attribute.
Confirmed facts (from Appwrite behavior)

Deleting an attribute removes the field and all its values from every document in the collection; the operation is immediate and irreversible.
Appwrite does not retain a soft‑delete or version history for removed attributes.
Other attributes and documents remain unaffected after the deletion.
To avoid data loss, you must export or back up the collection before deleting the attribute.

Likely explanation for the workflow
Because there is no built‑in “alter column type” operation, the only safe path is to treat the attribute change as a delete‑then‑add cycle while preserving the existing values externally.
Steps for this case

Export the collection (or take a full backup) using the Appwrite CLI, SDK, or console → you will obtain a JSON array of documents.
In the console, go to Database → Collections → <your collection> → Attributes and delete the attribute whose type you need to change.
Re‑create the attribute with the same name but the new data type.
Modify the exported JSON: for each document, move the old field’s value into a temporary field (if you kept it) or directly assign it to the new attribute name.
Import the modified JSON back into the collection (via SDK or CLI) to populate the new attribute with the original values.
Optionally, remove any temporary fields used during the migration.

Appwrite Database attribute deletion and data persistence

Schema Modification Behavior

Data Loss Constraints

1 answer

Answer

Confirmed facts (from Appwrite behavior)

Likely explanation for the workflow

Steps for this case

Your perspective belongs here.

1 question comment