How to export your data from DocuSign

What you can export from DocuSign before you move

A renewal, a price change or a residency requirement has pushed you to plan an exit, and the first question is which agreements you can take out and in what form. Completed envelopes, their documents and their certificates of completion can be retrieved through the DocuSign eSignature REST API, so most of your signed record can be scripted for export. Open envelopes, account settings, users, sending configuration and some template details do not come out through the same calls, and those need a manual inventory and rebuild. Keep that boundary in mind from the start, because the API covers the records you must keep, while the workflow you must recreate requires your own documentation.

The API returns a single document from an envelope, or, using special keyword values for the documentId parameter, all documents as a combined PDF, a portfolio PDF or a ZIP archive, or only the certificate of completion. Every DocuSign eSignature plan includes a real-time audit trail and a certificate of completion with electronic record disclosure, so the certificate is the file to archive alongside each agreement. Confirm with your administrator which API account, integration key and consent grant your team holds, and whether your plan and permissions allow bulk retrieval across the account. The formal parameter names and response types are described in the DocuSign eSignature REST API OpenAPI specification.

Export the documents and certificates first, then check that each file opens, that the signer names and timestamps match the certificate, and that filenames map back to envelope IDs in your records index. Store the audit trail as a record in a system you control, with retention set by your legal and records teams rather than by the migration schedule. List every template with its recipient roles, anchor fields and routing order, because those definitions usually do not travel with the envelopes and must be rebuilt in your new platform. Ask your legal counsel whether any exported agreements fall under the ESIGN Act exceptions for wills, family law, certain Uniform Commercial Code records or court documents, since those may need paper or other handling.

Which DocuSign data exports and how

This table matches each record you need to keep with the DocuSign eSignature REST API method and output format that retrieves it. Use it as a checklist before a move, and confirm the limits in your own account before you schedule bulk downloads.

Data type	Export method	Format and what to confirm
Single envelope document	REST API document retrieval for one documentId from an envelope	Original file per document. Confirm each envelope's document count and file names so nothing is overwritten.
All envelope documents combined	REST API with documentId set to the combined keyword	One combined PDF per envelope. Confirm that page order and form fields suit your records before you rely on it.
Portfolio or ZIP of documents	REST API with documentId set to the portfolio or archive keyword	Portfolio PDF or ZIP archive. Test one envelope first to confirm how attachments and file names appear.
Certificate of completion	REST API with documentId set to the certificate keyword	Separate certificate per envelope. Every plan includes this certificate with electronic record disclosure, so store it with the signed PDF.
Audit trail as a record	Certificate and envelope history in the account, then saved to your archive	Audit events are kept in DocuSign's system. Confirm with DocuSign which audit data you can export, and save a copy in a format your auditors can read.
Template list and template content	REST API template listing and retrieval, then rebuild in the target platform	Template names, roles and fields are exported as data, not as a working template. Confirm role names and field types before rebuilding.
Envelope volume and rate limits	Scripted calls against the REST API across all envelopes	Not a fixed figure. Confirm the API request limits and envelope count for your account with DocuSign before scheduling a bulk export.
Retention and access rules	Account admin review before download	Confirm which envelopes are open, which must be retained for your own policy, and who may download signer data.

What does not export cleanly and the workaround for each

The documented API paths return completed documents and certificates, but they do not return a full copy of your DocuSign configuration. Template layouts, recipient roles, account settings, integrations and open envelopes each need a separate step before you cut over. The cards below cover what to record, what to rebuild and what to confirm with DocuSign before you retire the account.

Template layouts and field logic

Templates hold the PDF pages, tabs (fields), conditional behavior and routing that define each agreement. The REST API can list templates, but the export does not give you a portable file that rebuilds the field placement and logic in another product. Open each template in DocuSign, screenshot or note every tab type, its position, required flags and any conditional rules, then recreate it in your target tool. Confirm with DocuSign which template attributes the list endpoints return before you rely on them as the inventory.

Recipient role configuration

Each template defines recipient roles, signing order and whether a role is a signer, carbon copy or approver. Completed envelopes keep the names and emails that signed, but they do not tell you how the template assigned those roles or which steps ran in sequence. Record the role name, routing order, authentication method and access code settings for each template in a spreadsheet. Those notes become the specification for the new workflow and help you check that signer history still reads correctly in the archive.

Account users and permissions

Who can send, edit templates, view other users' envelopes or manage the account is set in DocuSign's administration console, not in the envelope files. Document exports carry no record of these roles. List each admin, sender and shared-folder owner, and map them to groups in your identity provider before you create accounts in the new platform. Confirm with DocuSign how sharing and folder permissions are reported for your plan, because the admin reports available to you depend on it.

Webhooks and API integrations

Connect Connect configurations, webhook endpoints and API integrations send envelope events to other systems, and they are not part of any envelope download. Missing them means an HR or CRM system can stop receiving signed notices without any error on the DocuSign side. Export the list of Connect configurations and integration keys from the admin area, note each event type and destination, and then repoint those systems to the new platform's API and webhooks. Test each path with a sample envelope before you switch off the old one.

Envelopes still in progress

Envelopes that are sent but not yet fully signed cannot be exported as completed records, and some recipients may still hold valid links to them. Pull a list of open envelopes by status, decide whether each one will be voided or finished in DocuSign, and tell senders the cutover date. Keep the account running in read mode until open envelopes close, and archive their certificates of completion once they finish. Confirm with DocuSign how long signing links remain valid after you void an envelope.

Retention and legal hold metadata

Retention rules, legal holds and the audit records DocuSign keeps on its servers may not match what you copy into your own archive. A signed PDF and its certificate show the signing event but not whether a hold applied. Ask your DocuSign administrator which retention settings applied to each account and record any holds in your own register before deletion. Confirm with your legal team how your records policy treats electronic signature evidence under the ESIGN Act, which does not apply to certain record types such as wills and most of the Uniform Commercial Code.

The export sequence and how to verify each batch

This sequence moves completed agreements, certificates, audit records and template definitions out of DocuSign in a fixed order, and each batch is checked against a source list before the next one starts. The result is an archive you can prove is complete before any signing moves to a new platform.

Freeze new sends and record the baseline
Before you export anything, ask the DocuSign administrator to stop new envelopes from going out for the systems in scope, and tell signers who still have open envelopes what happens to them. Then list every envelope with its status, created date, sender and recipients, and save that list as the baseline for the whole project. Record the total count of envelopes by status, such as completed, sent, delivered and voided. This baseline is the source list every later batch is checked against, so keep a copy outside DocuSign and label it with the export date. The step is done when the baseline file exists and someone other than the exporter has read the totals.
List envelopes by status and split them into batches
Use the eSignature REST API to pull envelope metadata for each status, paging through results so no envelope is skipped. Split the completed envelopes into batches by date range or by sender, so that a failed download affects one small group and not the whole archive. Keep open envelopes (sent or delivered) in a separate list, because they are not finished agreements and should be handled during the cutover period, not archived as final records. The output is a manifest per batch with envelope IDs, status, document count and page count where the API returns it. Confirm that the sum of the batch manifests equals the baseline total before downloading anything.
Download completed envelopes as combined PDFs or ZIP archives
For each completed batch, call the envelope documents endpoint and set the documentId parameter to the keyword for a combined PDF or a ZIP archive, depending on whether your records team wants one file per agreement or the original separate documents. Store each file under a path that includes the batch name and envelope ID, and write the file size and a SHA-256 hash to the manifest as soon as it is saved. Where a download fails or returns a partial file, retry that envelope alone and note the retry in the log. The batch is finished when every envelope in the manifest has one file and a recorded hash.
Retrieve certificates of completion for each envelope
Request the certificate of completion for each completed envelope by setting documentId to the certificate keyword. The certificate records the signers, the times they acted and the envelope identifiers, so it should be stored next to its agreement and never separated from it. Name each certificate with the same envelope ID used for the agreement, and keep a one-to-one link in the manifest. Verify the batch by counting certificates against completed envelopes in that batch, then comparing the page count of each agreement PDF with the page count recorded in the baseline or the source file. Any mismatch goes back into the retry list before the next batch starts.
Keep audit trails as dated records
DocuSign includes a real-time audit trail with every plan, so ask your team which audit records your retention policy requires and export them in the form your legal or compliance owner accepts. Store the audit information with the certificate for the same envelope, and record who exported it, when, and from which DocuSign account. Do not edit these files after they are written. Confirm with your compliance owner whether a separate export format, such as a copy kept in a write-once storage location, is required for your sector. The batch is complete when every audit record is stored, indexed to its envelope and signed off by the person responsible for records.
Export template definitions and recipient roles
List every template in the account through the templates endpoint, then retrieve each template's name, document list, recipient roles, routing order and field placement. Save the template details as structured files alongside a PDF copy of each template document, because these definitions are what you rebuild in the new platform. Compare the template count in the export with the count in the DocuSign interface, and note any template shared with a group or owned by a user who has left, since those can be missed by a simple list. The step is done when the template manifest matches the interface count and each template has a PDF and a definition file.
Run a final reconciliation against the baseline
Once every batch has passed its own check, compare the complete archive with the baseline from the first step. Confirm that the total number of envelopes, certificates, audit records and templates matches the source counts, that every file in the archive has a hash that matches its manifest entry, and that no completed envelope is missing. Have a second person re-run the hash check on a sample of files, and keep the reconciliation report with the archive. Ask your legal and compliance owners to confirm that the archive satisfies your retention obligations before any DocuSign data is deleted or the account is closed.

How to keep audit trails and certificates as records

Every DocuSign eSignature plan includes a real-time audit trail and a certificate of completion with electronic record disclosure, so the evidence of who signed, when and how is part of each envelope. Treat that evidence as a record in its own right. Retrieve the certificate of completion on its own through the eSignature REST API by setting the documentId parameter to the certificate keyword, then store it next to the combined PDF of the same envelope under the same envelope ID. Without the certificate, a signed PDF shows the final text but not the signing events that support it. Confirm with DocuSign's API specification in the DocuSign OpenAPI specifications which keyword values your integration version accepts before you write the export script.

Keep an export log that records who ran each export, the envelope IDs and document types exported, the date and time, the source account and the destination location. Store the log with the archive, and make the hash or checksum of each file part of the record so you can show later that a file was not altered. Also decide whether the new self-hosted platform will hold these files in its own database or only as attachments, because that choice changes where your retention and deletion controls must reach. Ask legal counsel which retention period applies to each agreement type before you delete anything in DocuSign. The period may depend on contract type, jurisdiction and limitation rules, and it is not a question this guide can answer for you.

The ESIGN Act does not cover every record type. Under 15 U.S.C. 7003, it excludes records governed by laws on wills, codicils and testamentary trusts, state family law such as adoption and divorce, most of the Uniform Commercial Code, and court orders and official court documents, among other exceptions. Ask counsel to sort your envelopes into these categories before migration. Records in excluded categories may still need paper originals or a different validity review, and the archive should flag them so they are not treated as ordinary e-signed contracts. The govinfo text of 15 U.S.C. 7003 lists the full set of exceptions.

Export paths for API users and admin-only accounts

Teams with developers who can call the DocuSign eSignature REST API can script the whole export. The API can retrieve a single document from an envelope or, by setting the documentId parameter to special keyword values, all documents as a combined PDF, a portfolio PDF or a ZIP archive, or only the certificate of completion. That makes it possible to pull the signed file and its certificate together for each agreement.

Credentials: An integration key and an authentication method approved for your DocuSign account, with the account ID and base URI for the correct data center.
Integration owner: One named engineer who owns the script, its schedule, its logs and the decision to rerun it.
Storage location: An encrypted target on your own servers or in your own cloud account, with a folder structure keyed by envelope ID.
Retry and checksums: Logging of each envelope ID, the response status and a file hash, so a failed download can be found and repeated.
Confirm first: Whether your plan and account permit the API calls you need, and the current API version documentation in the DocuSign OpenAPI specifications.

Keep the exported certificate with its envelope, because it is the record of the signing event. Confirm the exact keyword values against the current specification before writing the script.

Questions buyers ask before exporting DocuSign data

How much effort does a DocuSign export take, and what drives it?

The effort depends mostly on how many envelopes you hold, how varied the templates and recipient roles are, and whether your storage and naming rules are already settled. A small account with uniform envelopes is a scripted download with checks. A large account with years of history, several business units and custom metadata needs more scripting, sampling and reconciliation. The DocuSign eSignature REST API can return one document, all documents as a combined PDF, a portfolio PDF or a ZIP archive, or only the certificate of completion, so the choice of format per envelope adds planning work. Ask your implementation partner for a count of envelopes and templates before you agree on scope, because that count shapes the quote.

Can our team export DocuSign data without outside help?

Often yes, if you have someone comfortable with REST calls, OAuth-based authentication and scripting, and someone who owns the records policy. The API documentation is published in the DocuSign OpenAPI specifications, so developers can start from the official definitions. Teams usually stumble on pagination, rate limits, file naming, handling envelopes in several accounts, and proving that every envelope was exported. If those skills or the time are not available internally, a fixed-scope engagement can take that work off your plate. Confirm internally who will sign off on completeness before you start.

What does the export need from our team before it starts?

Plan for four inputs: API access to the DocuSign account, credentials with rights to read the envelopes you need, named owners who approve the scope and the retention decisions, and a storage target with enough capacity and access controls. Confirm which DocuSign account or accounts hold the envelopes, whether any envelopes sit under other users, and who may view the archive afterward. Storage choices such as an existing file store or object storage should be decided in advance, along with backup and encryption requirements. Your own security team should approve where the exported files and metadata land.

How long does the export take, and what sets the timing?

No duration is fixed here, so ask for a timeline based on your own environment. The main drivers are envelope volume, total document size, API throughput limits on your account, the number of accounts, how much verification you require, and how many approval rounds the scope needs. Exports that run in parallel with live signing need a freeze point so new envelopes are not missed. Build time for a verification pass, where you compare envelope counts and sample files against the source, and time for any restarted batches after errors.

Is a certificate of completion enough to prove a signed agreement?

A certificate of completion is useful evidence, but it should not stand alone. Every DocuSign eSignature plan includes a real-time audit trail and a certificate of completion with electronic record disclosure, so you should export both the signed documents and the certificate for each envelope. Whether a record is legally sufficient depends on the transaction and the jurisdiction. Under the US ESIGN Act, an electronic signature or record may not be denied legal effect solely because it is electronic, but the Act has exceptions, such as wills, certain family law records and court documents. Ask your counsel which agreement types need retention beyond the certificate.

What does a fixed-scope DocuSign export engagement cover?

A fixed-scope engagement covers the agreed items in writing before work starts. A typical scope, subject to your own agreement, includes inventory of accounts, envelopes and templates, scripted export of completed envelopes in the formats you choose, retrieval of certificates of completion and audit records, a listing of templates and recipient roles for rebuilding, storage of the archive in your environment, and a verification report. DeployOpen plans and implements these items within your infrastructure. It does not issue audit reports or attestations, so a compliance assessor must still review your retention controls. Ask for the exact deliverables, acceptance criteria and exclusions in the written scope.

Do we need to export templates, and how are they handled?

Templates are not signed records, but you will need them to rebuild signing workflows on a self-hosted platform. Listing templates through the API captures names, document structure, recipient roles and routing, which helps you rebuild them in Documenso or DocuSeal. Template rebuilding is manual work in many cases, because field placement and conditional logic rarely translate directly. Count templates early, prioritize the ones still in use, and confirm which ones must be preserved as evidence of the form that was signed.

What to plan before the DocuSign contract ends

Plan the export while the DocuSign account is still active and fully paid, because the timing of access after cancellation is the one thing you cannot reconstruct later. Export completed envelopes, certificates of completion and audit trail records first, then templates and recipient role settings. Before you give notice, confirm in writing with DocuSign how long you can sign in, download documents and call the eSignature REST API after the subscription ends, and whether any retention window applies to your account. Ask for the answer in the contract or order documentation, not only from a sales contact, so the date your team works to is one you can point to.

Work out what happens to envelopes that are still open. A recipient who has not signed yet cannot complete an envelope in a system you have switched off, so decide for each open envelope whether to let it close in DocuSign before the cutoff or to void it and send a fresh request from the new platform. Record which agreements were re-sent, to whom and on what date, because a counterparty may ask which version of a contract they signed. Keep the same document content, but expect that the new envelope will carry a different identifier and certificate of completion.

Keep the old account readable until verification passes. Treat the export as complete only after you have opened a sample of downloaded PDFs and certificates, matched envelope counts and signer names against DocuSign, and confirmed that each ZIP or combined PDF contains every document you expected. Store the old account's exports, templates and audit records in your own retention system before the subscription lapses. Ask your compliance and legal teams which retention periods and record formats apply to each contract type, since the ESIGN Act covers electronic records generally but does not settle how long you must keep them.

What to plan before renewal or termination

Exporting files is only one part of leaving DocuSign. The cards below cover the contract terms, final exports, open envelopes, integrations, retention duties and sign-off that decide whether the move closes cleanly. Confirm each item with DocuSign and your counsel before the notice window passes.

Notice dates and renewal terms

Find the notice period, auto-renewal clause and the exact date your subscription ends in the signed order form, not in a sales summary. Ask DocuSign in writing whether API access, envelope storage and the audit trail remain available after termination, and for how long. Confirm whether any export fees or data deletion schedules apply. Build your export timeline backward from that end date.

A final full export before access ends

Run a complete pass of completed envelopes, certificates of completion and templates through the REST API, then repeat it close to the cutoff to capture late completions. Store each archive with its envelope ID so records can be matched later. Keep one copy outside the DocuSign account, in storage your organization controls. Do not treat the first export as the final one.

Open envelope handling

Envelopes still waiting for signers cannot be finished in the new system with their existing history. Decide per envelope whether to let it complete in DocuSign before the cutoff, void it and resend from the new platform, or keep it open in a parallel run. Record each decision, since a resent agreement is a new record for the signer. Confirm the handling with counsel for contracts that have deadlines.

Integration and webhook switchover

List every system that calls the DocuSign API or receives its Connect notifications, including CRM, HR and document management connectors. Point each one at the new platform in a staging environment first, then cut over in a controlled window. Keep the DocuSign endpoints alive until no envelopes are in flight. Missed status events are a common source of lost completion records.

Retention obligations and legal review

Your retention schedule, not the export tool, decides how long completed agreements and audit records must be kept. Map each contract type to its retention period and to any legal hold. Check that exported PDFs and certificates remain readable and verifiable after DocuSign is gone. Ask counsel whether the ESIGN Act exclusions, such as wills or court documents, apply to any of your envelopes.

Written verification sign-off

Compare envelope counts, template counts and a random sample of archived agreements against DocuSign before access ends. Record the totals, the sample results and the person accountable for each check in a signed record. Keep the sign-off with the migration file, because auditors and counterparties may ask how completeness was verified. Only close the DocuSign account after this record exists.

Where the exported files go next

Once the PDFs, ZIP archives and certificates of completion are on your own storage, the destination decides how they are used. If the goal is a long-term record, load them into a self-hosted archive or document repository that your retention policy already covers, and keep each envelope's certificate of completion beside its combined PDF so the signer events stay attached to the agreement. If the goal is to keep signing in Documenso or DocuSeal, the exported files are reference copies, not working documents. Neither platform reads a DocuSign envelope, so historical agreements will not appear as Documenso documents or DocuSeal submissions unless you upload them as new records, which should be a deliberate choice for each contract family.

Templates, recipient roles, signing certificates and webhook endpoints are a separate job. Documenso needs a signing certificate of its own before it can digitally sign documents, and its options include a self-signed .p12 certificate generated with OpenSSL or signing through Google Cloud KMS. DocuSeal's PDF field builder replaces DocuSign tabs, which means its templates are rebuilt by hand from the PDFs you have already exported. Export the template list from the API first so you know which templates exist, then confirm with your legal and operations owners which of them still need to be rebuilt. The migration pages cover how to rebuild those templates, roles and certificates in each platform.

Before you delete anything in DocuSign, check two things in your own environment: that every exported file opens, its page count matches the envelope, and its certificate of completion is readable, and that your retention schedule for each agreement type is written down and applied to the new location. Ask your compliance owner whether an archive copy plus a certificate is enough for each category, since the ESIGN Act exceptions for wills, family law and court documents may call for separate handling. Keep the DocuSign account open until the export is verified and your legal owners confirm the archive is complete.

How DeployOpen scopes and delivers a DocuSign export

DeployOpen treats a DocuSign export as a scoped piece of migration work, not a one-off download. We agree what is exported, how it is verified and where the archive lives before any envelope is pulled, so the records you keep can be produced and checked later.

How we scope

Inventory completed envelopes, templates and recipient roles in your DocuSign account before work starts.
Agree in writing which envelopes, certificates and audit trails are in scope and which retention period applies.
Confirm which API credentials, account types and storage location your organization will approve for the export.

How we build

Script retrieval through the eSignature REST API, using the combined, portfolio, ZIP and certificate options for each envelope.
Test the export on a sample envelope set and compare page counts, hashes and certificate contents against DocuSign.
Store archives in your own storage with naming, folder structure and access controls agreed in the scope.

How we hand over

Deliver an export log listing each envelope, its status, file names and any retrieval failures.
Document the template list, field names and recipient roles needed to rebuild workflows in the target platform.
Provide a runbook explaining how to search, restore and verify archived records without DocuSign access.

How we support

Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work begins.
Ongoing support, upgrades and continuous testing are available as a retainer after handover.
Ask any quote to itemize scoping, scripting, verification, documentation and handover so you can compare components.