Editing production Firestore data is sometimes necessary and rarely risk-free. A short checklist keeps small fixes from becoming incidents.
Before you edit
- Confirm the project and database. It’s easy to be looking at staging when you think you’re in production, or the reverse. Check the project name first.
- Read the whole document. Understand the shape of the data — field types, nested maps, references — before changing anything.
- Know the field type. A timestamp is not a string; a reference is not text. Changing a value to the wrong type can break readers downstream.
While you edit
- Change one thing at a time. Smaller edits are easier to reason about and to reverse.
- Confirm deletes deliberately. Deletion has no undo. Re-read the document before confirming.
After you edit
- Verify the app behaves. The point of the change is the app, not the database row. Check the result where it matters.
Tooling that helps
Good tooling makes the safe path the default: rendering field types natively so you don’t mistype them, requiring confirmation before deletes, and scoping access to your own permissions. That’s the model behind managing Firestore in Firedeck.