I spent 2 months developing a custom quote template on the legacy quote system.
Now I have been force migrated to the new quote system and all of our work is gone. This is delaying our migration and incredibly frustrating. Support is unsure if we can use what we have built, I do not get straightforward answers from them.
Has anyone else ecountered and/or solved this issue? I deleted all templates with the new system but still can not use my custom legacy quote
Hi there @UserZ
Thanks for sharing your post!
I’d love to get some extra eyes on this from folks in the Community who’ve dealt with legacy quotes or similar migration hiccups. Hi @d-lupo @ChristinaKay @Nagarjoon hope you’re having a great week! do you have any tips to share with?
If anyone else has run into this before or found a workaround, your experience could really help here.
Victor
Hi @UserZ , unfortunately yes, I’ve seen this happen a few times, and your frustration is completely justified.
The short and painful truth is that legacy quote templates cannot be re-enabled once a portal is force-migrated to the new Quotes tool.
Deleting new-style templates does not restore access to legacy quotes, because the migration is account-level, not template-level. Once HubSpot flips that switch, the legacy quote editor is effectively retired for that portal.
What sometimes helps, depending on timing, is checking whether HubSpot Support can temporarily roll the portal back if the migration was very recent and not fully completed. This is rare and time-sensitive, and Support will usually escalate it internally if it’s even possible. If they haven’t already, ask explicitly whether a rollback to legacy quotes is technically still an option, not just whether legacy templates can be reused.
If rollback is not possible, the only supported path is to rebuild the template in the new quote system, using custom modules and CSS. The good news is that the new quote editor is more flexible long-term, but the bad news is that legacy HTML cannot be imported 1:1. HubSpot documents this limitation pretty clearly now, though it’s easy to miss until you hit it (Manage quotes )
One practical workaround I’ve seen teams use is to extract the legacy HTML and CSS you built and reuse chunks of styling logic inside custom quote modules, instead of starting from zero conceptually. It’s still work, but it saves design thinking time even if it doesn’t save build time.
If this migration blocked an active rollout, I would also strongly recommend posting this in the Ideas forum or pushing Support to log it as feedback. HubSpot has been tracking quote migration friction closely, especially for RevOps-heavy portals (https://community.hubspot.com/t5/HubSpot-Ideas/idb-p/HubSpot_Ideas )
hopefully this gives you clarity instead of more ambiguity.
Agreed with @RubenBurdin on all points.
Additionally, HubSpot could really improve this by:
1) giving a visible ‘last chance’ banner before permanently switching off legacy quotes, and
2) providing a guided rebuild or template-conversion assistant for complex portals.
Hey Ruben, is it possible to actually modify the HTML & CSS of quotes in the new CPQ system in Design Manager? From what I’ve seen, you can’t, and I haven’t seen any documentation saying you can.
If you can, can you point me in the right direction?
Thanks,
Chris
Hey @chris-profitpad - thanks for following up here!
Re-tagging @RubenBurdin to ensure he sees this question!
Shane, Senior Community Moderator
Hi Chris,
I actually haven’t explored the new tool very much. After making a lot of noise support helped me go back onto the legacy tool.
Best of luck!