Upgrade to Salesforce V2 Guide

We've rebuilt Qwilr's Salesforce integration. This guide walks you through moving across from the previous one. You can go at your own pace. Your current setup keeps working the whole time, both integrations run side by side, and you upgrade your Templates one at a time — there's no cut-over moment where everything has to switch at once.

In this article:

• Before You Start
• Step 1: Install the New Package and Add the Component in Salesforce
• Step 2: Connect the New Integration
• Step 3: Upgrade Your Templates
  • Where to find the button
  • Running the upgrade
  • What the upgrade moves
  • Variables that can't be upgraded
  • Quote products
  • What the upgrade leaves alone
• Step 4: Check Everything Works
• Frequently Asked Questions

Before You Start

• In Qwilr, you need to be an Admin. The Upgrade button only appears for Admins.
• In Salesforce, you need a user who can install packages and edit page layouts: typically a System Administrator.

What you'll do

1. Install the new Qwilr Proposals package and add its component to your Salesforce record pages.
2. Connect the new integration.
3. Upgrade your Templates.
4. Point your Automations at the upgraded Templates.
5. Check everything works.

Step 1: Install the New Package and Add the Component in Salesforce

The new integration is its own package, Qwilr Proposals. This is separate from the earlier Qwilr package, so the two install side by side and nothing about your existing setup changes. There's no in-Salesforce upgrade between them; you simply add the new one, and uninstall the old one whenever you're fully moved across.

Install the package, then add the Qwilr Proposals component to the record pages where your team uses Qwilr; Opportunities, for example. For the install links and the full walkthrough, see Salesforce V2: Installation Guide.

Step 2: Connect the New Integration

Go to Account Settings → Integrations in Qwilr, search for Salesforce, and select the tile marked New version; your existing tile is renamed Salesforce (old) and its logo turns grey, so you can tell them apart. Click Enable Salesforce and approve the connection in the pop-up, or Connect to sandbox to trial it against a sandbox first.

Step 3: Upgrade Your Templates

Each Template is upgraded on its own, from inside the Template. There's no bulk conversion, and no rush to do them all at once. Templates you haven't upgraded yet keep working with the old integration.

Connected to a sandbox? That's a good way to try the new integration before you commit, and everything except the Template upgrade works as normal. Follow Salesforce V2: Installation Guide to build a Template against your sandbox, add variables to it, and create Pages from your sandbox records. When you're ready to move your real Templates across, reconnect the integration to your production org and the Upgrade button appears.

Where to find the button

Open a Template that's still linked to the old Salesforce integration. The Upgrade button the banner at the top of the Template editor.

Running the upgrade

We recommend you duplicate (clone) the template first.

There's no one-click undo for an upgrade. You can move a template back to the old integration by changing its connected integration, but you'd then need to reassign its variables by hand. Keeping a duplicate (by cloning) is the best safety net. You can try upgrading the cloned template and test it first before upgrading the original template.

1. Open the Template.
2. Click Upgrade. Qwilr reads the Template and works out what it can move.
3. Review the summary. It lists the Variables that will be swapped and, if there are any, the Variables that can't be swapped. Expand either card to see them named as they appear in your Template.
4. Click Upgrade to confirm.

When it finishes, you'll see a confirmation telling you how many Variables moved and how many were left behind.

What the upgrade moves

• Variables in your content: swapped for their equivalents in the new integration.
• Variables in the Page title: swapped as well, so Pages keep naming themselves after their record.
• Quote products (for Opportunity templates): line items driven by Salesforce data carry across, including their fields.
• The Template's link to Salesforce: moved to the new integration. The record type doesn't change: an Opportunity Template stays an Opportunity Template.
• For users of the Smart Proposal Engine and Conditional Content (Scale accounts only)
  • Block logic: conditions built on Salesforce Variables are upgraded with the Template. Conditions built on anything else are left exactly as they are.

Variables that can't be upgraded

A few Variables may need attention by hand. The review screen names them before you commit, and the confirmation screen names them again afterwards:

• Fields that no longer exist in your Salesforce org: this is most common with variables typed by hand inside curly braces, where a small typo means the Variable never matched a real field. These often sit in Template titles, where they're easy to overlook.
• Fields belonging to a different object type: an Account variable in an Opportunity Template, for example.

These are left untouched in the Template rather than removed, so nothing disappears without you seeing it. Replace each one with its new equivalent from the variables panel, or delete it.

Quote products

Quote line items driven by Salesforce carry across with the Template, and so do the product variables inside them.

What the upgrade leaves alone

• Seller Form Variables are untouched. They aren't Salesforce Variables, so the upgrade doesn't affect them and Templates that use them upgrade normally.
• Account Variables are untouched for the same reason.
• Pages already created from the Template are not changed. See the questions below.

Step 4: Check Everything Works

In Salesforce, open the Qwilr Proposals component on a record and click Create new page. Your upgraded template(s) should appear in the list. Create a page and check the variables fill correctly.

You can also tell your templates apart in the Qwilr Template dashboard by the color (or lack there of) of the salesforce integration they're linked to. Templates linked to the new integration are in color and the ones linked to the legacy integration are in black and white.

Frequently Asked Questions

Do I have to move everything at once?

No. Upgrade Templates one at a time, whenever it suits you. Both integrations run side by side, so nothing breaks while some Templates are still on the old one.

Why can’t I see the Upgrade button?

Check that you're in a Template rather than a Page, that you have Admin access, that you can edit that Template, and that the new integration is connected to your production Salesforce org rather than a sandbox.

The button says "Learn more" instead of "Upgrade".

That means the new Salesforce integration isn't connected on your account yet. Connect it first — see Step 2 — and the button becomes Upgrade.

Can I undo an upgrade?

There's no one-click undo. A Template can be moved back by changing the integration it's linked to, but its Variables would then need reassigning by hand. Clone a template, upgrade that and test it before upgrading the original template.

Do my quote products carry across?

Yes. Quote line items driven by Salesforce data are upgraded with the Template, along with the product variables inside them. If any product content can't be moved, the upgrade warns you before you commit and leaves that content in place.

Will I lose my pages previously created with the old integration?

No, all pages created with the old integration will also be shown in the new Qwilr component so there is no loss of records of Qwilr pages.

What happens to the Automations assigned to a Template?

They keep running. Check each automation in Library → Automations still has the Templates you expect assigned to it.

Do I need to re-authenticate?

The new integration is a separate connection: an Admin connects it once in Qwilr, and each team member authorizes the Qwilr Proposals component once. Your old connection stays as it is until you disable it.

When will the old integration stop working?

We will retire it on 28 February 2027. Until then both integrations run side by side, so you’ll have until then to move across.

When should I disable the old integration?

Once you've connected the new one and upgraded the Templates you need, you can disable the old integration in your account settings. Uninstall the old Salesforce package whenever you're fully moved across.

Any questions? Don't hesitate to contact us at help@qwilr.com