Next step · What to do next

Import and export data (spreadsheets) safely

What you may see

I have my products or customers in a spreadsheet
I need a report in Excel

Why this step

Imports are the easiest way to damage data in bulk; a safe import validates, previews and can be undone, and an export must not leak more than the person may see.

Before you start

Which columns and rules (required, unique, allowed values)? Who may import or export?

The prompt for this step

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

Any error or warning you see now

What you have now (tool, framework, where it is hosted)

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a senior engineer and careful product advisor who builds small business websites and apps, and explains every step to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

WHAT I WANT NEXT
Import and export data (spreadsheets) safely

ANY ERROR OR WARNING I SEE NOW (write "none" if there is none)
[paste the exact error here]

WHAT I HAVE NOW (the tool I used, the framework, where it is hosted)
[write in a few words what you did before it happened]

WHY THIS STEP
Imports are the easiest way to damage data in bulk; a safe import validates, previews and can be undone, and an export must not leak more than the person may see.

DO THESE STEPS, IN THIS ORDER
1. Define the file format with a downloadable template (headers, example row, UTF-8 so Arabic is kept).
2. Import in two steps: upload and validate everything (show errors with row numbers), then show a preview of what will change, and apply only after confirmation in one safe transaction; keep a copy of the file and a way to undo.
3. Export only what the role may see, protect against spreadsheet formulas (cells starting with =, +, -, @), and keep amounts with three decimals.
4. Test with a file that has Arabic text, bad rows, duplicates and a very large size.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- Bad files are rejected with row-level messages, a good file previews and applies once, and Arabic text is intact.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not import on the live database without a backup.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Define the file format with a downloadable template (headers, example row, UTF-8 so Arabic is kept).
Import in two steps: upload and validate everything (show errors with row numbers), then show a preview of what will change, and apply only after confirmation in one safe transaction; keep a copy of the file and a way to undo.
Export only what the role may see, protect against spreadsheet formulas (cells starting with =, +, -, @), and keep amounts with three decimals.
Test with a file that has Arabic text, bad rows, duplicates and a very large size.

Do not do this

Do not run formulas from imported cells.
Do not import on the live database without a backup.

Try another entry