Navigate to the Migrate templates from Docusign menu item in the Admin menu.
Last updated on
Jun 27, 2025
Alert:
This article contains prerelease information. Release dates, features, and other information are subject to change without notice.
Easily move your existing Docusign templates and workflows into Acrobat Sign to maintain consistency, save time, and reduce setup effort.
Note:
The Migrate templates tile on the Home page and the Migrate templates from Docusign option in the Admin menu are currently available only to VIP and VIPMP licensed accounts. Support for ETLA accounts is coming in a future release.
Acrobat Sign supports direct import of Docusign templates and envelopes. This migration process helps organizations transition their workflows while preserving field data, recipients, and structure.
What Gets Created in Acrobat Sign
Library Templates
- Docusign templates are converted into Acrobat Sign library templates.
- Fields (called "tabs" in Docusign) are mapped to Acrobat Sign form fields.
- Templates appear under the Templates filter on the Manage page.
Workflows
- Workflow logic in Docusign templates is used to generate custom workflows in Acrobat Sign.
- Created workflows appear in the Custom Workflows tab with the tag Migrated displayed
Supported elements in the migration
The following Docusign objects are mapped during migration:
| Docusign Object | Acrobat Sign Equivalent |
|---|---|
| Envelope | Agreement |
| Template | Library Document and Custom Workflow |
| Document | Uploaded PDF as a Library Document |
| Recipient | Participant |
| Tab | Form Field |
Not all of the Docusign elements can be mapped to equivalent elements in Acrobat Sign, and those elements that are not supported will require some manual adjustments:
Recipient mapping elements:
Docusign recipient role |
Acrobat Sign recipient role |
Can it be mapped? |
|---|---|---|
| Needs to Sign | Signer | Yes |
| In Person Signer | - | No |
| Receives a Copy | CC | Yes |
| Needs to View | Certified Recipient | Yes |
| Signs with Witness | - | No |
| Editors | - | No |
| Notaries | - | No |
| Agents | - | No |
| Seals | - | No |
Field mapping elements:
Docusign fields |
Acrobat Sign fields |
Can it be mapped? |
|---|---|---|
| Signature | E-Signature | Yes |
| Initial | Initials | Yes |
| Stamp | Stamp | Yes |
| Date Signed | Date | Yes |
| Name | Recipient Name | Yes |
| Recipient Email | Yes | |
| Company | Company | Yes |
| Title | Title | Yes |
| Text | Text | Yes |
| Number | Number | Yes |
| Checkbox | Checkbox | Yes |
| Dropdown | Dropdown menu | Yes |
| Radio | Radio button | Yes |
| Payment Item | - | No (Skipped) |
| Drawing | - | No (Skipped) |
| Formula | - | No (Skipped) |
| Attachment | Attachments | Yes |
| Note | - | No (Skipped) |
| Approve | - | No (Skipped) |
| Decline | - | No (Skipped) |
| Custom Fields | - | No (Skipped) |
Note:
Custom settings in the Docusign environment are not retained in Acrobat Sign.
Configuration
Availability:
- Acrobat Standard and Acrobat Pro: Not Configurable
- Acrobat Sign Solutions: Supported for enterprise tier VIP/VIPMP licensed accounts only
- Acrobat Sign for Government: Not Supported
Configuration scope:
Administrators can access this feature at the account level only.
Access this feature by selecting the Migrate templates tile on the Home page or by navigating the administrator's configuration menu to Admin > Migrate templates from Docusign
You may see one of the following messages if your account isn’t eligible:
- To migrate templates from Docusign, please contact your sales representative to upgrade from a business to an enterprise license.
- Your account tier does not support template migration.
- To migrate templates from Docusign, please enable creation of custom workflows in your global settings.
- The Workflow Designer feature must be enabled before migration can proceed.
How to migrate your templates
Upon first accessing the migration landing page, the admin is presented with a three-step view of the process.
To start the process:
-
-
Select the Select file button and browse to your zip file containing your Docusign templates.
If you have previously migrated some templates, select the Start new migration button.
-
Once the file is uploaded, the page refreshes to show the template file name and a Start migration button.
Select Start migration.
-
Migration in Progress
During migration:
- The system converts Docusign JSON to Acrobat Sign-compatible data.
- Each object (template, envelope, document, etc.) is validated and imported.
- Status and results are logged for each migration request.
-
Review Migration Results
Once complete:
- A confirmation message appears: Migration completed.
- Select Review workflows to view the imported workflows.
- To review templates, go to the Manage page and select the Templates filter.
The Custom Workflows page shows all of the completed and partially successful workflows that have been imported (identified by the Migrated tab displayed).
You can edit migrated workflows and templates at this time to ensure all roles and fields are properly mapped.
The Migration Summary table
After the first time a template is uploaded, the Migrate templates from Docusign page shows a list of all previous migrations.
The table has four columns:
- Zip file name - The exact file name that was uploaded for the migration.
- Total templates uploaded - The number of workflows in the zip file.
- Migrated workflows - this field contains either a summary of the migrated workflows (1 of 1) or a warning icon that contains a summary of the templates uploaded and their relative status in the Acrobat Sign system
- Status - The overall status of the migration.
Each row of the summary table indicates one uploaded file.
Selecting any one row will redirect the user to the Custom Workflows page, and filter the page content to only show the workflows that were imported in that migration:
Status codes and warning icons
When the migration is complete, a status is displayed, and a summary of the migrated workflows.
A migration that completes successfully shows a Status of Completed, and the migrated workflows will show 1 of 1 in terms of the Migrated workflows. Note that the Migrated workflows number reflects the number of zip files, not the total number of workflows imported during the process.
The migration process can fail for a couple of reasons:
- If the recipient role cannot be mapped, the migration will present as Failed.
- In this case, the workflow will have to be recreated manually to ensure that proper roles are assigned.
- If the recipient can be mapped, but one or more fields cannot be, the migration presents the workflow as a Partial Migration Success.
- These workflows require that the library template be manually evaluated to confirm the field placement and to assign any field types that can not be mapped.
- Partial migrations count as successful migrations in terms of the migration status.
Template Migration Statuses:
- MIGRATION_SUCCESS: Docusign template completely migrated to Acrobat Sign Workflow with all fields and recipients.
- If one template is successfully migrated, the overall status will be Completed.
- PARTIAL_MIGRATION_SUCCESS: The Docusign template was migrated to Acrobat Sign. All the recipient roles can be mapped, but some of the fields can't.
- Partial migrations count as successful migrations in terms of the overall migration status, but still require template cleanup.
- MIGRATION_FAILED: Docusign template migration failed as one of the Recipient roles can't be mapped to an Acrobat Sign Workflow.
- If all workflows fail, the overall migration status displayed is Failed.
- If some workflows fail, but others are successful, the failed workflows are listed under the warning icon
- SKIPPED: Docusign template migration skipped as the same template has already been successfully migrated to Acrobt Sign.
- If all workflows are skipped, the overall status of the migration will display as Discarded.
- If some workflows are skipped, the skipped workflows are listed under the warning icon, but otherwise don't impact the overall status of the migration.
