IMPORTANT NOTE: This feature is available to accounts subscribed to our Business Plan. Is this feature the answer to all your problems? Our sales team can get it added to your plan ASAP!

Need a quick answer? Here's what this article covers:

Introduction To Field Mapping

Field mapping links fields between Salesforce and Proposify. Once mapped, your Salesforce Opportunity, Contact, or Account fields will link to a Proposify custom field or variable of your choosing. Here’s how they link:

Salesforce Objects

Proposify Fields

Client

Client Contact

Account

Client Company

Opportunity

Proposal

Once linked, if you've made changes to the linked Object in Salesforce we’ll match them in Proposify documents.

HEADS UP: Only an account owner will be able to see this. We do this to help keep your fields consistent and ensure there are no unexpected changes. Not sure who the account owner is? You can find that listed in the Users page. Their image will have an account owner tag:

Mappable Fields

You can map Salesforce fields to Customer, Proposal, or Company fields in Proposify. The field types we currently support are:

  • String (letters and numbers up to 255 characters)

  • Date

  • Date/Time

  • Number (up to 18 characters)

  • Medium text

  • Email addresses

  • URLs

If you’re using a number field, we'll strip the formatting when pulled into Proposify. For example, if your number field in Salesforce has 1,547,999 it will import to Proposify as 1547999.

Entering the Field Mapping Menu

You can find the Field Mapping Menu from Salesforce Settings. To reach this page,

  1. Click Integrations from the Navigation Bar.

  2. Click Salesforce.

  3. Click the Map Fields tab.

  4. Click on the Salesforce object you wish to map to a Proposify field.

The Field Mapping Menu:

Here’s the place where you can map your standard and custom fields from Salesforce to Proposify. Here’s a breakdown:

Salesforce Field

  • This dropdown pulls your current list of fields and allows you to map them to Proposify.

Proposify Field

  • This represents custom fields in Proposify, some default fields will already exist and can be mapped and others will need to be created to accommodate your Salesforce fields.

HEADS UP: Sometimes you won’t see a custom field in the Proposify Field menu. If that’s the case, select Create a new custom field from that same dropdown menu.

Menu Button

  • The ellipses menu provides some extra options for this mapping. You can remove the mapping, edit the Proposify custom field, or delete that custom field entirely.

NOTE: If you are in the Opportunity/Document field mapping menu, an additional Field Groups menu will appear on the right. Click the + button to create field groups that can be assigned to your templates.

Mapping Salesforce Fields To Proposify

Mapping an existing field:

  1. Navigate to Integrations, then click Salesforce

  2. Click Map Fields

    1. If you are in the Opportunity/Document menu, select a Field Group preset. Choose either an existing group or click the + next to Field Groups to create a new one.

  3. Click Map a field

  4. Expand the Salesforce Field dropdown, then select the field to be mapped.

  5. Expand the Proposify Field dropdown, then select an existing Proposify custom field

  6. Click Save Settings to confirm your changes.

If the selected Salesforce field is supported by Proposify, then the Proposify custom field will appear in the dropdown.

HEADS UP: Once a field is mapped, you will no longer be able to edit that field in Proposify. This keeps the Salesforce Opportunity as the “source of truth” and prevents conflicts between your sales document and your opportunity.

Create a new mapped field

If you’d like to create a new field mapping for your sales document:

  1. Navigate to Salesforce SettingsMap Fields and click Opportunity / Document Fields.

  2. Select the preset group and click Map a field.

  3. Expand the Proposify Field dropdown and select Create a new custom field

  4. Create the new custom field (which will be the variable to populate in your documents) and click Save.

  5. Main Competitors will now be available to map.

HEADS UP: Once a field is mapped, you will no longer be able to edit that field in Proposify. This keeps the Salesforce Opportunity as the “source of truth” and prevents conflicts between your sales document and your opportunity.

Editing Existing Fields

If you need to make changes to your mapping, expand the dropdown for the field you would like to change, then choose the new field.

Once you've updated your mappings, click Save Settings once again. This will re-map these fields and will affect all new proposals.

HEADS UP: Re-mapped fields will not affect existing documents until you click Update This Connection in Document Settings or update the field in Salesforce.

Removing Mapped Fields

If you need to remove a mapped field from your page, expand the three-dot menu next to the field and select Remove Mapping:

Once you've pared down your mapped fields, click Save Settings to confirm your changes. Any existing proposals will keep their old text, but will no longer sync.

Assign A Mapping to a Template

You can create multiple Opportunity/Document field groups and assign them to templates, enabling a more varied workflow based on the document being sent to your prospect. To assign a field group to a template, navigate to the Template Editor. From there:

  1. Expand the Template Settings Menu.

  2. Click Mappings.

  3. Expand the Assign to your template menu under Mapped Fields, then select the field grouping you wish to assign to this document.

Finally, click Save Settings to confirm your choices.

Updating Proposals To Changed Mapping

When you made changes to your Salesforce entity (Account, Contact, Opportunity), we’ll apply those changes to the mapped fields in your document.

If you’re looking to update your mapped fields directly from the Proposify document, you can do so from the Document Editor.

Once in the Editor, click Sync Document Data from the menu pane:

This will pull all opportunity details and update all mapped fields within this document.

Did this answer your question?