How to migrate from DocuSign to Documenso
Move from DocuSign to self-hosted Documenso: archive signed envelopes, check signature levels, rebuild templates, rewire the API and let open envelopes finish.
In short
- Nothing in DocuSign imports into Documenso: completed envelopes are archived as PDFs with their certificates of completion, and templates and integrations are rebuilt.
- The Documenso Community Edition signs at the simple level; advanced and qualified signatures need a trust service provider and an Enterprise Edition licence, for the whole instance.
- Bulk export of completed envelopes runs through DocuSign Retrieve, a paid add-on, Connect’s manual publish, or the eSignature REST API, which downloads each envelope with its certificate.
- Envelopes already out on the cutover date finish in DocuSign, and the account closes once the last one is back and exported.
On this page (10)
Moving from DocuSign to Documenso is an export plus a rebuild. Nothing in DocuSign imports into Documenso: completed envelopes are exported with their certificates of completion and archived as they are, templates are set up again, and every system that calls the DocuSign API or waits for its Connect notifications is rewritten. Before any of that, one question shapes the plan: which of your processes need an advanced or qualified signature, because the Community Edition of Documenso signs at the simple level. This guide covers the order we run it in, and the places it usually goes wrong.
Why teams move from DocuSign to Documenso
Three reasons come up again and again.
- Where the contracts end up. Every DocuSign envelope, with its documents and audit trail, is stored by DocuSign. With Documenso on your own machines, the sealed PDFs sit in a bucket and the audit log in a PostgreSQL database, in the location you choose.
- Features that follow the plan. On DocuSign’s own plan comparison, PowerForms, bulk send and its APIs start at Business Pro. The Documenso Community Edition has templates, direct links, bulk send from a template, the API and webhooks, with no fee per user or per document on your own infrastructure.
- Your name on the seal. Documenso seals every completed PDF with a certificate that belongs to your instance, issued to your organisation, so the signature panel of a PDF reader names it, and any later change to the file breaks the seal.
What you give up is real. DocuSign can verify signers’ identities with ID Verification; Documenso has no identity verification built in, and re-authentication with a passkey or two-factor code before signing is a commercial feature. DocuSign also offers advanced and qualified signature types in the same account as simple ones, a catalogue of prebuilt connectors, and the fact that someone else runs the platform.
Step 1: list templates, integrations and signature levels
The archive is the easy part. What takes time is finding everything that still depends on DocuSign, so start there.
- Templates in use. The eSignature REST API lists templates with
GET /accounts/{accountId}/templates, and itsused_from_dateparameter returns only those used or edited since a date. Download the ones you keep: on the Templates page, the template actions menu has Download, and for several templates the More actions menu downloads a ZIP. Each JSON file holds the documents, recipient roles, routing order and fields, and it is the specification you rebuild from. - PowerForms. From Agreements, the PowerForms folder in the left panel lists them, and the API (
GET /accounts/{accountId}/powerforms) returns each one’s URL, template, number of uses and last use. Every PowerForm URL is published somewhere, on a website, an intranet page or in an email template, so note where. - API integrations. In eSignature Admin, Integrations, Apps and Keys lists the integration keys promoted to your account. Name the system and the owner of each. Connectors sold by another vendor, such as a CRM’s DocuSign integration, are found by asking each system owner.
- Connect. Account-level Connect configurations are listed under Integrations, Connect, or through
GET /accounts/{accountId}/connectby an account administrator. Record each listener URL, the events it subscribes to and whether it receives the documents. Envelope-level notifications are set by an integration in each envelope request, so they are found in that integration’s code, not in the admin. - Signature types and signer checks. For each template, record the signature type of every signer and how signers are authenticated. DocuSign’s types are the default electronic signature, DS Email Signature, EU Advanced, EU Qualified, and signatures through a trust service provider. A signer set to anything other than the default electronic signature, or verified with ID Verification, is a process that step 2 has to decide on.
Each line ends with a decision: rebuild, replace or drop. A template nobody has used in a year is usually dropped.
Step 2: decide which processes keep an advanced or qualified signature
Most contracts carry no form requirement, and for them a simple electronic signature with a sealed PDF and an audit trail is what DocuSign provided too. Some processes are different, and the law draws the line.
- In Switzerland, only a qualified electronic signature linked to a qualified electronic timestamp has the legal effect of a handwritten signature (Art. 14 para. 2bis of the Code of Obligations). The federal IT office names assignments, apprenticeship contracts, non-competition agreements and acknowledgements of debt as transactions where the law requires written form, and the same applies where the parties agreed on it.
- In the EU, Art. 25 of the eIDAS Regulation says an electronic signature cannot be denied legal effect only because it is electronic, and gives a qualified electronic signature the legal effect of a handwritten one. An advanced signature sits between the two: it must be uniquely linked to the signer and capable of identifying them.
- Between the two, as of 14 November 2026, BAKOM states that no mutual recognition agreement with the EU exists, so a qualified signature based on a foreign certificate is not equivalent to a Swiss qualified signature.
Three signature levels, and where each one runs
Simple
Contracts, NDAs, approvals and HR documents without a form requirement. Documenso Community Edition.
Advanced
Processes where a regulator, a counterparty or your own policy asks for an identified signer. A trust service provider is involved.
Qualified
Transactions where the law requires written form. A qualified provider verifies the signer and holds the key; in Switzerland, with a qualified timestamp.
Documenso reaches the advanced and qualified levels through a signing mode that hands each signature to a trust service provider over the Cloud Signature Consortium API. The provider verifies each signer, issues their certificate and holds the key. Documenso’s documentation sets out what that involves:
- An Enterprise Edition licence. The instance refuses to start in that mode without one. The Business Edition includes every commercial feature except this one.
- The whole instance. One provider per instance, and every envelope created in that mode is advanced or qualified. Signers enrol with the provider and authenticate with it to sign, signing is always sequential, and an envelope cannot be changed once it is sent.
- A provider that fits your jurisdiction. Upstream lists Swiss ZertES support as planned, so for Swiss qualified signatures we confirm that your provider works with Documenso before anything is promised.
So each process from step 1 that needs more than a simple signature keeps a route of its own: it stays where it runs today, moves to a qualified provider’s own signing service, or goes to a second Documenso instance in that mode with an Enterprise Edition licence. Write the decision down per process before you rebuild anything. This is general information, not legal advice: your counsel decides which of your documents need which level.
Step 3: export and archive the completed envelopes
DocuSign’s support article on exporting envelopes before closing an account names Retrieve, Connect, its Power Automate connector and a bulk download through Box, and says to download each envelope by hand when there are five or fewer. Three routes suit a full archive.
- DocuSign Retrieve. A Windows application that exports envelopes in bulk to a folder you choose, a paid feature that your DocuSign account team enables. Only account administrators can export envelopes sent by every user of the account. You filter by status, such as Completed, and by date range, and Retrieve can write a CSV index file with details such as the signing date, the completion date and custom fields. It exports only envelopes it has not exported before, so it can run again at the end to pick up the last ones.
- The eSignature REST API. List completed envelopes since a date, then download each one. The
archivedocument ID returns a ZIP with every PDF and the certificate of completion;combinedwithcertificate=truereturns one PDF that includes the certificate. You need an integration key promoted to your production account through DocuSign’s go-live process. - Connect manual publish. An account administrator uploads a CSV of envelope IDs under Integrations, Connect, Publish, and Connect publishes those envelopes to the listener of the Connect configuration named in the file. Account-level Connect is included in some plans and sold as an add-on on others.
# Envelopes completed since a date, one page per call: follow nextUri for the rest
GET /accounts/{accountId}/envelopes?from_date=2015-01-01&status=completed
# One envelope: every PDF and the certificate of completion, as a ZIP
GET /accounts/{accountId}/envelopes/{envelopeId}/documents/archive
DocuSign caps the API calls an account can make each hour, and every integration on the account shares that cap, so a large export by API is spread over several hours or run at night.
File each envelope where your records already live, with its envelope ID, subject, sender, recipients and completion date beside it, under the retention rules that apply to the contract. Documenso does not need to hold them. Then check the archive: the count per year against DocuSign’s envelope list, a sample opened at random, and a certificate of completion for every envelope.
Step 4: set up Documenso with its certificate, mail and sign-in
Three settings decide whether the first envelope works, and all three live in the environment.
# The certificate that seals every completed PDF, mounted read-only
NEXT_PRIVATE_SIGNING_TRANSPORT=local
NEXT_PRIVATE_SIGNING_LOCAL_FILE_PATH=/opt/documenso/cert.p12
NEXT_PRIVATE_SIGNING_PASSPHRASE=...
NEXT_PRIVATE_SIGNING_TIMESTAMP_AUTHORITY=https://tsa.example.com
# Signing requests and reminders through your relay
NEXT_PRIVATE_SMTP_TRANSPORT=smtp-auth
NEXT_PRIVATE_SMTP_HOST=smtp.relay.example.com
NEXT_PRIVATE_SMTP_PORT=587
NEXT_PRIVATE_SMTP_FROM_ADDRESS=contracts@acme.example
NEXT_PRIVATE_SMTP_FROM_NAME=Acme contracts
# Staff sign in through Keycloak
NEXT_PRIVATE_OIDC_WELL_KNOWN=https://id.acme.example/realms/acme/.well-known/openid-configuration
NEXT_PRIVATE_OIDC_CLIENT_ID=documenso
NEXT_PRIVATE_OIDC_CLIENT_SECRET=...
NEXT_PUBLIC_DISABLE_EMAIL_PASSWORD_SIGNUP=true
NEXT_PUBLIC_DISABLE_EMAIL_PASSWORD_SIGNIN=true
- The signing certificate. Documenso seals each completed document with one .p12 certificate that belongs to the instance, protected by a passphrase: a certificate without one fails at signing. A self-signed certificate proves the PDF was not changed, though PDF readers warn that its issuer is not trusted; one from a CA on the Adobe Approved Trust List shows as trusted in Acrobat. A timestamp authority keeps signatures verifiable after the certificate expires. Test a full signature before go-live.
- Mail. Pilae does not operate mail, so the relay is one you provide: your own server or a sending provider you contract. The instance sends from one address you set, on your own domain, which needs SPF and DKIM for that relay, or requests land in spam and contracts do not come back. Separate sender domains per organisation are a commercial feature.
- Sign-in. Instance-wide OpenID Connect is part of the Community Edition. Create a client in Keycloak, or in your own identity provider, and point Documenso at its discovery URL. With password sign-up and sign-in turned off, and no other sign-in method enabled, the sign-in page sends staff straight to the provider. The per-organisation SSO portal is a commercial feature.
Then build the structure. An organisation holds teams, and each team has its own documents, templates, webhooks and API tokens. Map DocuSign’s groups or sending departments to teams before people arrive. With two teams or more, a template can be shared with all of them as an organisation template.
Step 5: rebuild templates and direct links
Work from the JSON files of step 1, most-used first. The concepts map closely.
| DocuSign | Documenso |
|---|---|
| Envelope | Envelope: documents and templates are both envelopes in its API |
| Template | Template, owned by a team or shared with the organisation |
| PowerForm | Direct link on a template |
| Needs to Sign | Signer |
| Needs to View | Viewer |
| Receives a Copy | CC |
| Specify Recipients, Update Recipients | No counterpart; the Assistant pre-fills later signers’ fields |
| Allow to Edit, In Person Signer | No counterpart |
| Routing order | Signing order, sequential or parallel |
| Bulk send | Bulk send from a template, one document per CSV row |
| Certificate of completion | Certificate page and audit log, appended or downloaded |
| Connect | Team webhooks |
| Integration key and OAuth | Team API token |
- Recreate each template with the same documents, recipient roles and signing order. Where a recipient changes every time, give the role a placeholder email address and fill in the real one when the template is used.
- Place the fields. Signature, initials, name, email, date, text, number, checkbox, radio and dropdown fields are all in the Community Edition. For documents generated by another system, Documenso turns placeholder text in the PDF, such as
{{signature, r1}}, into fields when the file is uploaded. - Replace each PowerForm with a direct link on its template. A direct link is tied to one recipient role, the person who opens it enters their own name and email, and the template owner is notified of each signature. Keep the PowerForm’s URL list from step 1: each one is replaced where it is published.
- Test each template on a staging instance with test recipients: send, sign in the order you set, and open the sealed PDF and its certificate page.
Step 6: rewire the API and the webhooks
Integrations are rewritten, not moved. Each system from step 1 gets a team API token, created in the team’s settings and sent in the Authorization header. The calls follow the same shape as before: create an envelope (POST /envelope/create), or create one from a template (POST /envelope/use), then send it (POST /envelope/distribute). Set each envelope’s external ID to the record it belongs to, such as the CRM deal or the HR case, and it comes back in every webhook.
Webhooks replace Connect. They are configured per team, under Team settings, Webhooks, and personal accounts cannot have them.
| DocuSign Connect event | Documenso webhook event |
|---|---|
envelope-sent |
DOCUMENT_SENT |
recipient-delivered |
DOCUMENT_OPENED |
recipient-completed |
DOCUMENT_RECIPIENT_COMPLETED |
envelope-completed |
DOCUMENT_COMPLETED |
envelope-declined |
DOCUMENT_REJECTED |
envelope-voided |
DOCUMENT_CANCELLED |
Verification changes too. Where HMAC is set up, Connect signs each message with HMAC-SHA256 and sends the result in X-Docusign-Signature-1, with one more header per extra key; Documenso sends the secret you set on the webhook, as it is, in the X-Documenso-Secret header. The listener compares it with its stored value, in constant time.
Where the DocuSign integration was a connector inside another product, the replacement is usually a small n8n workflow: a Webhook node receives Documenso’s events, and HTTP Request nodes update the other system and call the Documenso API. Test every integration on the staging instance with test recipients, including a rejected and a cancelled envelope, before it touches production.
Step 7: send from Documenso, let open envelopes finish
The two systems overlap for as long as envelopes are still out in DocuSign. Nothing is moved between them.
The cutover, in order
- List what is open: In Agreements, select the envelopes still out for signature and Export as CSV.
- Switch senders: From the cutover date, people and integrations send from Documenso only.
- Replace public links: Each PowerForm URL is swapped for its direct link, then the PowerForm is deactivated.
- Let them finish: Open envelopes complete in DocuSign, with Connect still delivering their events.
- Close: A last export picks up the envelopes completed since, the archive is checked, then the account closes.
Envelopes that will never complete, such as an offer that was declined by phone, are voided in DocuSign rather than left open. Keep the integrations’ DocuSign code paths until the last envelope is back: they still receive its events. And run the final export while the account is open: once it closes, nothing more can be downloaded.
Running Documenso in production
A signing service is small, but it holds the record of what was agreed.
- PostgreSQL holds accounts, envelopes, recipients and the audit log. It is the only database Documenso supports.
- S3-compatible storage for the uploaded and sealed PDFs. The default keeps them in the database, which makes every dump larger and every restore slower.
- A job queue. Documenso sends email, seals documents and dispatches webhooks as background jobs. The default queue runs in PostgreSQL and is not recommended for production; the self-hosted option for production is BullMQ on Redis.
- Secrets outside the database. The signing certificate, its passphrase and the encryption keys are in neither the database nor the bucket, so they are backed up separately. A restore without them cannot seal a document or read stored secrets.
- Updates. Documenso runs its database migrations when a new container starts, and they cannot be reversed automatically, so the way back from an update is the backup taken just before it.
Pilae operates Documenso this way: PostgreSQL, PDFs in a bucket, background jobs on Redis, telemetry to Documenso off, and the certificate in a secret store with an alert weeks before it expires. Staff sign in through Keycloak or your own identity provider. The signing pages go out through the one gate on port 443, because outside signers must reach them, while the database, bucket and queue stay on your private network. Daily encrypted backups go offsite in the country your contract names, with the certificate and keys kept apart, and on Enterprise a restore test every month recorded in the console. Upgrades go through the Pilae Agent, tested on a copy and applied in your window. It runs on your premises or on dedicated machines in Pilae Cloud.
Let Pilae run the move
Pilae runs DocuSign to Documenso migrations at a fixed price: the inventory and the review of signature levels, the export of completed envelopes to your archive, the instance with its certificate, mail and sign-in, the template rebuild, the API and webhook rewiring, and the cutover. Where a process needs an advanced or qualified signature, the proposal names its route and any Documenso licence it needs, held in your name. Then we operate Documenso for you under a contract that, from the Business plan, includes a monthly availability commitment with service credits. See migration services for what the fixed price covers, or tell us how your contracts are signed today and we will scope it.
Questions
Can Documenso import our DocuSign templates or envelopes?
Which signature level does Documenso produce?
Do people who sign need a Documenso account?
What happens to envelopes still out for signature on the cutover date?
Is Documenso open source?
How long does a DocuSign to Documenso migration take?
Let us run the move for you
An inventory, a parallel run and a cutover plan, at a fixed price. Then we operate the app.
- Go deeperSaaS migrationA fixed-scope migration off Google Workspace, Microsoft 365, Zapier, Airtable and ChatGPT to open-source apps, with a parallel run and a cutover plan.
- CheckManaged operationsPatching, daily encrypted backups, monitoring and incident response for your open-source apps, under an SLA with an availability commitment of up to 99.9%.
