Next step · What to do next

Back up my database before changes (and restore plan)

What you may see

I am about to change tables or data and I am afraid to lose customer data

Why this step

Changes to a live database cannot always be undone by code; a backup taken just before the change is the only sure way back.

Before you start

What plan is the database on, and does it already make automatic backups (read the plan page)?

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
Back up my database before changes (and restore plan)

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
Changes to a live database cannot always be undone by code; a backup taken just before the change is the only sure way back.

DO THESE STEPS, IN THIS ORDER
1. Explain which backup options my database provider offers (automatic daily, on-demand, point-in-time) and what each costs or needs; tell me to check the current plan details.
2. Give me the exact steps to take a backup right before a change (an export file stored safely outside the project), and how to restore it into a TEST database first.
3. For each change, write the migration and its rollback file, and the check that proves it worked; I run both myself on the live database.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- I have a dated backup file, I restored it once into a test database and the row counts match.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not run anything on the live database yourself.
- Do not put the backup file inside the project folder or Git.
- 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

Explain which backup options my database provider offers (automatic daily, on-demand, point-in-time) and what each costs or needs; tell me to check the current plan details.
Give me the exact steps to take a backup right before a change (an export file stored safely outside the project), and how to restore it into a TEST database first.
For each change, write the migration and its rollback file, and the check that proves it worked; I run both myself on the live database.

Do not do this

Do not skip the test restore.
Do not run anything on the live database yourself.
Do not put the backup file inside the project folder or Git.

Try another entry