> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flowsign.app/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Flowsign is one word with a lowercase s.
> The REST API base URL is https://my.flowsign.app and every endpoint lives under /api/v1.
> When answering API questions, cite the HTTP method and endpoint path.
> API access needs the Enterprise plan and an API key with the API access permission.

# Migrate from Adobe Acrobat Sign

> Move your templates, contacts and team from Adobe Acrobat Sign to Flowsign, step by step, and keep an archive of your completed agreements.

This guide moves your documents, templates, contacts and team from Adobe Acrobat Sign to Flowsign. There is no automatic importer: you re-upload your files and rebuild your templates, and completed agreements stay behind as a downloaded archive.

## Before you start

> [!WARNING]
>
> Check your renewal date first. Acrobat Sign annual plans renew automatically, and some plans billed monthly on an annual term can carry an early termination fee. Confirm the terms against your own plan or contract, and give yourself enough time to finish the move before that date.

> [!WARNING]
>
> Download your archive before your Acrobat Sign licence ends. Adobe does not promise to keep your agreements or audit reports after that, and there is no guaranteed read-only period.

If your account uses data governance retention rules, older agreements may already be scheduled for automatic deletion. Check those rules before you plan the export.

## What moves and what doesn't

| Item | From Acrobat Sign | In Flowsign |
| - | - | - |
| Library templates | **Download PDF** gives the document only. Field definitions are not exported | Rebuilt by hand from the downloaded PDFs |
| Text tags and fields | Not carried across. Flowsign does not read text tags such as `{{Sig_es_:signer1:signature}}` | Remove the tags from the source file, then place fields in the field editor |
| Completed agreements | Downloaded per agreement, with the audit report | Not imported. Keep the downloaded archive |
| Agreements out for signature | Finish them, or cancel and resend | Sent again as new packages |
| Contacts | Recipient details from your agreements. Gather them into a CSV | CSV import with column mapping |
| Users | Exported as a CSV from the Users page or the Adobe Admin Console | Members are invited one at a time with a role |
| Send in Bulk | Recipient lists you kept | Bulk send from a per-template CSV (Business and up) |
| Custom send workflows | Notes on the routing you built | Workflow (Business and up) |
| Branding | Your logo and brand colour | Logo and brand colour on emails (Business and up) |

## Steps

**1. Take an inventory**

List what your team uses in Acrobat Sign today, so nothing is missed on the way out:

* Library templates
* Send in Bulk
* Web forms
* Custom send workflows
* Recipient groups and roles such as approver or acceptor
* SSO
* Microsoft 365, Salesforce or Workday integrations
* Webhooks or API

For each item, note who owns it and how often it is used. Flowsign may not have a match for every item, so check the list against these docs, or [ask us](/support/contact.md), before you set a switch date.

**2. Download your templates and the original files**

In Acrobat Sign, open **Manage**, then **Templates**, select a template and choose **Download PDF**. You get the document, but not its fields, roles or signing order.

Keep the original source files too where you have them. For each template, write down its recipients in order, the signing order (sequential, parallel or a mix), and which fields each recipient completes.

If your documents use text tags, note what each tag does. The `signer1`, `signer2` numbering follows the recipient order on the agreement, which tells you which role each field belongs to.

**3. Download your completed agreements**

Turn on the account setting **Attach Audit Report to Emails and Downloads** first. It is off by default, and with it on, each downloaded PDF includes its audit report.

Then, on the **Manage** page, select each completed agreement and choose **Download PDF**. **Download Individual Files**, **Download Audit Report** and **Download Form Field Data** are in the same panel if you need them. For a Send in Bulk parent, **Download Completed Agreements** gives one ZIP of the completed children, without audit reports.

For a large volume, the Acrobat Sign REST API is the realistic route, because downloads in the web app are per agreement. The **Reports** tab can also export a CSV of agreement details for your records.

> [!NOTE]
>
> Signed documents from another platform cannot be imported into Flowsign with their audit trail or certificate. Store the downloaded archive somewhere safe and treat it as your record.

**4. Export your users and gather your contacts**

Export the user list as a CSV from the **Users** page in Acrobat Sign, or from the Adobe Admin Console. Use it as your list of who to invite, and which role each person needs.

Gather your contacts into a CSV with a column each for name, email, phone, job title, company and tags. Every row needs a name and a valid email.

**5. Finish the agreements still out for signature**

Agreements in progress do not move. Let them finish in Acrobat Sign, or cancel them and resend them from Flowsign once your templates are ready.

**6. Set up your Flowsign organisation**

Follow [Setting up your organisation](/guides/organisation-setup.md) for the full order. The parts that matter most for a move:

* **Branding (Business and up).** Add your logo and brand colour in [Branding](/guides/settings/branding.md) so your emails look familiar to recipients from day one.
* **Members.** Invite each person from your exported user list in [Members](/guides/settings/members.md), one at a time, with a role. See [Roles & Permissions](/guides/settings/roles-and-permissions.md).
* **SSO and provisioning (Enterprise).** If you used SSO through the Adobe Admin Console, set up single sign-on and SCIM provisioning in [Organisation security](/guides/settings/security.md).

**7. Import your contacts**

In [Contacts](/guides/contacts/contacts.md#importing-contacts), choose **Import** from the **More actions** menu, pick your CSV and check the column mapping. Rows without a name and a valid email are skipped.

**8. Rebuild your templates**

For each template, create a new one and upload the original files. If they contain text tags, remove the tags first, because Flowsign does not read them and they would show on the signed document. Flowsign accepts PDF, Word, Excel, PowerPoint and images, and converts anything that is not a PDF to one. See [Document types](/document-types.md) and [Building a workflow](/guides/building-a-workflow.md).

Add your roles and signing order, then place the fields in the [template field editor](/guides/templates/template-fields.md):

* **Fillable PDFs.** If the PDF has real form fields, the field editor shows **Import form fields** with a review step. You still assign each field to a role by hand. See [Field editor](/guides/packages/fields-editor.md).
* **Flat PDFs.** Place each field by hand. Expect this for Acrobat Sign template downloads.

The field types are signature, initials, date signed, name, email, company, title, text, number, checkbox, radio, dropdown and merge field. Set reminders and expiry on the template, then publish it.

> [!TIP]
>
> Start with the two or three templates your team sends most. The rest can follow once the first ones are in use.

**9. Recreate your bulk sends and workflows (Business and up)**

A bulk send in Flowsign runs from a template, with a CSV of recipients for that template. See [Bulk send from a template](/guides/bulk-send/create-bulk-send.md).

If you used custom send workflows, or answers decide which documents go out or who signs, build that as a workflow. See [Workflow signing](/guides/building-a-workflow.md#workflow-signing).

**10. Send a test package**

Send each rebuilt template to yourself and a colleague before the team relies on it. Check the email, the signing order and every field. [Getting started](/getting-started.md) covers a first send from start to finish.

## After you switch

* Tell your team the date new documents start going out from Flowsign, and point them to [Getting started](/getting-started.md).
* Confirm every agreement left in Acrobat Sign has finished or been cancelled.
* Check that your downloaded archive opens and includes the audit reports.
* Deal with the Acrobat Sign plan before it renews, and only once the archive is safe.

## Need a hand?

The Enterprise plan includes hands-on migration: the Flowsign team rebuilds your templates and sets up your workspace with you. [Contact support](/support/contact.md) to talk it through.

## Related

* [Setting up your organisation](/guides/organisation-setup.md)
* [Building a workflow](/guides/building-a-workflow.md)
* [Contacts](/guides/contacts/contacts.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.