> ## 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 Docusign > Move your templates, contacts and team from Docusign to Flowsign, step by step, and keep an archive of your completed envelopes. This guide moves your documents, templates, contacts and team from Docusign to Flowsign. There is no automatic importer: you re-upload your files and rebuild your templates, and completed envelopes stay behind as a downloaded archive. ## Before you start > [!WARNING] > > Check your renewal date first. Docusign plans renew automatically, and contracts arranged through Docusign's sales team get a renewal notice about 90 days before the term ends. Give yourself enough time to finish the move before that date. > [!WARNING] > > Download your archive before you change anything on the Docusign account. Closing the account removes access to envelope history and downloads. Docusign recommends downgrading to its Free plan, not closing the account, if you want to keep access to your history. ## What moves and what doesn't | Item | From Docusign | In Flowsign | | - | - | - | | Templates | **Download** gives a template file in a Docusign format, for re-upload into Docusign | Rebuilt by hand from the original PDFs | | Fields on a document | Not carried across, unless the PDF has real fillable form fields | **Import form fields** for fillable PDFs, placed by hand on flat PDFs | | Completed envelopes | Downloaded per envelope, with the certificate of completion | Not imported. Keep the downloaded archive | | Envelopes out for signature | Finish them, or void and resend | Sent again as new packages | | Contacts | No export button. Gather them into a CSV | CSV import with column mapping | | Users | Organisation admins can export the user list as CSV | Members are invited one at a time with a role | | Bulk sends | Recipient lists you kept | Bulk send from a per-template CSV (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 Docusign today, so nothing is missed on the way out: * Templates * Bulk sends * Web forms * Payments * SMS delivery * ID verification * SSO * API or Connect integrations 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 PDFs** In Docusign, open the **Templates** page, open a template's actions menu and choose **Download**. You get a template file, or a ZIP when you download several. That file is a Docusign format meant for re-upload into Docusign, so keep the original PDFs too. They are what you rebuild from in Flowsign. For each template, write down its roles, the signing order, and which fields each role completes. **3. Download your completed envelopes** Download each completed envelope, either as separate files in a ZIP or as one combined PDF, and include the certificate of completion. For a large volume, use the Docusign eSignature API or one of Docusign's bulk tools. Docusign Retrieve is a paid add-on. > [!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** An organisation admin can export the Docusign user list as a CSV. Use it as your list of who to invite, and which role each person needs. Docusign has no contacts export button. 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 envelopes still out for signature** Envelopes in progress do not move. Let them finish in Docusign, or void 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 in Docusign, 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. 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. 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 (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 answers decide which documents go out or who signs, build that as a workflow (Business and up). 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 envelope left in Docusign has finished or been voided. * Check that your downloaded archive opens and includes the certificates of completion. * Deal with the Docusign account before it renews. Docusign recommends downgrading to its Free plan to keep access. Closing the account removes access to envelope history and downloads. ## 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.