Firestore PITR and Scheduled Export Backups for Solo Flutter + Firebase Founders in 2026

By · Published 2026-10-04 · Updated 2026-11-01 · Last verified 2026-11-01

Indie Flutter apps on Firestore often ship Crashlytics, Perf Monitoring, and cost alerts first—then discover that a bad migration, a buggy admin tool, or an accidental delete has no rollback path. Firebase documents three complementary tools: Point-in-Time Recovery (PITR), scheduled database backups, and managed exports you can schedule with Cloud Functions + Cloud Scheduler. This 2026 guide covers a practical solo-founder cadence: when to enable PITR, how scheduled backups differ from exports, and what to verify after a restore. Pair it with a Firestore Security Rules review cadence, Cloud Functions cost alerts and budgets, and Performance Monitoring triage. It extends ship and post-launch loops in ship Flutter Firebase apps as an indie developer and indie product ops after launch. Cite official Firebase Firestore PITR, backups, and schedule-export docs; UI labels and CLI flags move. Portfolio: gspteck.com.

Diagram of Flutter Firebase app with PITR window, scheduled backups, and Cloud Scheduler exports

Why solo founders need a backup cadence (not just rules reviews)

Security Rules and App Check reduce abuse; they do not undo a mistaken bulk delete or a bad write from an admin script. Official Firebase docs describe PITR as retaining document versions for up to seven days after enablement (minute granularity), scheduled backups as daily/weekly consistent copies you restore into a new database, and scheduled exports as Cloud Scheduler–driven managed exports to Cloud Storage.

Common indie failure modes without backups:

PITR is disabled by default and has no free-tier storage; scheduled backups and managed export/import require Blaze. Plan cost alongside your existing Functions budgets.

A minimal weekly / monthly backup cadence

  1. Enable PITR on production — After you understand PITR storage pricing, turn it on so the 7-day window starts retaining versions (you cannot retroactively read 7 days immediately after enablement).
  2. Create backup schedules — Up to one daily and one weekly schedule per database; set retention (docs allow up to 14 weeks). Backups live in the same location as the source database.
  3. Schedule exports to GCS — Follow Firebase’s schedule-export solution: Cloud Function calling exportDocuments + Cloud Scheduler; use a nearby non–Requester Pays bucket; grant Import/Export Admin + Storage Admin to the function’s service account.
  4. Dry-run restore literacy — Know how you would restore a backup to a new database ID, reapply TTL policies (not included in backups), and re-check IAM—without improvising during an outage.
  5. Pair with cost and rules — Same calendar block as Functions budgets and rules review: export reads and PITR storage should not surprise you after a viral week.

PITR exports cannot replace a durable off-database copy; scheduled backups and GCS exports cover longer retention and disaster scenarios beyond the 7-day PITR window.

Cadence cards: enable PITR, daily weekly backup schedules, Cloud Scheduler exports to GCS

What to watch on Flutter + Firebase specifically

Four-step recovery: detect bad write, choose PITR surgical read or backup restore, verify new DB, reapply TTL and IAM

Incident response when data is wrong or missing

  1. Stop the bleed — Disable the bad admin path (Remote Config / feature flag); ensure rules and App Check still fail closed—see Remote Config kill switches.
  2. Choose recovery mode — Surgical stale read / rewrite for a small subset (PITR); full backup restore or PITR export/import into a new database for widespread corruption.
  3. Verify before cutover — Spot-check critical collections; reapply TTL; confirm IAM on the new database.
  4. Short postmortem — Note root cause next to Crashlytics/Perf notes; adjust schedules if retention was too short.

Restores to a new database ID mean your Flutter apps must be pointed at the restored DB (or you migrate data back)—practice the cutover story before you need it.

Ops pairing with Flutter product cadence

Put PITR/backup checks next to Crashlytics, Perf, and billing budgets in one weekly block. A viral release can raise export costs and Functions invocations together. Align backup retention and export bucket access with store privacy commitments—see product ops and policy. Pair with Crashlytics weekly triage so data loss and crash spikes are not reviewed in isolation.

Ops checklist pairing Firestore PITR scheduled backups and exports with cost alerts and rules review

Checklist for indie Firestore PITR and backups

What the official limits are

Firestore’s point-in-time recovery documentation states that PITR data is retained for 7 days. You can clone or export data at a whole-minute timestamp within that window, but not earlier than the moment PITR started retaining data for your database. The scheduled backups documentation describes daily and weekly schedules with a retention period of up to 14 weeks. It also notes that deleting the source database does not automatically delete its backups. Managed export and import writes to a Cloud Storage bucket you control, so it can be kept for as long as your bucket policy allows. Together these three give you minutes-back recovery for a week, regular snapshots for about three months, and long-term copies you manage yourself.

Which tool for which mistake

Rehearse a restore twice a year

A backup you have never restored is a hope, not a plan. Twice a year, restore the latest backup to a new database ID in your staging project, or in production under a clearly temporary name. Point a debug build or a script at it and check a few known documents, then delete the temporary database. Note how long the restore took and which steps the docs did not make obvious, such as IAM roles, TTL policies, indexes and security rules for the new database. Those notes are what you will need under pressure, when an alert from your cost and error monitoring tells you something went wrong.

Key takeaways

Sources

Operational guidance for indie developers—not a guarantee of zero data loss or free restoration. Confirm current Firestore PITR windows, scheduled backup retention limits, restore behavior, and schedule-export IAM in official Firebase / Google Cloud documentation for your projects. Last verified 2026-11-01.