Record the task behind the extension
Start with what someone actually does: request a quotation, choose an available appointment or find a download. One plugin may serve several tasks, while one task may depend on a theme, plugins and an external service. Create a row for each function rather than just each product name.
Record the page and role using the function, and who can approve a replacement. Mark inactive or uncertain elements. Do not uninstall an unfamiliar extension simply to tidy the list; it may store information or run background jobs that are invisible on the page.
Trace data and access through the chain
In a fictional booking journey, the website displays appointments, capacity lives in an external calendar and notifications use a separate service. Record where authoritative information lives, who owns the account and where the connection runs. Name responsible people, never passwords or API keys.
Separate content export from complete recovery. WordPress's standard WXR export contains content records and fields; it does not establish that every plugin's data, files, settings and connections can be reconstructed. Check the particular extension's documentation and test relevant restoration in a safe environment.
| Register field | Record | Example without secrets |
|---|---|---|
| Task and source | User action and where facts live | Select a time; external calendar |
| Data and storage | Required records and files | Booking ID and confirmation status |
| Account and runtime | Owner, access route and execution | Customer-owned account; server integration |
| Replacement decision | Retain, integrate, rebuild or remove | Keep calendar; new public view |
| Acceptance test | Observable success and failure | Confirmed reservation; occupied slot rejected |
Separate presentation from business rules
A visible calendar is not a confirmed reservation. A browser check for a required field does not replace server validation. Identify which rules must run on a server or external provider, and which information the website merely presents.
For an Astro solution, content source, publishing and dynamic functions need to be chosen together. WordPress can remain a content source in some arrangements. If the aim is to leave WordPress, that dependency needs an explicit replacement; a successful API request during a trial does not show that the old system can be switched off.
Give each decision a test and an owner
For every critical row, record starting state, task, expected result and where the outcome can be confirmed. Include failures: an occupied slot, denied access, a failed notification or a missing file. Use fictional data and authorized test accounts. A thank-you screen alone does not establish receipt.
The business owner should approve what the function means; the technical owner verifies its behavior. Uncertainties can be tested through a migration pilot before commissioning the full move. Keep the register version and update it when the solution changes so the team does not test an outdated assumption.