Open-source alternative to DocuSign Bulk Send: the short answer
If your team sends the same agreement to a long list of people, such as offer letters, policy acknowledgements or renewal notices, Documenso can run bulk send from a CSV file against a template, and DocuSeal's bulk send from CSV or XLSX is a Pro feature in its self-hosted edition, not something the free on-premises edition includes. A renewal or licensing change to DocuSign Bulk Send is a good moment to check which of these paths fits your documents, your file formats and your budget before you commit. The choice depends on three things you should settle first: the document types you send (a fixed PDF template with a few merge fields behaves differently from a form with conditional logic), the file formats your HR, legal or renewals team already maintains (CSV is supported by both platforms, while XLSX is a DocuSeal Pro capability), and the edition each product requires once it runs on your own servers. Documenso's bulk send works from a template's menu, and each row in the CSV creates a separate document, so you should check how your recipient data maps to template roles before testing with a small list. This page covers each path in turn, the license terms that apply to both projects, and what self-hosting adds in terms of hosting, signing certificates, backups and upgrades. Documenso and DocuSeal are both licensed under AGPL-3.0 family terms, so you should have your legal team read the license text, especially if you plan to modify the code. Confirm current edition features, license terms and per-user or per-completion fees directly with each vendor, since pricing pages change.
Which DocuSign Bulk Send capabilities map to Documenso and DocuSeal
This table maps DocuSign Bulk Send capabilities to Documenso and DocuSeal for offer letters, policy acknowledgements and renewals. Each cell states whether the capability is documented as covered, covered only on a paid edition, or needs confirmation with the vendor. Check the availability row first, because DocuSeal's free on-premises edition has no bulk send, and Documenso's plan gating for bulk send should be confirmed on its current pricing page.
| Capability | Documenso | DocuSeal |
|---|---|---|
| Bulk send availability | Covered: documented from a template menu; confirm plan gating | Covered on a paid edition: On-Premises Pro, not the free edition |
| Recipient list input | Covered: CSV file of recipients uploaded to the template | Covered on a paid edition: CSV or XLSX upload on Pro |
| Template reuse | Covered: bulk send starts from an existing template | To confirm with the vendor: template reuse inside bulk send |
| One envelope per recipient | Covered: each CSV row creates a separate document | To confirm with the vendor: whether each row becomes its own submission |
| Signer roles per row | To confirm with the vendor: role assignment for each CSV row | To confirm with the vendor: role mapping for each CSV row |
| Completion tracking | To confirm with the vendor: status reporting for each bulk batch | To confirm with the vendor: batch status reporting on Pro |
| Audit trail | To confirm with the vendor: audit record for each bulk-created document | To confirm with the vendor: per-submission audit record; PDF signature verification is documented |
| API or webhook triggers | Covered on a paid edition: API access starts on the Teams plan | Covered: API and webhooks; API use carries per-completion fees |
| SSO access | To confirm with the vendor: SSO availability for your plan or setup | Covered on a paid edition: SAML SSO on Pro |
Documenso or DocuSeal Pro: which bulk send path fits your workflow
Bulk send is the same job in both products: one template, one recipient list, one signing request per recipient. The paths differ in where the list comes from, which edition you pay for, and how much control you keep over each row. Start with the list format and the edition you can justify, then pick the path that fits how often the list changes.
Documenso template bulk send from CSV
Documenso runs bulk send from a template's menu: you upload a CSV of recipients and each row creates a separate document. This suits offer letters or renewal notices built from one approved template. The trade-off is that every row is its own document, so each signature request, status and completed file is tracked individually, which helps audit but grows the record count quickly. Confirm the column mapping for recipient roles and fields against a small test file before sending to the full list.
DocuSeal Pro bulk send from CSV or XLSX
DocuSeal Pro accepts bulk send from either CSV or XLSX, so HR or finance teams can keep the list in the spreadsheet they already maintain. Unlimited bulk send is a Pro feature in the on-premises edition, so the free edition is not enough for this path. Budget for per-user Pro licenses on the admin side, and check whether your recipient data requires SAML SSO, which is also a Pro feature, before committing to this path.
Scripted bulk send through each API
Teams that need validation, deduplication, or approval steps before a send can call each product's API from a script or workflow tool. Documenso exposes API access on its Teams plan and above, and DocuSeal provides an API and webhooks in its self-hosted editions. Scripts give the most control over the list but shift the work to your team: you own error handling, retries, rate limits, and logging of each sent request. For DocuSeal, confirm whether API usage in your setup triggers per-completion fees.
Edition and license check first
Before choosing a path, confirm which edition supports it. DocuSeal's free on-premises edition has no bulk send, so the Pro edition is the gate for CSV or XLSX batches. Documenso's AGPL-3.0 code is open to read, run and fork, but plan features such as API access are tied to its cloud and hosted tiers, so ask Documenso which self-hosted licensing option covers your batch volume. Get these answers in writing before the project scope is set.
Which edition and license each bulk send path needs when self-hosted
Before you choose a bulk send path, settle which license and edition you will run, because the two candidates differ in both. Documenso is licensed under AGPL-3.0, and its README states that the code stays open source to read, audit, run and fork. DocuSeal is distributed under AGPLv3 with Section 7(b) additional terms. Those additional terms can add attribution or notice obligations, so have counsel read them against your deployment model, especially if you modify the code, host it for staff only, or expose it to outside signers or customers.
DocuSeal's bulk send sits behind its paid edition. Its free On-Premises Open Source edition does not include bulk send, SSO or embedded signing. On-Premises Pro costs $240 per user per year, according to DocuSeal's pricing page, and it is the tier that adds unlimited bulk send from CSV or XLSX. Confirm whether the per-user count covers only the people who create batches or every signer, and whether a Pro license applies to the instance or to each user, since that changes the cost for an offer letter or acknowledgement campaign that goes to hundreds of recipients.
For Documenso, the bulk send path is documented in its templates guide, but you must confirm which self-hosted license includes it before you commit. Documenso's self-hosting licensing is handled through its self-hosting page and an Enterprise plan with custom pricing, and the cloud plans listed on its pricing page do not give you a self-hosted instance. Ask the vendor in writing which features are included in the self-hosted license, whether bulk send is among them, and what support and update terms apply. A DeployOpen scope can include that license check as an agreed deliverable.
How bulk send differs for offer letters, policy acknowledgements and renewals
Offer letters are usually one recipient per row, with a template that carries the company terms and a small set of fields that change for each candidate. In a Documenso or DocuSeal bulk run, each CSV or XLSX row produces a separate document, so the file must map cleanly to the template's fields. Illustrative example: a row might hold a candidate name, email, job title, start date and base pay, while the employer signature block stays the same.
- Recipient shape: One row per candidate, with the email address as the key that routes the signing request.
- Per-row fields: Title, start date, compensation and reporting line. Confirm that numeric and date columns are formatted the way the template expects.
- Signer routing: Usually the candidate signs first, then an authorized company signatory countersigns. Confirm that the signing order is set on the template, not left to the sender.
- Audit trail: Keep each completed offer with its signing record, timestamps, IP data and the certificate that closed it, so the version offered can be proven later.
- Access control: Limit who can upload candidate files, since salary data is sensitive.
Before any run, check a test batch of two or three rows against the final template and confirm the completed PDFs contain the right values.
Policy acknowledgements send the same document to a large group, often every employee or every person in a department. The per-row data is thin, usually a name and email, so the value lies in tying each signature to the exact policy version. A changed policy should produce a new template or version, not an edited copy that makes earlier acknowledgements ambiguous.
- Recipient shape: A roster exported from your directory, one row per person, with department or group used for reporting rather than routing.
- Per-row fields: Usually none beyond the name. The policy version and effective date should be fixed on the template and printed on the document.
- Signer routing: Single signer per row. Confirm how departures, leave and new hires are handled, since a roster exported late can miss people.
- Audit trail: Record which version each person acknowledged, when, and whether reminders were sent. Auditors usually ask for completion evidence per person and per version.
- Re-issue rules: Decide whether a new version triggers a new run for everyone, and keep the old run's records intact.
Confirm that your roster source is current on the day you send, and that the completion report can be exported per policy version.
Renewals, such as vendor, subscription or annual service agreements, combine a fixed body with terms that change per customer, such as the renewal date, fee schedule and term length. The risk is less about delivery and more about a wrong value reaching a counterparty, so the data check before sending matters most. Illustrative example: a renewal file might carry the counterparty legal name, the renewal start and end dates, and an updated fee schedule reference.
- Recipient shape: One row per agreement, often with a separate contact row when a counterparty has several signers.
- Per-row fields: Term dates, fee schedule references and notice periods. Use formulas or conditional fields where the template supports them, and check the result in a sample.
- Signer routing: Often the counterparty signs first and your signatory countersigns. Route by contract owner where your approval policy requires it.
- Audit trail: Keep the source file, the rendered agreement for each row and the completion certificate together, so the exact terms signed can be reconstructed.
- Duplicates: Check for duplicate rows and for counterparties already mid-renewal before the run starts.
Before sending, ask whether the vendor's legal team needs a review step outside the bulk run, and confirm that your own contract records are updated from the completed documents.
What self-hosting changes for signer data and the signing certificate
Self-hosting Documenso moves two things onto your side of the line: the signing certificate that Documenso uses to digitally sign completed documents, and the database that holds your bulk send recipient lists and finished records. Documenso documents options for this certificate, including a self-signed .p12 file generated with OpenSSL and signing through Google Cloud KMS. The choice is an architecture decision, not a setting to leave at its default. A self-signed certificate keeps the key material in files you manage, so you must control who can read them and how they are backed up. A KMS-backed key keeps the private key in a managed key service, which moves key custody into a cloud account you already govern. Confirm which option your security team can operate and audit before the first production send.
Your organization also owns the PostgreSQL database, the file storage and the backups. For a bulk send run, that means the CSV of recipients, each generated document, and each completion record sit in systems you operate. Plan the retention period for those rows, who may export them, and how a restore is tested. Verify that backups of the database and the document store are taken together so a restored record still points to its file. Ask your DeployOpen or internal team to document where each component runs and who holds administrative access.
On legal effect, the ESIGN Act provides under 15 U.S.C. 7001(a) that an electronic signature or record affecting interstate commerce may not be denied legal effect solely because it is electronic. Section 7003 excludes several categories, including wills and codicils, most family law matters such as adoption and divorce, most of the Uniform Commercial Code, and court orders. Offer letters and policy acknowledgements generally fall outside those exclusions, but renewals and some regulated notices may not. Ask counsel to list which bulk send templates qualify, and confirm any state-level rules for your employees and customers before you rely on the signed output.
Running bulk send beside DocuSign while open envelopes close
A bulk send move rarely happens in one step. DocuSign keeps the envelopes already out for signature, while the new bulk sends start on the self-hosted tool, and both need identity, status flow and an agreed end date. The four cards below cover the decisions that keep those two systems from drifting apart.
Keep DocuSign for open envelopes
Envelopes already sent from DocuSign keep their signing sequence, reminders and certificates of completion inside DocuSign until they close. Do not reissue them from the new tool, because a second copy creates two signed records for one offer or acknowledgement. List every open envelope by template and batch, record the date each batch is expected to close, and confirm with your DocuSign administrator that completed envelopes and their certificates can still be downloaded after the subscription changes.
Route new bulk sends to one tool
Pick a single rule for where each new bulk send starts, such as all policy acknowledgements from a given date going to the self-hosted tool. Mixed routing within one campaign makes reporting and reminders unreliable. Documenso runs bulk send from a template's menu with a CSV file of recipients, and each row creates a separate document. DocuSeal's bulk send from CSV or XLSX is listed among its Pro features, so confirm the edition you plan to run before you assign campaigns.
Connect SSO for senders
Senders who launch bulk campaigns need individual accounts that map to HR or contract ownership, and offboarding must remove their access in the new tool as well. DocuSeal lists SSO with SAML as a Pro feature, so the free on-premises edition may need local accounts for senders. Ask your identity team which protocol your environment supports, who approves sender roles, and how a departing employee's open campaigns are reassigned.
Pass completion status back
HR and contract systems usually need to know when each recipient signs, so the offer or acknowledgement record updates without manual entry. DocuSeal documents an API and webhooks for integrations, which is the natural starting point for this flow. Confirm the exact events each tool emits, how failed deliveries are retried, and whether a signed PDF and its audit trail can be pushed to your document store. Test with a small illustrative batch before routing live campaigns.
Moving bulk send templates, recipient lists and history off DocuSign
This sequence moves bulk send templates, recipient lists and completed agreements from DocuSign to a self-hosted signing platform, with the archive kept as records and a tested send path before production cutover.
Inventory bulk send templates and recipient lists
The process owner and an administrator list every DocuSign template used for bulk send, including the document version, signing order, recipient roles and any fields that are filled in at send time. For each process, record the source of the recipient list, such as an HR export, a renewal report or a spreadsheet, and its current column names. Done when every bulk send process has one row in an inventory that names its template, its roles and its list format, and the owner has signed off on it.
Export completed envelopes and certificates of completion
An administrator downloads completed envelopes for each bulk process as signed PDFs, together with their certificates of completion, using DocuSign's own export tools or the eSignature REST API. Store the files in your records system with a manifest that lists envelope IDs, dates and signers, so an auditor can match each signed PDF to its certificate. Done when a sample of exports has been opened, checked against the source envelope and filed, and the manifest matches the count reported in DocuSign.
Rebuild each template and its recipient roles
A template owner recreates each bulk send template in Documenso as a template, or in the DocuSeal form builder if the document relies on fillable fields, mapping each DocuSign role to a recipient role with the same signing order. Confirm which conditional logic and formulas the process depends on, since these are DocuSeal Pro features. Done when each rebuilt template has been compared side by side with its DocuSign original, and the owner has confirmed that field placement and role order match.
Convert recipient lists to CSV or XLSX
The process owner converts each recipient list to the file format the chosen platform accepts, with one column per role field that the template expects, such as recipient name and email address. Documenso bulk send reads a CSV of recipients, where each row creates a separate document, and DocuSeal accepts CSV or XLSX on its Pro edition. Remove duplicate addresses and test a copy with a few rows first. Done when each list opens cleanly, its column headers match the template's fields, and the owner has checked a sample row against the source record.
Run a pilot send to internal test recipients
An administrator runs each rebuilt bulk send against a small list of internal test addresses that the team controls, and each tester completes the signing steps as a real signer would. Check that every row produced its own document, that the right signers received the request in the right order and that the completed PDF and audit trail were stored. For DocuSeal, confirm that bulk send is available on the edition you have licensed before the pilot. Done when every test row has produced a completed document with the expected fields, and any mismatch has a recorded fix.
Switch the production bulk process
The process owner moves each production send to the new template and list format on an agreed date, and updates any upstream system that generates recipient files so it writes the new column layout. Notify the people who receive or sign these documents of the new signing address and sender name. Keep a record of the first production batch, including the count of documents created and any failed rows. Done when the first live batch completes, the count matches the list, and the owner signs off that the old DocuSign template is no longer used for new sends.
Keep DocuSign read-only until open envelopes close
Leave the DocuSign account active in read-only use so that envelopes already out for signature can finish and can be downloaded. Ask the DocuSign account owner which contract terms govern access after the subscription ends, and confirm this with the vendor, since these terms are not part of this page. Stop new sends, archive the final set of completed envelopes once no open envelopes remain, and record the date the account was closed. Done when the open envelope count is zero, the final archive has been verified, and the closure record is filed with the process inventory.
What does it cost and take to replace DocuSign Bulk Send?
What are the cost components of replacing DocuSign Bulk Send with self-hosted software?
The cost has five main parts: the software license or Pro seats, per-completion fees if you use DocuSeal's API or embedding, hosting, the database and backups, and a signing certificate, plus the labor to set up and run the system. Documenso and DocuSeal's free editions are open source, so the software itself has no license fee. DocuSeal's On-Premises Pro edition, which includes bulk send from CSV or XLSX, is priced at $240 per user per year, according to DocuSeal's pricing page. Ask your vendor or implementation partner to itemize each part in the written scope so you can compare it with your current DocuSign invoice.
Which costs are one-time and which recur every year?
Setup labor, template rebuilding, initial configuration, and the signing certificate setup are usually one-time costs. Recurring costs include hosting, database and backup storage, Pro seats billed per user per year, per-completion fees if you call the API or embed signing, and the staff time to patch and upgrade. Confirm with DocuSeal whether Pro seats are billed monthly or annually, because the pricing page lists $20 per user per month billed annually. Documenso's self-hosted setup also depends on how you source the certificate, so confirm whether that certificate has an annual renewal cost in your chosen option.
What drives the cost of bulk send up or down?
The main drivers are how many people need to send bulk batches, how many completions each month pass through the API or embedding, and whether you need SSO, white-label or embedded signing. Under DocuSeal's model, bulk send itself is a Pro feature, so the number of Pro seats is the biggest lever. Per-completion fees at $0.20 per completion apply only to API and embedding usage, so a team that sends bulk batches from the interface alone pays differently from one that triggers batches through an integration. Hosting size and backup frequency also change the total.
Can our team run bulk send ourselves, or do we need outside help?
A team with Docker, PostgreSQL and basic web server administration can install and test Documenso or DocuSeal, since both ship Docker images and document their database options. Documenso supports Docker, Docker Compose, Kubernetes and manual installation, and DocuSeal runs from the docuseal/docuseal image with SQLite by default. The harder parts are a signing certificate policy, template and recipient role rebuilding, and proving that bulk runs produce the records your audit needs. Decide early whether you will do all of this internally or buy a fixed-scope engagement for part of it, and check your staff capacity before you commit.
How long does a bulk send migration take, and what makes it longer?
The duration depends on how many templates use bulk send, how many fields each template has, how many recipient roles they define, and whether your CSV or XLSX data is clean. Installing the software is usually the quickest step. Rebuilding PDF fields in DocuSeal's WYSIWYG builder or Documenso templates, testing a sample batch end to end, and setting up the signing certificate take longer. We do not publish timelines, so ask for a written schedule that lists each template and each test batch, and confirm it against your own renewal date for DocuSign.
What should we ask for in a written scope before hiring help?
Ask for a written scope that names the platform and edition (Documenso or DocuSeal, and whether DocuSeal Pro is included), the list of templates and bulk send workflows in scope, the CSV or XLSX formats you use, and the hosting location. Also request the database choice, backup and restore procedure, the signing certificate approach, how SSO will be connected, the testing plan for sample batches, handover documentation, and what happens after go-live. Require the scope, deliverables and timelines to be agreed in writing before work starts, since most engagements are fixed-scope.
Does self-hosting bulk send change our compliance responsibilities?
Yes. When you self-host, you own the controls that a vendor previously handled, including access control, backups, patching, logging and key management for the signing certificate. Your auditor or certification body will assess those controls, and DeployOpen prepares systems and evidence but does not issue audit reports or certifications. Ask your compliance lead which DocuSign controls you need to reproduce, and confirm with each open-source project which compliance references apply to the version you deploy.
How DeployOpen scopes and delivers a bulk send replacement
DeployOpen plans, implements, customizes, integrates, hardens, backs up, documents and supports self-hosted open-source platforms inside your own infrastructure. For a bulk send replacement, that means agreeing in writing which recipient lists, templates and edition choices are in scope before any work starts, then delivering the signing workflow on your own servers with its evidence and handover material.
How we scope
- Inventory the DocuSign bulk envelopes, templates and recipient lists that must be rebuilt, with the owning business teams
- Confirm whether Documenso bulk send from CSV or DocuSeal Pro bulk send from CSV or XLSX fits each use case
- Agree the edition and license per user, the hosting location and the signing certificate approach in the written scope
How we build
- Deploy the chosen platform from its official Docker image with PostgreSQL or another supported database in your environment
- Rebuild templates and recipient roles, then test CSV or XLSX imports with sample rows that do not contain real signer data
- Configure the signing certificate, email delivery and access controls, then test completion and audit trail output before go-live
How we hand over
- Document the bulk send procedure, file format rules, template mapping and rollback steps for your operations staff
- Provide records showing how each bulk run was tested, including the controls behind signing certificates and audit trails
- Run both systems in parallel until open DocuSign envelopes close, then confirm archived agreements are stored where your policy requires
How we support
- Ongoing support, upgrades and continuous testing are available as retainers after handover
- Apply platform upgrades and re-test bulk send workflows against each new release before rollout
- Confirm with your legal and compliance teams which agreement types can be signed electronically, since some record types fall outside the ESIGN Act
