Calculator migration
How to Migrate a Website Calculator Without Losing Leads or Attribution
A 24-point cutover runbook and twelve executed fixtures for replacing a hosted or embedded calculator while preserving formulas, routes, consent, CRM delivery and campaign context.
Direct answer
Migrate a website calculator as a versioned system, not as a visual embed. Inventory every route and placement, freeze the active formula and rule contract, export only data you are entitled to retain, rebuild the smallest equivalent workflow, and replay fixed fixtures through calculation, result, consent, CRM, follow-up and analytics. Keep the old URL where possible; otherwise use one direct permanent redirect and do not cut over until the displayed answer and downstream record reconcile.
Definition
A calculator migration is the controlled replacement of a published calculation workflow while preserving its documented inputs, formula version, result meaning, accessible interaction, consent state, lead-delivery contract and acquisition attribution.
Key findings
Verified 14 September 2026
- A visual rebuild is not an equivalent migration unless the formula, assumptions, validation, result explanation and downstream field contract also match.
- A stable public URL is the lowest-risk path; when it must change, one direct permanent server-side redirect is easier to verify than a chain.
- Consent and attribution are separate contracts: campaign context may survive the handoff, but it cannot create permission for contact or marketing.
- An immutable completion ID lets retries recover without duplicating a contact, CRM activity or message.
Why is calculator migration urgent when a hosted service closes?
Calculator Studio's official termination notice says the service closed on 1 September 2026, shared and embedded projects are offline, and users can access accounts only until 15 September before projects and accounts are deleted. It advises exporting spreadsheets and saving PDFs. This dated event demonstrates why a migration plan needs an inventory and retained contract before a hosted editor or embed disappears.
The notice does not establish that every calculator service has the same export path, and this guide does not recommend a replacement vendor. Confirm the current source system's own terms, export formats, deadlines and deletion behavior before acting.
What must be inventoried before rebuilding?
The migration inventory is the cutover control plane. Crawl each calculator route, then locate every iframe, script, pop-up, CMS block, email link, result page and campaign link that reaches it. Record the current canonical, response status, embed dimensions, title, formula version and downstream destination.
Do not assume the editor contains everything needed to recreate the experience. A live page may supply surrounding instructions, consent language, analytics parameters, responsive constraints or fallback content that the calculator export does not contain.
| Area | Checks 1–4 | Release evidence |
|---|---|---|
| Inventory | Crawl routes; find every embed; record canonical/result routes; preserve inbound campaign links | URL and placement register |
| Calculation contract | Save formula/version; record input schema; retain rounding and assumptions; create fixed fixtures | Independent input/output set |
| Interface and result | Preserve labels; preserve conditional state; preserve result explanation; test keyboard/zoom/mobile/updates | Published interaction review |
| Data and consent | Export only necessary data; map purpose/destination; separate consent; exclude personal data from analytics | Field and retention contract |
| Delivery and attribution | Use one completion ID; verify idempotent retries; map campaign context; gate follow-up on consented delivery | CRM and event reconciliation |
| Cutover and recovery | Keep URL or redirect once; replace every embed; monitor safe error signals; retain rollback target | Cutover and rollback record |
How do you preserve the calculation contract?
Freeze the exact expression, formula identifier and version, required inputs, units, defaults, validation, conditional formula selection, caps, exclusions, internal precision, display rounding and visible assumptions. Save expected results for typical, minimum, maximum, zero, invalid and boundary scenarios outside the builder.
A screenshot of a result is evidence of one display state, not a reproducible model. The replacement should produce the expected raw value and the same explained display value for every retained fixture before it receives production traffic.
What should the route, field and event contract contain?
The route contract identifies the canonical calculator URL, every legacy URL, the result behavior and the permitted redirect. The field contract maps normalized scenario inputs, formula and rule versions, raw and displayed results, consent state, source context and completion ID to the downstream record. The event contract uses non-identifying calculator, version and result-band parameters for measurement.
Google Analytics documents event parameters as contextual details attached to an event and provides Realtime and DebugView for verification. Do not place names, email addresses, phone numbers or unrestricted free text in analytics. Personal fields belong only in the consented workflow that needs them.
| Contract | Required fields | Failure that blocks cutover |
|---|---|---|
| Route | canonical_url, legacy_url, response, redirect_target | Missing page, chain, loop or irrelevant target |
| Formula | formula_id, version, expression, units, assumptions, fixtures | Unexplained output difference |
| Lead | completion_id, consent_state, required contact fields, result context | Lost, duplicated or unauthorized record |
| Event | calculator_id, formula_version, event_name, result_band, source context | Personal data or inconsistent attribution |
How should old calculator URLs and embeds be cut over?
Prefer keeping the existing public URL and replacing the calculator behind it. When a route must move, Google's current guidance recommends a permanent server-side 301 or 308 redirect and warns against redirect chains. Point each old route directly to its closest equivalent, preserve useful query parameters deliberately and keep the new page's HTTPS self-canonical consistent.
Replace every embed in a controlled list rather than searching only the main website. Verify the final container at narrow mobile width, 200 percent zoom and keyboard-only operation. A successful script request does not prove that the calculator is visible, labeled, sized correctly or capable of recovering from a blocked third-party request.
What did the twelve migration fixtures verify?
The executable reference gate evaluates five binary contracts: route availability, formula equivalence, CRM field completeness, explicit consent state and completion-ID continuity. The consent-declined path may publish a result but cannot start follow-up. All other missing contracts block cutover.
| ID | Changed condition | Expected and observed outcome |
|---|---|---|
| M01 | Complete contract | Ready — passed |
| M02 | Public route missing | Blocked at route gate — passed |
| M03 | Formula result differs | Blocked at formula gate — passed |
| M04 | CRM field contract incomplete | Blocked at field gate — passed |
| M05 | Consent state missing | Blocked at consent gate — passed |
| M06 | Consent declined | Result allowed; no follow-up — passed |
| M07 | Retry keeps completion ID | Ready without a new identity — passed |
| M08 | Duplicate changes completion ID | Blocked at idempotency gate — passed |
| M09 | Contact-free route with declined consent | Result allowed; no follow-up — passed |
| M10 | Contact-free route with formula mismatch | Blocked at formula gate — passed |
| M11 | Contact-free route with incomplete field contract | Blocked at field gate — passed |
| M12 | Final complete contract | Ready — passed |
Which failures should stop the release?
Block the cutover when a legacy route has no relevant destination, a fixed fixture changes without an approved explanation, a hidden stale value affects the model, the displayed unit or rounding differs, a retry can duplicate activity, consent is missing, attribution overwrites consent, or the published embed cannot be completed with a keyboard.
After release, reconcile a small set of completed scenarios across page result, CRM activity and event record. Keep the prior formula contract and rollback target until the team can explain every expected difference. Monitoring should use non-identifying status and reason codes rather than logging personal data.
Method and evidence
Evidence type: Reusable 24-point calculator migration runbook, route/field/event contract and twelve executed deterministic cutover fixtures
- Mapped a calculator migration across six independently testable surfaces: public inventory, calculation contract, interface, data and consent, delivery and attribution, and cutover recovery.
- Defined a fictional route, field and event contract with one immutable completion ID shared by the result, CRM activity and retry decision.
- Executed twelve deterministic fixtures that block release when the route, formula, CRM field contract, consent state or completion identity is not preserved.
- Checked current primary guidance and one dated service-termination notice without claiming a hands-on migration, a named replacement product or results for a real organization.
Topic score: 4.86 / 5. Business fit 5, verified demand 5, distinct intent 4.8, original evidence 4.9, citation usefulness 4.6, feasibility 4.5.
Primary sources
- Calculator Studio service termination notice ↗Official shutdown, offline-embed and export-deadline notice; checked 14 September 2026.
- Google Search Central redirects guidance ↗Primary guidance on permanent redirects and moved locations; checked 14 September 2026.
- Google Search Central site-move guidance ↗Primary guidance on server-side redirects and avoiding chains; checked 14 September 2026.
- Google Analytics event parameters ↗Primary guidance for event context and verification; updated 3 June 2026 and checked 14 September 2026.
- W3C Forms Tutorial ↗Primary guidance for labels, grouping, instructions, validation and notifications; checked 14 September 2026.
- ICO data-minimisation guidance ↗Regulator guidance to limit personal data to what is necessary; checked 14 September 2026.
Limitations
- The runbook validates a migration process, not a real organization's formula, contract, retention duty or regulated calculator.
- The Calculator Studio closure is a dated migration trigger, not a recommendation for or against a replacement product.
- The executed fixtures validate the deterministic reference gate, not a named calculator builder, live CRM, email provider, browser or assistive technology.
- Redirects and crawlable discovery signals do not guarantee search indexing or preservation of rankings.
Verification and corrections
Current shutdown, redirect, analytics, accessibility and data-minimisation guidance plus twelve deterministic cutover fixtures verified 14 September 2026.
Recommended retest: Recheck source-system availability, export deadlines and every public placement before cutover; replay the complete contract after formula, route, embed, field or event changes.
Found an error or a changed standard? Use the correction process and include the page URL and primary evidence.
Next step
Apply the evidence to your next release
Use the published method, keep a dated test record and revisit the result after the calculator or its operating rules change.
Open the testing protocol