Import in Studio
On a table’s Data tab choose Import. The wizard has three parts. 1. The file. A CSV needs a header row. A JSON file is an array of objects. Up to a few hundred thousand rows works in the browser. Columns are matched to the table’s columns by name. 2. What to do with a row that already exists.
3. Events. Run events, flows and realtime for each row is off by default: a bulk import should not send a welcome email for every row. Turn it on only when you want each row to behave like a normal create.
Use dry run first: it validates every row against the column rules and reports a Row and Problem for each failure without writing anything. Then run it for real. Large files go in chunks, and the report shows how many rows were created, updated and failed.
Export
Studio: Export table downloads every row (CSV or JSON). Code: For a full environment (data, definitions and users together), use Backups.Move data between environments
Remember: definitions move with promote; data moves only when you export and import it. Never copy real customer data into a development environment without anonymising it.Seeding
Keep a seed script in your repository, usingimportRecords with mode: "upsert" and a stable key. It can be re-run safely: existing rows update instead of duplicating.
Common problems
Bulk writes
From your app.
Backups
Everything at once.