Migrating from DocuSign
TrueSign covers the full feature set of DocuSign eSignature for Salesforce — templates, merge fields, writeback, bulk send, signing groups, document generation. This page gives the concept mapping and the switch-over procedure.
Concept mapping
| DocuSign for Salesforce | TrueSign | Notes |
|---|---|---|
| Envelope | Signature request (TES_SignatureRequest__c) | Equivalent statuses (Ongoing, Done, Voided → Cancelled…) |
| Envelope Configuration (template) | Envelope Template (TES_EnvelopeTemplate__c) | 6-tab editor: Documents → Recipients → Merge Fields → Place Fields → Options → Custom Button |
| Recipient Status | Signer (TES_SignatureRecipient__c) | Individual status, signing date, audit |
| Merge Fields | Merge fields | Text, currency, date, address, related list, checkbox, formula |
| DocuSign Connect | TrueSign Connect | Writes signer-entered data back to Salesforce |
| DocuSign Gen | TrueSign Gen | Word → PDF generation with {{Object.Field}} tags |
| Signing Groups | Signing groups | The first member who signs validates for the group |
| In-Person Signing (Sign Now) | In-person signing | Host + on-device signing, no email |
| Bulk Send (CSV) | Bulk send | Salesforce-native, no CSV file: selection from a List View |
| Custom Buttons | Custom buttons | Quick Send, embedded, fixed template or free mode |
| Jobs & Logs | Jobs & Logs | TrueSign Logs tab, configurable retention |
| DocuSign account (per-envelope billing) | Yousign account (usage-based billing) | EU hosting — see GDPR & data residency |
Worth noting for operations: TrueSign only makes outbound calls to Yousign — no inbound IP restrictions to configure, unlike DocuSign.
Carrying your configuration over
The switch-over is done manually, template by template, following the checklist below. The package ships migration components, but no screen exposes them today (verified on version 1.22: no tab, no entry in TrueSign Setup). Don't go looking for an "Import from DocuSign" button.
For each DocuSign Envelope Configuration, note what has to be carried over into the TrueSign template:
| Note in DocuSign | Re-create in TrueSign |
|---|---|
| Attached documents | Template's Documents tab |
| Roles and signing order | Template recipients tab (recipient source, sequential order) |
| Merge fields / tags | Merge Fields tab (label, Salesforce field, type, placement) |
| Information sent back to Salesforce | "Signer fills it, and it returns" behaviour — see TrueSign Connect |
| DocuSign buttons on objects | Custom buttons to re-create in App Builder |
Switch-over checklist
- ☐ Connect Yousign and validate Test Connection (TrueSign setup).
- ☐ Configure the webhook + HMAC secret.
- ☐ Inventory the DocuSign Envelope Configurations worth keeping (many are usually obsolete — a good moment to prune).
- ☐ Re-create each template in TrueSign using the table above.
- ☐ Test each template on a test record (send + sign + writeback).
- ☐ Re-create the buttons on Lightning Pages (App Builder).
- ☐ Assign the TrueSign permission sets to users (
TES_User,TES_BulkSendUser…). - ☐ Switch Flows / NBA over to the TrueSign invocable action.
- ☐ Let in-flight DocuSign envelopes finish in DocuSign — TrueSign does not take over requests already sent.
- ☐ Uninstall DocuSign once the overlap period is over.
DocuSign and TrueSign can stay installed side by side for the whole switch-over: the namespaces are separate and nothing conflicts. So you can migrate gradually, template by template, with no downtime window.