Why old data doesn't update when you edit a Custom Question

Why edits don’t migrate old data

A Custom Question’s answers are captured against the question’s structure at the moment of capture. If a consumer answered “Single-select: A / B / C” yesterday, and you change the question today to “Single-select: A / B / C / D / E,” yesterday’s answer is still tied to the original three options.

This is by design:

• Data integrity — automatically rewriting old answers to new structures could change the meaning of the data without the consumer’s consent.
• Audit clarity — what the consumer agreed to (and what you can prove they answered) shouldn’t change after the fact.
• Reporting honesty — comparing trends over time requires that historical answers stay as they were.

What edits apply forward

These edits affect new answers but leave old answers untouched:

• Renaming the question prompt
• Adding new options to a select
• Removing options from a select (old answers remain even if the option is no longer offered)
• Changing visibility modifiers
• Adjusting validation rules

What edits could break old data

Some edits would create ambiguity if applied retroactively, so they don’t:

• Changing the input type (e.g. text to numeric)
• Changing scope (per-Submission to per-Vehicle, etc.)
• Removing inputs entirely

If you make any of these changes, old Submissions retain the original structure. New Submissions use the new structure. The two coexist — exports and reports may show some old-shape and some new-shape data.

When to edit vs build new

Edit when:

• Fixing typos or improving wording
• Adding new options to a select
• Tightening or loosening validation
• Updating visibility modifiers

Build a new Custom Question when:

• The meaning of the data changes (you’re really asking a different question)
• The input type changes
• The scope changes
• You need a clean break in reporting

For “build new”:

1. 1

   Create the replacement Custom Question with the new structure.

2. 2

   Publish it. (Make sure you have a slot under your plan limit.)

3. 3

   Attach it to the Forms that need it.

4. 4

   Archive the old Custom Question to keep your published count clean.

5. 5

   Past Submissions retain their old-shape data; new Submissions capture the new shape.

Migrating old answers (manual)

If you absolutely need historic answers in the new shape, a manual migration is the only path:

• Bulk-export Submissions with the old data.
• Transform externally (e.g. in a spreadsheet) into the new shape.
• Either reconcile in your downstream system or contact support to discuss bulk update options.

This is not common — most agencies live with mixed-shape historic data and just go forward cleanly.

Common questions

Can I see what version of the question a particular answer was captured under? The Submission’s data retains the structure as captured. There’s no separate “version 2.3.1” label, but the structural details are preserved alongside the answer.

If I rename a select option, does the answer text update? The new label appears wherever the question is displayed; the underlying answer reference stays consistent. So yes, in display, but the captured answer ID is anchored.

What about exports — will old and new data look different? Yes. Old answers reflect the structure at capture; new answers reflect the current structure. Mixed CSVs need careful interpretation if structure changed.

Is there a way to “freeze” a published Custom Question to prevent edits? Not directly. The cultural pattern is: don’t edit a published Custom Question without a clear reason. For structural changes, archive and replace.