Migrate from DocuSign to DocuSeal

Migrate from DocuSign to DocuSeal: what the move involves

A team that wants signing on its own servers faces three pieces of work: rebuilding DocuSign templates in DocuSeal, archiving completed envelopes, and repointing every integration that receives DocuSign events. The move is mostly template rebuilding, data archiving and webhook changes, and the effort is set by how many templates you have and how deeply your systems depend on DocuSign's API and Connect-style notifications. Count templates and list integrations before you estimate anything else. Internal platform or IT staff usually do the work, with an implementation partner sometimes handling the deployment, SSO wiring or integration changes. In DocuSeal, the WYSIWYG PDF form field builder is where templates are rebuilt, so someone must place each signature, date and text field on each PDF and assign it to the right signer role. Confirm with DocuSeal which editions include the features you rely on, since the free on-premises edition has no SSO or bulk send, and the DATABASE_URL setting determines whether you run SQLite, PostgreSQL or MySQL before any data lands in the system.

The short answer on risk is moderate and manageable with a parallel run. Keep DocuSign active until open envelopes close, export completed agreements and audit trails as records you can retrieve later, and point new sends at DocuSeal only after a test set of templates has produced verifiable signatures. The DocuSeal API and webhooks must be tested against your own receiving systems, because a DocuSign event payload will not match a DocuSeal payload field for field. DocuSeal's own pricing page lists the Pro license at $240 per user per year, and its per-completion API fee applies only to embedded or API signing, so ask for both figures in a written quote alongside your hosting and backup costs. Confirm the current release with the DocuSeal releases page before you pin an image version, and record which template and webhook tests passed so the cutover decision rests on evidence.

Which DocuSign capabilities map to DocuSeal and which need rework

This table maps the DocuSign capabilities a migration usually touches to DocuSeal, marking each as clean, needs rework or gap. Read the edition column first, because the free on-premises edition lacks SSO, bulk send and embedded signing, which only the paid Pro edition adds. Confirm any advanced routing or envelope rules in your own DocuSign account before you plan the rebuild.

Capability	DocuSeal fit	Edition and what to check
Templates	Needs rework	Rebuild each DocuSign template in DocuSeal. Export the template list from your account first so nothing is missed.
PDF field builder	Needs rework	DocuSeal has a WYSIWYG PDF form field builder. Place fields again on each document, since field positions do not carry over automatically.
Signature verification	Clean	DocuSeal includes PDF signature verification. Include it in your verification test plan for archived documents.
API and webhooks	Needs rework	DocuSeal provides an API and webhooks. Map each DocuSign Connect or API call to a DocuSeal endpoint and repoint callbacks.
Bulk send from CSV or XLSX	Clean	Available only on On-Premises Pro. Free edition users must send one envelope at a time or use another process.
SSO with SAML	Clean	Available only on On-Premises Pro. Free edition users sign in with local accounts.
White-label and company logo	Clean	Available only on On-Premises Pro. Confirm the branding you need before you pick an edition.
Embedded signing	Gap	Not in the free edition. Pro adds it with per-completion fees on the DocuSeal pricing page. Confirm the fees for your volume.
Conditional fields and formulas	Needs rework	Listed as a Pro feature. Recreate DocuSign conditional logic as DocuSeal rules and test each branch.
Advanced routing and envelope rules	Gap	Confirm each routing rule in your DocuSign account. Map it to a DocuSeal workflow manually and document any rule that does not map.

Choosing the free on-premises edition or Pro before you start

Decide between the free on-premises edition and On-Premises Pro during inventory, before any template is rebuilt. The free edition has no SSO, bulk send or embedded signing, so every DocuSign workflow that relies on those features either moves to Pro or has to be redesigned. Pull the list of DocuSign envelopes, bulk sends and sign-in rules from your inventory and mark which ones depend on them. If bulk send for renewals or offer letters is in use, or if staff sign in through your identity provider, the edition choice determines whether those workflows can move at all.

On-Premises Pro lists at $240 per user per year, which is $20 per user per month billed annually, according to the DocuSeal pricing page as read in October 2026. Pro adds unlimited bulk send from CSV or XLSX, white-label branding, embedded signing and SAML SSO. Embedded signing and API usage also carry a fee of $0.20 per completion, so a product that embeds signing in another application adds a per-completion cost on top of the seat license. Confirm the current terms with DocuSeal before you budget, and ask whether the per-user price applies to senders only or to every account that touches a document.

Record the decision with its cost basis in the migration plan. Ask DocuSeal for a written quote that states the number of Pro seats, the expected completions per year and whether the per-completion fee applies to your use. Then check the DocuSeal pricing page against that quote. A team that only needs manual sending for a few contracts may stay on the free edition, while a team that sends bulk renewals needs Pro for those flows from the first day of cutover.

What data and integrations to move and rebuild

A DocuSign to DocuSeal move has four kinds of material: finished agreements and audit records, the templates that generate new envelopes, the people and roles that sign and administer, and the API and webhook connections that feed other systems. Each one moves on its own track, and each has a different owner and a different failure mode if it is skipped.

Archive completed envelopes and audit records

Completed agreements and their certificates of completion are the records you must keep, so export them before you change anything else. Use the export paths DocuSign documents for envelopes, combined PDFs and certificates through its eSignature REST API, and confirm the exact formats your account returns. Store the exports with their envelope IDs and timestamps in your own retention system, because DocuSeal's audit output will not replace DocuSign's certificates for documents signed before the move.

Rebuild templates in the WYSIWYG builder

DocuSign templates do not convert automatically into DocuSeal. Recreate each template in DocuSeal's WYSIWYG PDF form field builder, placing signature, date and text fields on the source PDF and naming the recipient roles the same way your team does. Start with the templates that generate the most envelopes, and check each rebuilt field against a signed copy from the old system before retiring the original.

Map users, roles and sender permissions

Build a table of every DocuSign user, shared sender and role, and decide which of them need an account in DocuSeal and at what level. Keep signer roles separate from administrator roles, and remove stale accounts from the export before importing anyone. On the free on-premises edition, user management is basic, so confirm what your role model needs before you commit to a plan.

Configure SAML sign-in

SAML single sign-on is a feature of DocuSeal's paid On-Premises Pro edition, not the free one. If your DocuSign tenant signs users in through a corporate identity provider, define the SAML metadata, attribute mapping and certificate rotation process before go-live. Test a deprovisioned account as well as a new one, so that leaving staff lose access to signing and administration at the same time.

Switch API clients and repoint webhooks

Every system that calls the DocuSign eSignature API or receives its Connect events needs a planned cutover. Inventory each client, its credentials and the events it consumes, then point the DocuSeal API and webhook endpoints at the same services in a test environment first. Compare payload fields one by one, since DocuSeal's webhook structure does not match DocuSign Connect, and retire old DocuSign credentials only after both paths have run in parallel.

Plan bulk send and embedded signing

Bulk sending from a CSV or XLSX file and embedded signing inside your own product both sit in paid DocuSeal editions, and embedding carries a per-completion fee. Count how often your team uses bulk send or embedding today, and price both against the free edition before you move those workflows. Keep any integration that depends on these features on the same schedule as the license purchase.

How to sequence the cutover from DocuSign

The sequence moves templates, open envelopes and integrations from DocuSign to a self-hosted DocuSeal instance in an order that keeps signing running throughout. Each step ends with a written output that the next step depends on.

Inventory templates, envelopes and integrations
Export a register of every DocuSign template, every envelope still in progress, and every system that calls the DocuSign API or receives its Connect webhooks. Record the owner of each template, the recipient roles and routing order, the fields used, and whether the template is sent by a person, by an API call or by bulk send. The output is a template register, a list of open envelopes with their expected completion dates, and an integration map naming each client and endpoint. Confirm with each template owner that the register is complete before moving on.
Deploy DocuSeal from the Docker image
Stand up DocuSeal in your own environment using the docuseal/docuseal Docker image, which uses SQLite by default. If you expect a larger volume or need your database standards, point the DATABASE_URL variable at PostgreSQL or MySQL before first start, because changing the database later is a separate task. Put the service behind your TLS termination, restrict administrative access, and configure outbound email. Pin the image to a specific version you have tested, such as the 3.3.2 release published on October 12, 2026, and check the release notes before any upgrade. The output is a running instance with a documented version, database choice, and a backup job that has restored successfully at least once.
Rebuild and test templates in a pilot
Recreate the highest-volume templates in the DocuSeal WYSIWYG PDF form field builder, placing signature, date, text and checkbox fields on the source PDF and assigning each to the correct submitter role. Confirm which Pro features a template needs, such as conditional fields or bulk send from CSV or XLSX, and decide on the edition with your license owner. Send each rebuilt template to internal test recipients, complete it, and compare the output PDF and field values against the DocuSign original. The output is a signed-off pilot list where each template records a passed test, its edition requirement, and any field that could not be matched.
Run both systems in parallel
Keep DocuSign active for envelopes already sent, and direct all new agreements to DocuSeal once a template passes the pilot. Do not reissue open DocuSign envelopes in DocuSeal unless the signer agrees, because a second copy creates two legally competing records. Review the open envelope list at a regular interval until it is empty, and log every agreement that moved to the new system with its owner. The output is a parallel-run log showing the date each template was switched and a confirmed count of open DocuSign envelopes at each review.
Cut over webhooks and API clients
Change each integration from the inventory to point at the DocuSeal API and webhook endpoints, updating the submitter and template identifiers that the client uses. Test each integration in a non-production environment with a sample submission, and confirm that the receiving system records the completion event and the signed document. Keep the DocuSign webhook listener running until the parallel run shows no open envelopes that depend on it. The output is a set of tested integrations, each with a signed-off test record and a rollback note naming the previous endpoint.
Archive, verify and decommission DocuSign
Once no DocuSign envelopes remain open, export completed agreements and their audit trails as records, following the process for exporting data from DocuSign, and store them in your records system with retention metadata. Check a sample of archived files against the originals, then confirm with legal and compliance that the archive meets your retention obligations. Only after that, close DocuSign accounts, revoke API keys, and remove DocuSign webhook registrations. The output is a verified archive with a retention record, a list of revoked credentials, and written approval from the records owner to close the DocuSign account.

Choosing SQLite, PostgreSQL or MySQL for DocuSeal

The database decision for DocuSeal comes down to one question: will the instance hold a small team's documents on a single server, or does it need the backup, recovery and availability features of a database your organization already operates? DocuSeal runs on SQLite by default with the docuseal/docuseal Docker image, and you switch to PostgreSQL or MySQL by setting the DATABASE_URL variable. SQLite keeps the first deployment simple because there is no separate database server to install, patch or monitor. Moving to PostgreSQL or MySQL adds a database service that you must provision, secure and back up, but it fits better when your standard operations already cover those engines.

Start with four inputs. User count and signing volume shape load on the database, and a pilot with a few senders is a different problem from a company-wide rollout. Backup needs matter because your recovery point depends on how the database is dumped or snapshotted, so confirm that your backup tooling supports the engine you pick and that restores are tested. High availability requirements may rule out a single-file SQLite database running on one host. Finally, existing skills count: a team that already runs PostgreSQL backups and upgrades should not take on a new engine just to avoid a server.

Before you decide, check the supported database versions, the exact DATABASE_URL format and any migration notes in the DocuSeal GitHub repository. Confirm the backup and restore procedure for each engine in the same place, and ask your DeployOpen scope lead to include a restore test in the written plan. Whichever engine you choose, record it in the migration runbook so that the database version, backup schedule and owner are known before the first live envelope is sent.

What drives migration cost and duration

This table breaks the DocuSign to DocuSeal migration into its cost components, showing who is paid for each, whether it is one-time or recurring, and what drives it up or down. Use it to build a written scope and to check that a quote covers every item before you sign.

Cost component	Who is paid or who spends effort	One-time or recurring	What drives it and what to ask for
Internal staff time	Your IT, security and business owners who inventory templates and approve field layouts	One-time	Template count and field complexity. Ask your team to list templates and signer roles before any quote is requested.
Template rebuild and validation	Your team or an implementation partner rebuilding PDF fields in DocuSeal's WYSIWYG builder	One-time	Number of conditional fields and formulas. Confirm each rebuilt template against a sample signed copy from DocuSign.
Implementation partner fees	An implementation partner, paid under a written, fixed scope	One-time	Integrations, SSO setup and webhook repointing. Ask for deliverables, timelines and acceptance criteria in writing.
DocuSeal Pro licence	DocuSeal, paid per user per year on the On-Premises Pro edition	Recurring	Whether you need bulk send from CSV or XLSX or SSO with SAML. The DocuSeal pricing page lists On-Premises Pro at $240 per user per year, billed annually at $20 per user per month. Confirm current figures before budgeting.
Per-completion fees	DocuSeal, charged per completion for API embedded signing on Pro	Recurring, usage-based	Volume of embedded signing completions. The DocuSeal pricing page lists $0.20 per completion. Model expected completions with your own data.
Hosting and compute	Your cloud account or data center team	Recurring	Database choice (SQLite, PostgreSQL or MySQL), user volume and high availability needs. Confirm sizing with your own environment.
Backup and retention	Your backup platform team	Recurring	Envelope archive volume and retention rules for signed PDFs and audit records. Confirm the backup scope covers the database and file storage.
Email delivery	Your mail provider or relay	Recurring	Signer volume and reminder settings. Confirm sending domain authentication with your mail team.
Dual running period	Your team, while DocuSign and DocuSeal both operate	One-time, with ongoing DocuSign subscription cost	Length of open envelopes still in DocuSign. Keep your DocuSign plan active until open envelopes close and archives are verified.

What usually goes wrong and how to prevent it

Most failed DocuSign-to-DocuSeal moves fail at the edges: the PDF fields, the archive, the integrations and the people who receive the links. The cards below name the six risks we see most often and a concrete check for each, so the cutover can be tested before any real signer depends on it.

Field placement drift in rebuilt PDFs

DocuSeal's WYSIWYG builder places fields on the PDF you upload, so a template rebuilt by hand can shift by a few millimeters, change page breaks or lose a signature box on a long agreement. Signers then sign in the wrong place or the form fails validation. Prevent this with a field-by-field test checklist: for each template, list every DocuSign tab, confirm its page, type, required flag and recipient role in DocuSeal, and send a test envelope to a internal signer on each page size you use. Keep the original PDF version that DocuSign used as the reference.

Missing archived audit trails

DocuSign envelopes carry a certificate of completion and an audit history that you may need for disputes, audits or retention. If you cutover without exporting them, the record of who signed, when and from where stays only in a system you are leaving. Before you decommission the DocuSign account, export every completed envelope with its audit data and store it in a write-once location on your own storage. Confirm with your legal and records team which fields they require, and test that a restored archive opens and verifies.

Webhooks still pointing at DocuSign

Downstream systems such as contract repositories, CRMs and HR platforms often receive DocuSign Connect events and update records from them. After the move, DocuSeal sends its own webhooks to endpoints you configure, so any system still listening only to DocuSign will stop receiving completions without an error on the sending side. Inventory every DocuSign callback and API integration, register the matching DocuSeal webhook for each, and run one completed test signature through the full chain to confirm each downstream record updated.

Open envelopes orphaned at cutover

Envelopes that are sent but unsigned on the last day of DocuSign use can stall indefinitely if no one owns them. Signers may hold a link to a DocuSign page that no longer routes anywhere useful, and the sender may not know the envelope is still open. Set a cutover date, stop creating new DocuSign envelopes on that date, and list every open envelope with its owner and recipients. Either let them complete in DocuSign under a defined end date or resend them from DocuSeal with a clear note, and record which path each one took.

Signer email failing on the new host

Invitation and completion emails are sent from your DocuSeal server, so a new host that lacks correct SPF, DKIM and DMARC records, a valid TLS certificate or an allowed outbound route can have its messages filtered or dropped. Your signers will then see that nothing arrived, and the sender may assume the envelope was never sent. Before go-live, confirm the sending domain's authentication records with your mail team, send test invitations to mailboxes at your main providers, and check the spam and bounce handling. Monitor delivery logs during the parallel run.

Unplanned reliance on Pro features

The free on-premises edition of DocuSeal does not include SSO, bulk send or embedded signing, while On-Premises Pro adds them along with white-label and per-completion embedding fees. Teams that adopt bulk sends or SAML sign-in after go-live discover the license gap too late, and per-completion charges start on high-volume flows. List every DocuSign feature your workflows use, mark each as free or Pro in DocuSeal, and confirm the Pro licensing terms and per-user counts in writing before you schedule the cutover. Ask the vendor how usage is counted for your volume.

How the migration changes by starting point

A small team that sends a limited set of PDF agreements usually needs the least change. The work centers on rebuilding a few templates in DocuSeal's WYSIWYG PDF form field builder, sending requests by hand, and keeping completed PDFs and signature records in a known place. The free On-Premises Open Source edition covers this pattern, because SSO, bulk send and embedded signing are not part of it.

Edition: Start with the free on-premises edition and confirm that none of your workflows depend on Pro features such as SAML sign-in or CSV bulk send.
Database: SQLite is the default and is often enough for a single small instance. Confirm backup and restore procedures for the database file before you rely on it.
Integrations: Usually none beyond email delivery. Confirm who sends requests and whether anyone uses DocuSign's mobile or Word add-in workflows today.
Archive: Export completed agreements and audit records from DocuSign before you cancel the subscription, since envelope history stays with the old account.
Templates: Rebuild each template by hand and test each one with a dummy signer before first real use.

Confirm the number of active templates, the number of signers per agreement and whether any document needs a retention period that outlasts the DocuSign account.

Questions teams ask before migrating from DocuSign to DocuSeal

How much does a migration from DocuSign to DocuSeal cost?

The cost depends on the scope you agree in writing, and the main drivers are the number of templates to rebuild, the number of users, the edition you choose and the hosting you provide. DocuSeal's pricing page, as read in October 2026, lists its On-Premises Open Source edition as free and On-Premises Pro at $240 per user per year, billed as $20 per user per month annually. Pro also carries a $0.20 per completion fee for embedded signing. Your own costs include the server, database backups, email delivery and staff time. DeployOpen does not publish a price list, so ask for a quote built from a written scope that lists each template, integration and edition.

How long does it take to move from DocuSign to DocuSeal?

Timing depends on how many templates, recipient roles and integrations you must rebuild, and on how many open envelopes must finish in DocuSign first. Teams usually run both systems in parallel until open envelopes close, so the overlap period is a planning decision rather than a fixed figure. DeployOpen agrees timelines in writing as part of a fixed-scope engagement before work starts. Ask for a timeline that separates template rebuilds, API and webhook changes, archive export and the parallel run.

What does our internal team need to provide during the migration?

Your team needs to supply a list of active DocuSign templates, the signing workflows behind them, and the systems that call the DocuSign API or receive its webhooks. You also need to name an owner for the hosting environment, decide which database engine you will run, and confirm who approves changes to signing workflows. Someone from legal or compliance should review the templates and signature wording before go-live. Clear decisions up front shorten the work and reduce rework.

Can we migrate from DocuSign to DocuSeal without outside help?

Yes, a team with server administration and integration skills can install DocuSeal from its Docker image and rebuild templates in its WYSIWYG field builder. The harder parts are repointing webhooks, deciding how archived envelopes are stored, and configuring backups and access controls to match your security policy. Outside help is most useful when many templates need rebuilding, when SSO or bulk send depends on the Pro edition, or when you need documented evidence for an assessment. Whichever path you choose, test each template end to end before retiring DocuSign.

Are DocuSeal signatures legally valid under the ESIGN Act?

Under 15 U.S.C. 7001(a), an electronic signature relating to a transaction in or affecting interstate or foreign commerce may not be denied legal effect solely because it is electronic. That rule does not settle every case, because ESIGN excludes records such as wills, codicils and testamentary trusts, most of the Uniform Commercial Code, state family law records and court documents, as set out in 15 U.S.C. 7003. Whether a particular DocuSeal signature holds up depends on your records, your signer consent process and your jurisdiction. DeployOpen does not issue legal opinions or audit reports, so confirm the question with your counsel.

Will our archived DocuSign envelopes remain usable after the move?

Archived envelopes stay usable if you export them to formats you control before your DocuSign subscription ends, and then store them in your own repository with their audit records. DocuSign provides export through its eSignature REST API, including combined PDFs and certificates of completion, so confirm which exports your plan allows and export them early. Keep the audit trail alongside each document, and test that you can open and verify archived files on the new system. Ask your DocuSign administrator to confirm the export scope before the subscription changes.

Does DocuSeal include qualified eIDAS signatures?

No, a self-hosted DocuSeal instance does not on its own provide qualified electronic signatures. Under the European Commission's eSignature FAQ, a qualified signature requires a qualified signature creation device and a qualified certificate from a qualified trust service provider listed in a national Trusted List. DocuSign's pricing page places advanced and qualified signatures on its Enhanced plans, so EU teams should map their need for each signature level before choosing a platform. Confirm the requirement with a qualified provider and your legal team.

How DeployOpen scopes and runs a DocuSign to DocuSeal migration

DeployOpen plans, implements, integrates, hardens, backs up and documents self-hosted DocuSeal inside your own infrastructure, whether that is your cloud account, your data center or an air-gapped network. In a DocuSign to DocuSeal move, the work usually covers the Docker deployment from the docuseal/docuseal image, the choice between SQLite, PostgreSQL or MySQL set through DATABASE_URL, storage and backup of the database and uploaded documents, TLS and access controls for the admin console, and the rebuilt templates and webhook endpoints that your systems depend on. Each of these is a decision with a cost and an owner, so it belongs in the written scope before any work starts.

Most engagements are fixed-scope. The written scope, deliverables and timelines are agreed before work begins, and they should name the things a DocuSign migration tends to miss: how many templates are rebuilt in the WYSIWYG builder, which signers and roles each template uses, whether Pro features such as bulk send from CSV or XLSX, SSO with SAML, white-label or embedded signing are in scope and therefore need a Pro license, how archived envelopes and their audit records are exported and kept, and which systems are repointed to the new webhooks and API. Ask for the scope to list each of these items separately so you can see what is included and what is left for your own team.

A quote follows from that written scope, so the more precisely you describe your template count, integrations, data location and retention needs, the more precisely the quote can reflect them. Ongoing support, upgrades and continuous testing of the DocuSeal instance are available as retainers, which suits teams that want a named party to apply new releases and patch the host after the migration closes. Confirm with DeployOpen which parts of the scope you would keep in-house after go-live, and agree on who owns the Pro license, the database backups and the signing setup from day one.

Migrate from DocuSign to DocuSeal