The form migration checklist: test before replacing the old form
Check fields, logic, delivery, mobile use, and links with a concrete acceptance worksheet before switching a live form.
Create the inventory
List the source form URL, owner, purpose, audiences, embed locations, confirmation copy, recipients, and connected workflows. Export existing responses if needed and document how long they must remain accessible. A form recreation does not automatically migrate historical responses.
Record each field’s label, type, required status, options, validation, and visibility rules. Screenshot each branch in the old form. A screenshot of the first page cannot capture controls that appear only after an answer.
Run the acceptance cases
| Test case | Expected behavior | Evidence to retain |
|---|---|---|
| Empty required field | Submission blocked with a clear message | Field and error screenshot. |
| Every conditional branch | Correct fields shown, irrelevant fields hidden | Answer path and observed fields. |
| Invalid email / unsupported file | Clear rejection without losing other answers | Error and retained values. |
| Successful test response | Correct confirmation and stored answers | Synthetic response ID and timestamp. |
| Notification / connected workflow | Expected recipient or destination receives correct data | Receipt or delivery evidence. |
| Phone and keyboard | Readable labels, reachable controls, usable submit | Device and navigation notes. |
Cut over deliberately
Keep the old form reachable until the new form has passed its acceptance cases. Change one known link or embed, verify the production destination, then update the remaining locations. Document how to restore the old destination if the new flow fails.
Use synthetic test answers. Do not submit real customer data merely to prove a migration. After testing, label or remove test responses so staff do not mistake them for customer requests.
Define who signs off
The form owner checks business wording, the operations owner checks delivery, and the person responsible for the site checks embeds and mobile behavior. A recreation score does not replace these decisions.
Check capabilities in the actual account. Do not assume a field shown in a builder means payments, integrations, or a regulated workflow is configured and ready.
Your checklist
0 of 5 reviewed. Progress stays in this tab; download the worksheet to keep notes.