TL;DR: To auto-fill contracts using Salesforce fields, you link each field in a contract template to a field on a Salesforce record. Create the contract from that record, and the customer and deal details fill in for you. Our Salesforce eSignature integration does this and saves the signed copy back to the record.
A deal is ready to close. The customer has said yes, and the opportunity in Salesforce is up to date. All that is left is the contract.
Yet a rep still copies the company name, signer email, price and start date into a Word file by hand. One wrong email address sends the contract to the wrong person, and the deal waits another day.
What does it mean to auto-fill contracts from Salesforce fields?
Auto-filling means your contract template pulls its details from a Salesforce record instead of from someone’s typing. You set up the links once, and every contract after that fills in on its own.
Think of a return address stamp. You make the stamp once, and every envelope gets the same correct address in one press. Field mapping works the same way, except each record supplies its own details.
In practice, the template holds the fixed contract wording. The blanks in it, such as the customer name or the deal amount, each point to a Salesforce field.
Which Salesforce fields are useful in contracts?
The fields that change on every deal are the ones worth mapping. The exact list depends on your contract type and how your Salesforce org is set up.
Customer and contact fields
These say who the contract is for and who signs it.
- Account name
- Billing address
- Contact name
- Signer email
Deal fields
Sales contracts and order forms carry details from the opportunity.
- Opportunity name
- Opportunity amount
- Close date
- Product or service details
Contract term fields
Some teams keep contract dates on the opportunity or on a custom object.
- Contract start date
- Contract end date
- Renewal date
Why does manual contract preparation slow teams down?
Typing the same details into each contract takes time and invites mistakes. Each mistake then costs a correction and a resend.
A rep may not know which field holds the right billing address. A manager may need to check that the contract amount matches the opportunity. Small checks like these add up across dozens of deals a month.
Copying by hand tends to cause these problems:
- Wrong customer or signer details
- Old prices or deal terms
- Missing contract dates
- The same data typed into two tools
Our Salesforce contract management webinar recap covers how teams send, track and manage agreements inside Salesforce.
How does Salesforce field mapping work?
You give each blank in the template a matching Salesforce field. After that, the template reads the value from whichever record you send from.
A typical sales contract might map like this:
- Company Name reads the Account Name field.
- Signer Email reads the email on the Contact record.
- Contract Value reads the Opportunity Amount field.
- Start Date reads a contract start date field.
Reusable templates are the base of this setup. Our page on eSignature templates explains how they work. You can also start from our free contract templates and adapt them.
How do you auto-fill a contract from a Salesforce opportunity?
Once your template is mapped, sending a contract takes a few clicks from the record. Here is the usual flow for a rep:
- Open the opportunity in Salesforce.
- Choose the contract template for this deal.
- Check the details that Salesforce filled in.
- Confirm the signer and send the contract.
- Watch the status on the record until it is signed.
Our step-by-step guide on how to send contracts from Salesforce with BoldSign shows each screen.
How does BoldSign auto-fill contracts from Salesforce fields?
We let you map fields such as contact name, email, account, amount and close date to BoldSign template fields. You create the template in BoldSign once, and your team reuses it on any Salesforce record.
Our cards work on leads, contacts, accounts and opportunities, and on custom objects too. Each record shows the contract status as it changes: sent, opened, signed, declined or expired.
The signed document saves to the matching record, under Notes and Attachments. A copy also stays in BoldSign. Our post on eSignature for Salesforce walks through the one-time setup.
What should you check before you auto-fill contracts?
Auto-fill copies whatever sits in Salesforce, mistakes included. A few checks before rollout keep bad data out of your contracts.
Clean the source data
Review the fields your templates depend on. An old address or a typo in an email on the record will appear in every contract built from it.
Pick one source per field
Billing details may sit on the account, on a quote or on a custom object. Agree which field your team trusts, and map only that one.
Use templates, not uploads
Mapped fields fill only from templates. A one-off file you upload goes out as it is, so keep a template for every contract you send often.
Test with real records
Send a test contract to yourself from a real opportunity. Look for empty fields, odd date formats and the wrong signer.
Keep the template set small
A few approved templates are easier to keep current than many near copies. For a nondisclosure agreement (NDA), you could start from our confidentiality agreement template. Our guide to a Salesforce eSignature workflow shows where templates fit in the wider process.
Which BoldSign plan do you need, and what does the Salesforce add-on cost?
The Salesforce integration is a paid add-on on the Business and Premium plans only. Prices are in USD, billed yearly, as listed on our Salesforce integration page in November 2026.
On the Business plan, you pay $15 per user a month plus a $10 Salesforce add-on per user a month. On the Premium plan, you pay $99 a month for unlimited users plus a $21 add-on a month for the organization.
The Premium plan has a cap of 250 envelopes a month, and the Business plan has none. Our pricing page lists every plan, and you can try one with a 30-day free trial.
How do you start auto-filling contracts from Salesforce?
The quickest test is one mapped template and one real opportunity. Pick a next step:
- Start a 30-day free trial and map your first template.
- Book a demo to see field mapping on your own records.
- Read how to track contract status in Salesforce once your contracts are out.
Frequently asked questions
How do I auto-fill contracts from Salesforce fields?
Map each field in a contract template to a field on a Salesforce record. Then create the contract from that record, and the mapped values fill in for you.
What Salesforce fields are useful for contracts?
Start with the fields that change on every deal. Account name, contact name, signer email, deal amount and close date cover most sales contracts.
Do mapped fields fill a document I upload?
No. Mapped fields fill only from BoldSign templates. A one-off file you upload goes out as it is, and you place its fields by hand.
Which Salesforce records can I send contracts from?
You can send from leads, contacts, accounts and opportunities. Our cards also work on custom Salesforce objects.
Where do signed contracts go in Salesforce?
Each completed document saves to the matching Salesforce record, under Notes and Attachments. A copy also stays in your BoldSign account.
Is a contract auto-filled from Salesforce legally binding?
Yes, when it meets the usual rules for electronic signatures, such as the signer agreeing to sign electronically. Auto-fill only types the details in. It does not change how the signature works.
Can I see if a customer opened the contract?
Yes. The record shows each status as it changes: sent, opened, signed, declined or expired. Only the sender can remind or revoke a request from the record.
How much does the BoldSign Salesforce add-on cost?
It costs $10 per user a month on top of the Business plan, or $21 a month per organization on top of the Premium plan. Prices are in USD, billed yearly.