Skip to content
  • There are no suggestions because the search field is empty.

Transitioning from Legacy Templates to the New Quotivity Templates: Things to Know

Summarizes the differences between the properties populated on quotes when using the legacy templates versus the new Quotivity templates.


When you switch from the legacy quote templates to the new Quotivity templates, the quotes themselves start populating different HubSpot properties than they did before. The new templates work exactly as designed — but anything in the rest of your HubSpot portal that was built around the old properties won't know about the change unless you update it.

This article covers what to review and adjust so your workflows, views, lists, and reports keep working after you enable the new templates. If you're looking for an overview of what the new templates are and what they offer, see our template overview articles instead — this one is specifically for customers moving from the old setup to the new one.

The short version: The properties that signal "e-signature is enabled" and "e-signature is complete" are different under the new templates. Update any automation or filter that relies on the old properties. During the transition, the safest approach is to have those automations recognize both the old and new properties at once.

E-signature properties

The most common place this trips people up is e-signature. If you have workflows, views, or reports that key off whether e-sign is enabled or a quote has been signed, note the property changes below.

What you're checking Legacy templates New templates
Is e-signature turned on? E-sign enabled is true E-Signature Status is known
Is the e-signature complete? Signing Status is Signed E-Signature Status is Completed

In other words, the new templates consolidate the signal into a single E-Signature Status property: its presence (being "known") tells you e-sign is active on the quote, and a value of Completed tells you the signature process has finished.

Updating your workflows

Any workflow that triggers or branches on the legacy e-sign properties should be updated to account for the new properties as well. Common examples are workflows that:

  • Move a deal to a new stage when a quote is published for signature
  • Mark a deal as closed won when a contract is signed
  • Update a custom property (such as an NDA or partner-agreement field) once a document is signed

Recommended approach during the transition: rather than replacing the old criteria outright, add the new criteria alongside them so a single workflow supports both template types at the same time. In practice this means adding a second enrollment/branch condition with OR logic:

  1. Open the workflow and locate the trigger or branch that references the old e-sign properties.
  2. Keep the existing condition (e.g., Signing Status is Signed).
  3. Add a new OR condition for the new property (e.g., E-Signature Status is Completed).
  4. Save and test.

With both conditions in place, quotes created on either the old or the new templates will continue to enroll and fire correctly. This matters because quotes already in flight on the old templates won't retroactively switch — so you'll likely have both types in your system for a while.

Once you're confident every quote has moved to the new templates, you can remove the legacy conditions if you want to tidy things up, but there's no harm in leaving both in place.

Updating views, lists, and reports

The same property swap applies anywhere else you've filtered on e-sign status:

  • Saved views / board filters on your quotes or deals
  • Active or static lists built on the old properties
  • Reports and dashboards that segment or count by e-sign status

Review each of these for references to E-sign enabled or Signing Status, and update them to use E-Signature Status (adding it alongside the old property where the tool allows, so historical records still appear).

Quote and PDF links

Beyond e-signature, the properties that store the link to the hosted quote and the link to the quote PDF are also different under the new templates. Both sets are single-line text properties on the quote, but the new templates write to their own dedicated fields:

What it holds Legacy templates New templates
Link to the hosted quote Link to hosted Quote Quotivity Quote Link
Link to the quote PDF PDF download link Quotivity PDF Download Link

If you reference either of these — for example, in a workflow that emails a quote link, an internal notification, a sales email template, or a report — update those references to point to the new Quotivity Quote Link and Quotivity PDF Download Link properties.

Recommended rollout checklist

  1. Audit before you switch. Search your workflows, views, lists, and reports for anything referencing the legacy properties: E-sign enabled, Signing Status, Link to hosted Quote, or PDF download link.
  2. Add the new criteria alongside the old. Use OR logic so both template types are supported during the transition.
  3. Enable the new templates.
  4. Test with a real quote. Confirm your key automations still fire as expected on a quote created with the new templates.
  5. Clean up later (optional). Once every active quote is on the new templates, you can remove the legacy criteria.

If you'd like help identifying which of your workflows and views reference the old properties, reach out to our team — we're happy to review your setup and can keep an eye on things as you make the switch.