Skip to content
Book a Demo Open a Case

Salesforce apps by To A Finish

Four managed packages that run inside your own Salesforce org.

Simple Signature

Document creation and e-signatures in Salesforce

Address Verification

Clean, verify, and geocode Salesforce addresses

Highlighter

Colors, renames, or hides Salesforce fields

List Browse

Go from record to record without a trip back to the list

Get started

Install a TAF package, set it up, and give it to your users.

Implementation guides

Guides for all four apps are ready.

How-to articles

One article for each task

Book a demo

See a package in a live org

Compatibility

Editions and releases we support

Get help

Open a case. Our support team answers by email.

Open a support case

Our support team answers by email

Give us access

Let us sign in and see the problem

Support home

Guides, release notes, and the case form

Troubleshooting

Search by the error text you see

Documentation

We write these pages for Salesforce admins.

Implementation guides

Guides for all four apps are ready.

How-to articles

One article for each task

Change log

What changed in each release

Compatibility

Editions and seasonal releases

Simple Signature Address Verification Highlighter List Browse Support Book a Demo Staff
Simple Signature · How-to

Move your setup from a sandbox to production

This article shows each step of the task in Simple Signature.

Last updated 9 Oct 2026

Paid version only. These steps do not count in the setup progress.

A change set cannot carry most of the setup of Simple Signature. Do these steps in production by hand.

  1. Install Simple Signature in production.

    Install it from the AppExchange, as in Install Simple Signature. TAF support can also send you an install link.

  2. Check that both orgs run the same version.

    The version shows at the bottom right of the Configure page, and in Installed Packages. If the versions differ, ask TAF support to push the new version to production, or for a link to do it yourself. See Update Simple Signature.

  3. Turn on the paid version in production.

    Each org needs its own Upgrade Key. See Turn on the paid version.

  4. Set up the signature site and its connection, if you use requests.

    Do Set up the signature site and Connect the site to Simple Signature in production.

  5. Connect Google Docs, if you use it.

    Do steps 1 to 4 of Make a PDF template in Google Docs in production.

  6. Set the Configuration tab the same as in the sandbox.

    Type each value again. Click Save Settings. Only Site URL for Signature Requests is different: use the address of the production site.

  7. Move the experiences with Export and Import.

    In the sandbox, open the Experiences tab. Click Export. The browser downloads Experience.csv, with all your experiences.

    In production, open the Experiences tab. Click Import. Under Upload Files, pick the file. Click Upload. For each column, pick the matching Field and a Field Type: Experience for Experience Name and Description, Parameter for the others. Click Save.

    Then check each experience:

    • Each experience gets a new Experience ID in production. Change it everywhere you typed it, for example in the Sign button component, on record pages, and in Flows.
    • Import does not keep values with commas. Check the parameters fieldreadonly, hideblankfields, templates, and submissiontype. Type their values again.

    If the import fails, see Import of experiences fails.

  8. Move your own changes.

    Make them again in production, or deploy them with a change set: your own fields, Visualforce pages, Lightning components, actions, and Flows. TAF support can help with the deploy.

Applies to

Simple Signature 5.8.x, paid version. These steps come from the tested Simple Signature implementation guide, where they sit with the steps before and after them.

Was this helpful?

Related

Support

Still stuck?

Open a case, and paste the exact error text into it. Our support team answers by email.