firestore-migration

To migrate local mock data to Firestore, you use a batch processing action triggered by a Migrate to Firestore button in your app, transferring in-browser memory records directly to cloud collections. This enables cloud-backed development and testing.

Moving in-browser memory data to Firestore collections involves executing a single-action batch process that exports local mock data, such as crew and bills, to the cloud, providing UI indicators and a confirmation toast upon successful migration.

Yes, you can batch process larger datasets when migrating from offline to Firestore. The migration workflow supports handling substantial record sets, such as migrating 145 crew records, directly from local memory to cloud collections in a single action.

Yes, switching from local mock data to Firestore requires your app to expose a Migrate to Firestore button in the sidebar. Upon success, the workflow requires UI indicators showing Firestore Connected and a migration confirmation toast.

Exporting local mock data supports migrating to specific Firestore collections including crew, bills, payments, slips, and crewPayments. These collections are targeted during the batch processing transfer from in-browser memory.