Moving the form is usually easier than moving the history. You can rebuild a template, test it, and publish a new signing link. Years of signed records are a different problem: they need to remain findable, readable, and connected to the information that explains what was signed.
Treat a provider switch as two coordinated projects. One moves future signing to the new system. The other preserves access to existing records. Completing the first does not prove you have completed the second.
Inventory what the old account actually holds
Before scheduling a cutover, inspect the export options in your current provider. Do not assume that a button called “Export” includes every record, attachment, historical version, and audit detail.
Write down the types of information you need to preserve and where each one can be obtained. Include signed documents, participant and guardian associations, timestamps, record identifiers, and any supporting files your process collects. Check whether a CSV is just an index or contains the answers themselves. Check whether PDFs include the agreement as signed rather than only the current template.
| Export item | Question to answer before leaving |
|---|---|
| Signed PDFs | Do the files contain the correct agreement and completed signing information? |
| CSV or record index | Which stable identifier connects an index row to a document? |
| Attachments | Are these included, separate, or unavailable through the normal export? |
| Version information | Can you identify the wording associated with a historical signature? |
| Audit information | What can be exported, and what remains accessible only in the old account? |
| Location or event references | Will the receiving team understand the names and identifiers? |
Ask the provider about anything missing before closing the account. Keep the answer with your migration notes. An assumption about what remains available after cancellation is not a preservation plan.
Prove that someone can retrieve a record
Downloading a ZIP is the beginning of verification. Extract it, open files, and test the relationship between the index and the documents. Use a controlled storage location with access limited to the people who need it.
Choose samples across the situations your business actually has: an older form version, a family submission, different locations, and records with attachments. Include any unusual cases you know may export differently. A sample does not prove every file is correct, but it can expose problems that a successful download message will not.
Record total counts and explain differences. One submission may list several minors, so the number of people is not necessarily the number of PDFs. An attachment may create another file without representing another signed waiver. Compare like with like rather than forcing every total to match.
Then give an authorized colleague a retrieval task without telling them the filename: “Find the record for this test reference and confirm which agreement was signed.” If they cannot follow the index to the document, improve the archive organization before relying on it.
The downloaded PDF archive checklist provides a shorter verification routine. Download the migration register (CSV) to track export batches, counts, missing items, review owners, and unresolved actions. The register is a planning sheet, not a bulk import format.
Keep historical records separate from editable templates
A signed document is evidence of a completed interaction. An unsigned master is the starting point for future interactions. Mixing those purposes makes both harder to manage.
In Waiver.com, PDF, DOCX, and pasted-text template imports create editable builder content. That does not mean a folder of historical signed PDFs automatically becomes native signed records in your new account. Confirm the available migration path for historical records before planning around it. An accessible external archive may be part of the transition, depending on your needs and the available export.
Build future templates from approved unsigned sources. Do not delete a customer's signature from a historical PDF and treat the result as your master. Follow the document import review process, then test the new signing flow with clearly identified internal data.
Preserve original historical files when cleaning up filenames or indexes. If you create a new index for staff convenience, keep the relationship to the original identifiers and document the changes. Do not rewrite agreement text inside old records to make it match your new template.
Define the signing cutover precisely
“Switch on Monday” is not precise enough if several people update different links. Agree on a date, time, and time zone. List every place someone can start signing: your website, booking messages, QR posters, kiosk devices, event invitations, and saved staff shortcuts.
For each location, assign an owner and a verification step. After replacing a link, open it as a guest and complete the relevant test. Keep a record of which old links may still be circulating in already-sent messages.
Plan for three groups:
- People who signed before cutover. Explain how staff will find and assess those existing records under your approved policy.
- People who started near cutover. Decide where staff will check if the customer says they completed a form during the transition.
- People who sign afterward. Confirm the new record appears where the desk expects to find it.
A software change alone should not lead staff to make up a new rule about whose waiver is valid. Whether someone needs to sign again depends on your approved agreement, activity, and operating policy. Make that decision before the queue forms.
Limit unnecessary copies of customer data
Migration can create temporary copies on laptops, in email attachments, and in shared folders. Keep a list of those copies and an owner for cleaning them up once the verified archive is in place.
The FTC recommends knowing what personal information a business holds, limiting unnecessary collection and retention, and restricting access. Apply that principle to the migration itself: the people checking filenames may not need access to every sensitive answer. See the FTC guide to protecting personal information.
Do not adopt a universal retention period from a software blog. Set retention and deletion requirements with the people responsible for your legal, insurance, and business obligations. Account closure, ordinary cleanup, and a preservation requirement may need different treatment.
Close the old account only after the handoff works
Before cancellation, confirm that the final export is complete, unresolved gaps have an agreed answer, and authorized staff can retrieve the records they need. Verify the new signing links and the process for finding pre-cutover records. Keep the provider's account-closure terms with your notes.
If something fails during cutover, staff need a specific fallback: who makes the decision, which approved signing route to use, and how to reconcile submissions afterward. Avoid switching links back and forth without recording what happened.
Waiver.com's record export tools are also worth reviewing while choosing a system. Planning how you could leave a provider later is a practical way to evaluate how well you will control your records today.
Migration questions
Can I cancel the old provider as soon as the new form works?
Wait until you have verified the historical exports, resolved missing items, and confirmed the terms for access after cancellation. A functioning new form does not establish that the old records are safely available elsewhere.
Do all customers need to sign again after we switch?
That is not automatically determined by the software change. Follow the requirements of your approved agreement and business policy. Give staff a clear process for checking older records and identifying situations that require a new signature.
Is a CSV enough to preserve signed waivers?
Not necessarily. It may contain only an index or selected answers. Check what it includes and how it relates to signed documents, versions, attachments, and audit information. Verify the actual export rather than relying on the file extension.